Software engineer fresher resume format

A fresher software engineering resume is read twice: once by a parser looking for stack keywords, once by an engineer looking for evidence you have built something that works. It has to pass both, and the two readers want the page organised the same way.

The projects section is the resume. Everything above it exists to get the reader there, and everything below it is corroboration.

Link a GitHub profile with pinned repositories that have README files. An engineer will click it, and an empty profile is worse than no link at all.

Section order

Top to bottom. The order matters more than the styling, because it decides what a reader sees in the first few seconds.

HeaderName, phone, email, GitHub, LinkedIn, portfolio. Links must be live.
Technical skillsGrouped: languages, frameworks, databases, tools. Parser food and human scan.
ProjectsTwo or three. The section the decision is made in.
Experience / internshipsBelow projects unless you shipped to production.
EducationDegree, CGPA on a stated scale, graduation year.
AchievementsCompetitive programming ratings, hackathons, open-source contributions.

What has to be on the page

A working GitHub link with pinned, documented repositories.
Projects with the stack named, a deployed URL where possible, and a measurable outcome.
Skills grouped by category, with a database and version control present.
Any open-source contribution with the repository and the merged pull request linked.

Bullets in the right shape

Bracketed values are placeholders. Substitute your own real figures, and leave a line out entirely rather than inventing a number for it.

Built [an expense-splitting web app] in [Next.js, TypeScript and Postgres]; deployed on [Vercel] and used by [65] users across [4] months with [~1,200] transactions recorded.

Cut API response time from [820 ms to 190 ms] on the [search] endpoint by adding a [composite index] and replacing [N+1 queries] with a single join.

Contributed [3] merged pull requests to [open-source project], including a fix for [issue] affecting [the CLI's config resolution].

Mistakes that cost this profile interviews

Instead ofA skills list of twelve languages, most of which you used once.

Do thisList what you would defend in an interview. An engineer will pick the weakest-looking item on the list and ask about it.

Instead ofProjects with a stack and no outcome, so every entry reads 'built X using Y'.

Do thisAdd the result: users, latency, accuracy, records processed. Without one it is indistinguishable from a tutorial.

Instead ofA GitHub link to a profile with three empty repositories.

Do thisEither populate it with the projects on your resume and write READMEs, or remove the link.

Instead ofListing DSA problem counts as the main achievement.

Do thisKeep one line for a rating or rank if it is genuinely competitive. Problem counts alone say you practised, not that you built.

Free template for this format

Terminal — Monospaced accents and a dense skills grid that reads as native to engineering hiring, while staying fully parseable. Hand-designed, and the PDF and Word exports are free with no watermark and no card.

Use the Terminal template Score a resume you already have

Questions

How many projects should a fresher software engineer resume have?

Two or three, described properly. Five thin entries look like a course completion list. One deployed project with real users outweighs four that only ever ran locally.

Does a fresher developer resume need a summary?

No. With one page and no experience the space is better spent on a project bullet. Add a two-line summary only when you are switching domains and the resume needs explaining.

Should I list DSA or LeetCode stats?

Only a rating or contest rank, and only if it is competitive. Recruiters treat solved-count as practice, not as evidence of shipping ability.