How long should a software engineer resume be?

One page for under five years of experience, two pages beyond that. Length is not the constraint — relevance is. A second page earns its place only if the older roles still say something the first page does not.

Should I list every programming language I know?

No. List what you want to be hired for and what you could defend in an interview tomorrow. A language you used once in 2019 dilutes the signal and invites a question you cannot answer well.

Do I need a GitHub link?

Only if the profile is worth reading. An active repository with real commits helps; an empty profile with three tutorial forks actively hurts, because the reader clicked expecting evidence and found none.

Where do side projects go?

Below professional experience, and only projects with users or a genuinely interesting technical problem. For career changers with little professional history, promote them above — they are your evidence.

Software engineer resume example

A strong software engineer resume leads with impact rather than technology: what the system does now that it did not before, and the number that proves it. List languages and frameworks in a scannable skills block, keep the experience section to outcomes, and put the stack you actually want to be hired for first.

Summary section

Backend engineer with six years building payment and identity systems in Go and TypeScript. Cut p99 checkout latency from 1.8s to 240ms by replacing a synchronous fan-out with an event queue, and led the migration of 40+ services to a shared auth library.

Achievement bullets that work

Written to show the result first and the method second. Adapt the structure — never copy the numbers.

Cut p99 checkout latency from 1.8s to 240ms by replacing a synchronous fan-out with an event-driven queue, removing the timeout errors that affected 3% of transactions.
Led migration of 40+ services onto a shared authentication library, eliminating four duplicate token implementations and closing a session-fixation vulnerability found in audit.
Reduced CI runtime from 22 to 6 minutes by parallelising the test suite and caching dependency layers, recovering roughly 15 engineer-hours per week across the team.
Designed and shipped the rate-limiting layer now handling 40M requests/day, sized from measured traffic rather than a guess, with zero incidents in the year since launch.
Mentored three junior engineers through their first on-call rotations; all three now lead incident response independently.

ATS keywords for Software Engineer roles

Terms that postings for this role commonly contain. Use the ones that are true of you, in the posting’s own wording.

software engineer
backend
API design
distributed systems
CI/CD
code review
unit testing
REST
microservices
Git
Agile
SQL
cloud (AWS/GCP/Azure)
containerization
system design

Lead with the outcome, not the stack

The most common failure in engineering resumes is a list of technologies with no evidence they achieved anything. "Worked with React, Node, and PostgreSQL" tells a reader what you were near, not what you did. Every posting attracts dozens of candidates who have touched the same tools; the differentiator is what changed because you were there.

Rewrite each bullet so the first clause is the result and the technology is the mechanism. "Cut p99 checkout latency from 1.8s to 240ms by replacing a synchronous fan-out with an event queue" contains the same stack information as a list, but it also proves you can diagnose a performance problem and choose an appropriate fix. That is the thing being hired.

Quantify honestly, including when the number is small

Engineers routinely under-report because the honest number feels unimpressive. A 6-minute CI improvement sounds minor until you multiply it by the team and the year. Do that multiplication in the bullet — "recovering roughly 15 engineer-hours per week" — and let the reader see the scale.

Where you genuinely do not have a metric, describe the scope instead: services touched, requests handled, size of the codebase, number of engineers affected. Scope is a legitimate substitute for impact. Inventing a percentage is not, and it fails the moment an interviewer asks how you measured it.

What the ATS is actually looking for

Applicant tracking systems match on the literal terms in the posting. If the posting says "distributed systems" and your resume only says "microservices", a keyword match can miss even though a human would consider them equivalent. Mirror the posting's own vocabulary where it is accurate for you — and only where it is accurate.

Put the skills block above the fold and keep it as plain text. Skills rendered inside tables, columns, or graphics are the single most common cause of a resume parsing into fragments.

Which template suits a software engineer

Single-column and header-anchored contact details, so a long technical history parses cleanly even in older applicant tracking systems.

More about this template

Questions

How long should a software engineer resume be?: One page for under five years of experience, two pages beyond that. Length is not the constraint — relevance is. A second page earns its place only if the older roles still say something the first page does not.
Should I list every programming language I know?: No. List what you want to be hired for and what you could defend in an interview tomorrow. A language you used once in 2019 dilutes the signal and invites a question you cannot answer well.
Do I need a GitHub link?: Only if the profile is worth reading. An active repository with real commits helps; an empty profile with three tutorial forks actively hurts, because the reader clicked expecting evidence and found none.
Where do side projects go?: Below professional experience, and only projects with users or a genuinely interesting technical problem. For career changers with little professional history, promote them above — they are your evidence.