Software Engineer resume example
Also indexed as: software developer · backend engineer · full stack engineer
Engineering resumes fail in a specific way: they list technologies and omit consequences. A recruiter screening forty applications reads the first line of each bullet, and "responsible for maintaining the payments service" tells them nothing about whether you are good at it. The engineer who wrote "cut p99 settlement latency 71% by replacing synchronous fan-out with a batched outbox consumer" gets the call, even when both people did the same work.
The other half of the problem is the index. Engineering requisitions are matched on stack, scale and domain (Go, Kubernetes, event-driven, payments, multi-tenant), and if those words appear only in a skills list at the bottom, the match is weak. Put them where you used them, inside the bullet that describes the work.
A complete document in the Meridian family of layouts, rendered live, not a screenshot.
The screen
What a software engineer resume is actually judged on
Scale, stated in numbers
Requests per second, data volume, team size, number of services owned. "High-traffic" means nothing; 9,200 writes per second means something.
Ownership, not participation
Did you design it, ship it, and carry the pager for it? "Contributed to" and "assisted with" read as junior even when the work was not.
The stack in context
Naming Kafka in a skills list is weaker than naming it in the sentence about the pipeline you built with it.
Bullets
6 bullets that would survive the screen
Copy the shape, not the words. Each one leads with the result, then names the mechanism, and carries the vocabulary of the field without listing it.
Rebuilt the double-entry ledger on an append-only event store, lifting sustained throughput from 400 to 9,200 writes per second with exact balance reconciliation.
Led the shard migration of 42M accounts off a single Postgres primary across six weeks with zero customer-visible downtime and no rollback.
Cut p99 API latency 71% (2.4s to 690ms) by replacing synchronous fan-out with a batched outbox consumer.
Reduced infrastructure spend 34%, or $780K annualised, by moving cold objects to tiered storage behind a signed-URL cache.
Designed the multi-tenant isolation model that unblocked $3.1M of enterprise ARR held up in security review.
Mentored four engineers through the promotion process; two reached senior within eighteen months.
The rewrite that matters most in this role
Responsible for improving the performance of backend services.
Cut p99 checkout latency from 2.4s to 690ms by batching a synchronous fan-out into an outbox consumer, holding the gain through a 3× traffic increase.
Why it works: The weak version describes a job description. The strong one names the metric, the delta, the mechanism and the durability of the result, and it carries the keywords a platform requisition indexes on without listing them.
Skills
Skills worth listing as a software engineer
Only what you would be comfortable being interviewed on. A long list dilutes every real match.
Technical & role-specific
Worth proving, not claiming
These belong inside a bullet that demonstrates them, not in a list. A line that says “communication” is worth nothing; a bullet showing you ran the workshop is worth a lot.
Keywords
What the tracking system is indexing
These are the terms a requisition for this title typically matches on. Use the ones that are true of you, inside the sentences where you did the work.
Paste the actual posting into the builder and you get this list generated from that requisition instead of the general case, including which terms you are already carrying and which bullet is the right home for the rest.
How keyword targeting worksMistakes
Errors specific to software engineer resumes
Not the generic advice. These are the ones that cost people interviews in this particular field.
A skills wall with thirty technologies
It reads as padding and it dilutes every real match. Keep the ones you would be comfortable being interviewed on, and let the bullets carry the rest.
Projects that are tutorials
A to-do app and a clone of an existing product tell a reviewer nothing. One project you actually maintained, with a user count or a problem it solved, is worth five.
Burying the impact at the end of the bullet
Scanning happens on the first six words. Lead with the result, follow with the mechanism.
Questions
Software Engineer resume questions
How long should a software engineer resume be?
One page under ten years of experience, two beyond that. Nobody has ever been rejected for concision; plenty have been skimmed past because page two was a list of technologies.
Do I need a GitHub link?
Only if the profile is worth opening. An active repository with real commits helps; an empty account with three forks is a broken promise and reviewers do check.
What if my numbers are confidential?
Use relative figures: "cut latency 71%" rather than the absolute request volume. Percentages, multiples and orders of magnitude carry the signal without leaking anything.