How to write a resume that gets shortlisted
Most resumes don't get rejected because the candidate is unqualified. They get rejected because a recruiter spent seven seconds on them and couldn't tell. Here's how to fix that, in the order it actually matters.
Mirror the job description's own words
Recruiters skim for a handful of things: your most recent title, your years of experience, and two or three skills the job description names explicitly. If the job asks for "React" and your resume says "modern JavaScript frameworks," you've made the recruiter do the matching in their head — and on a stack of a hundred resumes, they won't.
Read the job description line by line and use its exact terms for the skills and tools you actually have. Not every skill, and never one you don't have — just the ones that are true and that the posting names. This is the single highest-leverage change most resumes need.
Lead every bullet with what changed, not what you did
"Responsible for managing the sales pipeline" tells a recruiter your job title, which they already know. It doesn't tell them anything about you. Compare:
- Responsible for managing the sales pipeline
- Rebuilt the sales pipeline process, cutting average deal cycle from 41 to 26 days
The second version is a claim a recruiter can picture and a hiring manager can ask about in an interview. It doesn't need to be a huge number — a small, specific, honest result beats a vague, sweeping one every time.
Put the last three years first, literally
Recruiters read top to bottom and stop early. Your most recent and most relevant role belongs at the top, with your strongest, most quantified bullets first within it. Older or less relevant roles can be a single line each — you don't need to account for every year in equal detail.
Keep the format boring on purpose
Multi-column layouts, tables, icons and text boxes look sharp to a human eye and are frequently mangled by resume parsers, including the one behind your own profile here. A single column, standard section headings (Experience, Education, Skills), and a normal reading order will parse cleanly everywhere — on this platform and everywhere else you apply. Save the visual personality for a portfolio site, not the file that has to survive a parser first.
One page, unless you have a genuine reason not to
Under roughly eight years of experience, one page is almost always right — length isn't a proxy for value, and a tightly edited page reads as someone who can prioritize. If you're past that, two pages is fine; three rarely is.
Proofread it as if someone else wrote it
A typo in a resume doesn't just look careless — for a role where writing or attention to detail matters, it's read as direct evidence against you. Read it out loud, or read it backwards by section. Both catch things a normal read-through skips.
None of this replaces having a profile employers can actually search and apply against — it just makes sure the first seven seconds go your way once they find it.