Software engineer resume example

A one-page resume for a senior backend engineer: two jobs, six results with numbers, and tools named where they were used.

Fictional example, drawn by the same engine that builds the PDF.

Why this resume works

Every achievement has a before and an after
“p99 latency went from 180 ms to 25 ms” tells the reader the size of the change. “Improved performance” would not.
Tools appear inside the work
TypeScript, PostgreSQL and Redis are named in the achievements where they mattered, and again in the skills section. A reader sees the tool and the proof together.
The summary is specific
It gives years of experience, the stack, the scale of the latest system and what the person wants to own. No adjectives such as “passionate” or “results-driven”.
Skills are grouped, not ranked
Three short groups (languages, backend, infrastructure) with no bars or percentages. Self-assigned skill levels say nothing a reader can verify.
One side project, with its purpose
A single project with one sentence on what it does is worth more than a list of repository names.

Replace each achievement with one of yours in the same shape: verb, what you changed, the number before and after.
If you have no production numbers, use counts you do know: users, requests, team size, time saved in a release.
Order the skill groups by what the job posting asks for first.
For under three years of experience, move Projects above Experience in the section order.

When your version is ready, paste the job posting into the resume check to see which of its terms your text does not mention yet.

With under ten years of experience, yes. Keep three or four results for the two most recent jobs and one line for anything older.

No. List what you could discuss in an interview and what the posting asks for. Long lists dilute the ones that matter.

Only if the profile shows work you want read. An empty or outdated profile is better left out.