What this role’s resume is actually judged on — the language postings use, what a reviewer looks for in the first ten seconds, and the specific way Backend Engineer resumes go wrong.
A first pass takes seconds and is looking for three things. If they are not near the top, the rest of the page rarely gets read.
Most resumes fail one bullet at a time. The difference is almost always specificity — a number, a constraint, or a consequence.
Developed and maintained microservices in Go.
Made the order pipeline idempotent after a retry storm double-charged 300 customers; reprocessing is now safe and duplicates are zero.
Terms that recur in real postings for this role. They belong in the bullet that proves them, not in a list at the bottom — our own checker weights requirement coverage at 40% and raw keyword matching at 20%, and most serious systems make a similar trade.
A keyword you cannot defend in an interview is worse than a missing one. How the format checks work.
'Built scalable microservices' tells a reviewer nothing — scalable to what? Backend work is judged on magnitude, and a resume without a single throughput, latency or volume figure is indistinguishable from a bootcamp project.
The centre of gravity is data and failure. Expect schema design, idempotency, retries and what happens when a downstream dependency starts timing out at ten percent.
Listing technologies you have touched once
A resume that reads identically to a mid-level one
Abstraction with no anchor
Framework nouns instead of outcomes
Claiming both halves equally
No shipped app anyone can open
Generic resume advice only goes so far — what matters is whether this resume covers this posting. Paste both and get requirement-by-requirement coverage, the keywords you are missing, and the format problems a parser will hit. The first check is free.