How to write a resume that survives the first thirty seconds
Most resumes are read in under a minute on the first pass. Here is what actually gets read, what gets skipped, and how to structure yours accordingly.
7 min read· 25 Aug 2026· The Growtriz team
A recruiter reviewing a shortlist reads your resume differently to how you wrote it. They scan for a small number of signals — current title, years, the two or three skills the role requires, and whether your last few roles form a coherent story.
Start with the summary, but make it specific. "Experienced professional seeking opportunities" tells a reader nothing. "Backend engineer, five years, mostly payment systems in Go" tells them whether to keep reading.
Lead each role with outcomes rather than duties. "Responsible for the checkout service" describes a job description. "Cut checkout latency from 800ms to 240ms, which raised conversion by 4%" describes what you did with it. The second version is also much harder to write, which is exactly why it stands out.
List skills you would be comfortable being interviewed on. Padding the list dilutes the signal and creates an unpleasant interview when someone picks the wrong one.
Finally: keep it to two pages, use a format that survives being parsed by software, and check the dates. A surprising number of otherwise strong resumes have a gap the candidate cannot explain because they simply typed the wrong year.
Put it to use
Every role on Growtriz shows its salary range up front, so you can tell whether it is worth your time before you write a word.
Browse open roles