How long should a software engineer resume be?

One page in the US unless you have ten or more years of relevant depth, in which case two is acceptable. In the UK two pages is normal at any level. Length is a convention; keeping every line load-bearing matters more.

Should I include a skills section if I list technologies in my bullets?

Yes. The skills section is what a keyword search hits first; the bullets are the evidence that the skill is real. Use both, and keep them consistent.

Do side projects belong on the resume?

Only when they add something your job history does not — open-source contributions, a product you run, published writing. A tutorial clone adds nothing.

Does the ATS score matter for engineering roles?

Less than for high-volume hiring, because engineers are often screened by a human who reads the resume properly. It still matters for large employers and for any role filled through a portal.

US resume & UK CV

Software engineer resume: what hiring teams actually scan for

A software engineer resume is judged on three things in the first ten seconds: the stack, the scale of what you built, and whether you owned it.

Build my resume Check it free

Job titles this covers

Summit

Software Engineer
Backend Engineer
Full Stack Developer
Frontend Engineer

Dense, single-column, projects-friendly — it fits a stack list and three roles on one page without shrinking the type.

Starts from the recommended template
Section order matches this role
Export as Letter or A4

What this document has to prove

Engineering resumes fail in a specific way: they list technology without evidence of consequence. "React, Node, AWS" tells a reader nothing about whether you shipped anything that mattered. The hiring manager is scanning for someone who has solved a problem close to theirs, at a comparable scale.

This guide covers the structure that survives a parser, the keywords a recruiter actually searches for, and the bullet shape that survives a technical screen — in both US resume and UK CV conventions.

What a recruiter searches for

These are the terms a hiring team filters on. Include the ones that are true of your work — our checker tells you which are missing, it never inserts them for you.

Programming languages: Write the ones you would be comfortable being interviewed in. Both the acronym and the name once (JavaScript, TypeScript).
Frameworks and libraries: Match the advert exactly: "React" and "React.js" are read the same by a human, but mirror the advert where you can.
Infrastructure: AWS, GCP, Azure, Kubernetes, Docker, Terraform — cloud and container tooling is one of the most common hard filters.
System design vocabulary: Distributed systems, event-driven, message queues, caching, latency, throughput. Use it where it is true of your work.
Testing and delivery: CI/CD, unit testing, integration testing, code review, incident response.
Scale figures: Requests per second, records, users, services, data volume. This is what separates a junior bullet from a senior one.

How to write it, section by section

Structure that survives the parser

One column, standard headings, no skill matrices or dot ratings. Contact details as plain text in the body — a GitHub or portfolio URL belongs there too, as a real link, not an icon.

Header: name, city, email, phone, GitHub or portfolio.
Summary: two or three lines — specialism, stack, and one proof point.
Experience: reverse chronological, most relevant work first within each role.
Projects: only if they add something the job history does not (open source, side products, published work).
Skills: grouped by language, framework, infrastructure, tooling. No proficiency bars.
Education and certifications: brief unless the certification is a hard requirement.

The bullet shape that gets read

Every strong engineering bullet answers: what did I build, with what, at what scale, and what changed as a result. Engineers are usually good at the first two and skip the last two — which is exactly what the reader needs.

Weak: "Worked on the payments API using Node and Postgres."
Stronger: "Rebuilt the payments API in Node and Postgres, adding idempotent retries that removed duplicate charge incidents."
Best: "Rebuilt the payments API in Node and Postgres; idempotent retries removed duplicate-charge incidents and cut support tickets on the checkout flow by a measurable margin."
Team work: "Part of a four-engineer team migrating 30 services to Kubernetes; I owned the deployment pipeline and rollback strategy."

Keywords, honestly

A recruiter searching a database types the stack, then a specialism, then a seniority marker. If your resume describes your work in different vocabulary than the advert uses, you can be a strong fit and still never surface.

Mirror the advert's language where it is genuinely accurate — "backend services" instead of "server-side code", the exact cloud provider, the exact framework. Do not add a technology you have only read about. An interview panel will find out in the first ten minutes.

US resume vs UK CV

The engineering content is the same in both markets; the packaging differs. US: Letter paper, one page unless you have genuine depth, no photo, no date of birth, US spelling. UK: A4, two pages is normal, a short personal statement at the top, British spelling (optimise, not optimize).

Wherever you are applying, keep the GitHub link alive and representative — a stale profile with three half-finished repositories is worse than no link.

When you have gaps in the stack

Job adverts list the ideal candidate, not the minimum. If you meet most of the requirements and the missing one is learnable, apply — but say what you do have rather than hoping the gap is not noticed. "No production Kafka experience; built an equivalent event pipeline with SQS and documented the migration trade-offs" is an honest sentence that reads as engineering judgement.

Mistakes that end the first read

Each of these is common in this role specifically, and each one costs a real application.

Listing twenty technologies you have touched once, with no evidence for any of them.
Bullets that describe responsibilities ("responsible for backend services") instead of outcomes.
Skill bars, percentage ratings or star systems — invisible to parsers, meaningless to humans.
Two-column layouts with a skills sidebar; parsers interleave the columns.
A GitHub link that lands on an empty or abandoned profile.
Claiming senior-level scope while describing junior-level work — the mismatch is the first interview question.

Questions people ask

How long should a software engineer resume be?: One page in the US unless you have ten or more years of relevant depth, in which case two is acceptable. In the UK two pages is normal at any level. Length is a convention; keeping every line load-bearing matters more.
Should I include a skills section if I list technologies in my bullets?: Yes. The skills section is what a keyword search hits first; the bullets are the evidence that the skill is real. Use both, and keep them consistent.
Do side projects belong on the resume?: Only when they add something your job history does not — open-source contributions, a product you run, published writing. A tutorial clone adds nothing.
Does the ATS score matter for engineering roles?: Less than for high-volume hiring, because engineers are often screened by a human who reads the resume properly. It still matters for large employers and for any role filled through a portal.

Related roles

Build a software engineer resume in the builder

Fill in the real details, let the checker tell you what is missing, and export a text-based PDF when it reads cleanly.

Start building free Check my resume

No credit card · Unlimited manual editing · Your documents stay private