How to tailor your resume to a job description
To tailor your resume to a job description, pick the five or so requirements the listing puts first or repeats, and make sure each one is visible in your summary, skills line and top bullets, in the listing's own words where they're true for you. Then cut or shorten whatever doesn't support them.
You don't need to rewrite the whole resume. The top third does most of the work, and twenty minutes per application is enough.
By PickedJobs · Updated · Live figures from 62,231 open jobs, as of (method)
Step 1: Find the requirements that matter
Read the listing once for the role, then again with a highlighter. The requirements that matter most are usually:
- the first three or four bullets under “Requirements” or “What you'll bring”;
- anything mentioned twice, for example in both the summary and the requirements;
- the main technologies in the title or first paragraph (“Senior Go engineer, payments infrastructure”).
“Nice to have” items are tie-breakers. Cover them if you can, but not at the cost of the core five.
Step 2: Match each requirement to evidence
Write a quick two-column map before you edit anything. For a backend listing it might look like this:
| The listing asks for | Your evidence |
|---|---|
| 5+ years building backend services in Go | Four years of Go at your current job plus two years of Python before; say “6 years backend, 4 in Go” |
| Designing APIs used by other teams | The internal billing API used by six teams; move it to your first bullet |
| PostgreSQL at scale | Partitioned a 2 TB events table; name PostgreSQL explicitly |
| On-call and incident response | Led the postmortem process; add one bullet with the outcome |
| Kubernetes (nice to have) | Deployed services on Kubernetes; list it in skills |
Gaps are fine. If a core requirement has no evidence, address it honestly in the cover letter or leave it, rather than stretching a bullet until it's untrue.
Step 3: Use their words, truthfully
Recruiters search their applicant tracking system by keyword, and they skim for the terms in their own listing. If the listing says “Kubernetes” and you wrote “K8s”, use their spelling. Spell out acronyms once. Put skills in the same order the listing does.
These are the technologies named most often in open tech listings on PickedJobs right now; if they're on your resume, write them exactly like this:
| Technology | Open jobs naming it | Share of all jobs |
|---|---|---|
| Python | 25,364 | 41% |
| AWS | 15,663 | 25% |
| Kubernetes | 10,750 | 17% |
| TypeScript | 8,877 | 14% |
| React | 7,886 | 13% |
| Java | 7,031 | 11% |
| C++ | 6,565 | 11% |
| Docker | 6,210 | 10% |
| Terraform | 6,137 | 10% |
| PostgreSQL | 5,871 | 9% |
More in the market statistics.
Step 4: Rewrite the top third
- Headline: match the listing's title if it honestly fits (“Senior Backend Engineer”, not “Software Ninja”).
- Summary: two lines that name your level, your main stack and one result relevant to this role.
- Skills line: the listing's core technologies first, then the rest.
- Latest role: reorder bullets so the ones that prove the core requirements come first.
Step 5: Make the bullets prove it
Each bullet should say what you did, how, and what changed, with a number when you have one: “Cut p95 checkout latency from 900 ms to 250 ms by moving pricing to a cached Go service.” The resume bullet point generator helps turn rough notes into bullets like this.
Step 6: Check before you send
Paste both texts into the resume to job description match tool to see which listing keywords you cover and which you miss. It runs in your browser and nothing is uploaded. Then apply on the company's own site; see whether to apply on the company website or LinkedIn. When the interview comes, prepare with these STAR interview questions for software engineers.