Contents
Part 1: A resume that gets read

Section by section

What goes in each section, in what order, and the weak versions recruiters see a hundred times a day.

Header

  • Your name, large. Under it, your target title: “Full-Stack Developer (Next.js, TypeScript, PostgreSQL)”. Not “Fresher”, not “Aspiring Developer”.
  • Area and city (“HSR Layout, Bengaluru”), phone with +91, a professional email.
  • LinkedIn, GitHub, and portfolio URLs written out as text.

Summary

Three lines at most: what you are, the strongest concrete thing you built, and when you can join.

Weak
MCA graduate and Full Stack Developer passionate about building real-world web applications. Seeking an entry-level role where I can apply my skills and grow as a software developer.
Strong
MCA graduate who builds and deploys full-stack web apps with Next.js, TypeScript, Prisma and PostgreSQL. Built a multi-vendor marketplace with 4 user roles, order tracking and returns, live on Vercel. Available to join immediately.

“Available to join immediately” is a real advantage. Employed candidates have 30 to 90 day notice periods. Say it.

Technical skills

  • Four grouped lines, not a list of 30 tools: Languages, Frontend, Backend & Database, Tools.
  • If your projects are in TypeScript, list TypeScript first. Many job descriptions filter on it.
  • Only list what you can build in an interview today. If Express.js is on your resume, expect to write an Express route live.
  • Be exact. If you used Supabase only as a hosted Postgres database through Prisma, write “Supabase (Postgres hosting)”. Otherwise “how did you use Supabase Auth and Storage?” becomes a trap.

Projects

  • Your 3 strongest, not everything you built. Tutorials and clones don’t count.
  • Each one: a real product name, the dates you worked on it, the stack, a live link, a GitHub link, and 2 to 4 bullets.
  • Put the project with the hardest engineering first, not the one you finished last.
  • Dates matter: they show a timeline of steady work since graduation.

Internship

If you did an internship or company training, it goes in its own section with the company name, role, dates and 2 or 3 bullets about what you built. With an internship, use format C so it sits at the top.

Education

  • Degree, specialisation, university, years.
  • For startups, add CGPA only if it’s 7.5 or above.
  • For services companies (TCS, Infosys, Wipro), include marks for every degree plus Class XII and Class X. They screen on eligibility cut-offs.

Certifications and achievements

  • Certifications only if they are relevant and verifiable. Most startups ignore them, and services companies like them.
  • Achievements that carry weight: a merged open-source pull request, a hackathon result, a talk at a meetup.
  • Leave out “completed 100 days of code” or course completion streaks.

Languages

List every language you speak. Kannada, Telugu, Tamil, Odia, Hindi and others start real conversations with founders, managers and alumni from your state.

If there’s a gap since graduation

“What have you been doing?” is often the first HR question. Handle it with honesty, not with an invented job title:

  • Dated projects show the timeline on the page itself.
  • Your summary says what you’ve been building.
  • Prepare one spoken answer: “I chose to build instead of waiting for campus placements. I built three full-stack apps, and the marketplace is the one I’m proudest of. Now I want to do this inside a real team with code review.”