Everyone says tailor your resume. Almost nobody says what to change, so most people either rewrite the whole document and burn out after four applications, or swap two words and call it tailored.
Both are wrong for the same reason. Tailoring is not rewriting. Four things on your resume carry nearly all of the role specific signal. Change those, leave the rest alone, and the whole thing takes about twenty minutes.
What tailoring actually means
Tailoring is not writing a new resume. It is taking the same true facts about you and reordering and renaming them so the person reading can see the fit without working for it.
You did the same internship whether you are applying to a data role or a product role. What changes is which part of it goes first, and which words you use to describe it. The data posting cares that you built the pipeline. The product posting cares that you ran the stakeholder review and shipped on time. Same eight months, different first sentence.
Tailoring changes the emphasis, never the facts. The moment it changes the facts it stops being tailoring and starts being a problem.
The four things worth changing
Ranked by how much they move the outcome per minute spent. If you only have ten minutes, do the first two.
1. The two lines at the top
The top of page one gets more attention than everything under it. If you have a summary, it should name the target role and carry three or four terms from the posting. If you do not have one, this is the single highest return thing to add, but only if you will actually rewrite it each time.
Motivated computer science student with strong problem solving skills seeking opportunities to grow in a fast paced environment.
Third year software engineering student targeting backend internships. Built two production Python and PostgreSQL services, one serving 4,000 monthly users. Comfortable owning a feature end to end.
The first version could belong to anyone applying to anything. The second one tells a recruiter, in four seconds, whether to keep reading.
2. Section order
Whatever is most relevant to this posting goes highest. For a research role, Projects can sit above Experience. For an operations role, put the part time job with real responsibility above the personal project. Nothing says the order has to be the same every time, and reordering costs you thirty seconds.
3. The first two bullets of your most relevant role
Not all of them. The first two. Those are the ones that get read on a scan, and they are where the posting's vocabulary belongs. Bullets three through six can stay exactly as they are across every application.
4. The skills list
Reorder so the terms from this posting come first, and drop anything irrelevant to this role. A skills line that opens with the three things the job asked for looks targeted. One that opens alphabetically looks like a template.
That is the whole edit. Your education, your older roles, your formatting, your contact block: untouched.
The twenty minute process
- 1
Pull the terms (7 minutes)
Strip the posting down to the title, requirements, and first three responsibility bullets. Pull the eight to twelve nouns that repeat or sit in the requirements block. Full method in the ATS keywords guide. - 2
Rewrite the top two lines (4 minutes)
Name the exact role from the posting. Put three of your pulled terms in. Add one number that proves you have done the thing. - 3
Reorder sections (1 minute)
Most relevant block goes highest. That is the entire step. - 4
Rewrite the top two bullets of your lead role (5 minutes)
Use the posting's word for work you already did. Keep the number that was already in there. If there is no number, add one now. - 5
Reorder the skills line (1 minute)
Posting terms first, irrelevant ones deleted for this version. - 6
Read it once at scan speed (2 minutes)
Look at it for eight seconds the way a recruiter would. Can you tell which role it is for? If not, the top two lines are still wrong. Go back to step two.
Twenty minutes. Compare that to the fifteen to thirty minutes people spend retyping their address and graduation year into a Workday form, which changes nothing about whether they get called.
How much is enough
The number people ask about is match percentage. Most tools that score this describe a strong match as roughly seventy to eighty five percent overlap with the posting, and treat anything under about sixty percent as likely to be filtered out or simply never surfaced.
Useful, with two caveats.
First, the score is a proxy, not a verdict. A resume at sixty five percent with three specific, quantified bullets beats a resume at ninety percent that is a keyword pile. The score gets you looked at. Evidence gets you called.
Second, chasing a high number is exactly how people end up stuffing. If getting from seventy five to eighty eight percent requires adding tools you have used once, you have traded a real interview for a fake match.
Practical target: get the required qualifications covered honestly, get three or four of the preferred ones if they are true, and stop. Then spend the remaining time on whether your bullets prove anything, which is covered in the bullet points guide.
Build a bullet bank so it gets faster
The reason tailoring feels unsustainable is that people rewrite from scratch every time. You should be writing each bullet once, in two or three versions, and then picking.
Keep one document. For each real thing you have done, store:
- The technical version, leading with the stack and the mechanism.
- The impact version, leading with the number and the outcome.
- The collaboration version, leading with who you worked with and what shipped.
Same project, three angles. When a backend posting comes up you take the technical version. When a product posting comes up you take the impact version. No writing, just selection.
Do the same for the questions that repeat across applications. Why this company, why this role, tell us about a challenge. I filled out more than 400 applications before I built any of this, and roughly forty questions repeated in every single one. Writing the good version once and reusing it is not cutting corners. It is the only version of this that scales.
By the tenth application, tailoring is about eight minutes. By the twentieth it is five.
Mistakes that make tailoring backfire
- Changing the job title on your own past roles. Tempting, and it is a reference check failure waiting to happen. Change how you describe the work, never the title you actually held.
- Tailoring the resume and not the file name.
resume_final_v7_stripe.pdfgoing to a different company is a small thing that reads very badly. UseFirstname-Lastname-Resume.pdfevery time. - Rewriting the whole document. You will do it four times and then stop tailoring entirely. Four sections is the sustainable version.
- Tailoring content while ignoring format. If the parser is mangling the file, none of this reaches anyone. Check what actually breaks the parser first.
- Tailoring when the resume is not the problem. If you are getting first rounds and no offers, more tailoring changes nothing. Diagnose the stage you are stuck at before optimising the wrong one.
Do the four things, keep the bank, and stop treating every application as a blank page. The goal was never a perfect resume. It was a resume that makes the fit obvious in eight seconds to someone who is tired and has 900 more to get through.
Common questions
- How long should tailoring a resume actually take?
- Around twenty minutes once you have a strong base resume and a saved bank of alternate bullets. The first two or three take longer because you are building the bank. If a single application is costing you an hour, you are rewriting rather than tailoring.
- What keyword match percentage should I aim for?
- Most tools describe a strong match as somewhere between seventy and eighty five percent overlap with the posting. Below about sixty percent you are likely invisible in recruiter searches. Above about eighty five percent you are usually forcing terms in, which a human reader notices immediately.
- Should I keep one resume or make a different one for every job?
- Neither extreme. Keep one strong base resume plus two or three role variants, then tailor four specific things per application. Maintaining twenty separate files is unmanageable and you will eventually send the wrong one.
- Is it worth tailoring for every single application?
- For roles you actually want, yes. For a wide net of long shots, tailor the four things listed here and move on. Twenty tailored applications beat two hundred generic ones, because a generic resume fails the same filter two hundred times in a row.
- Do I need a summary section at the top?
- Optional, and only worth it if you will actually rewrite it per role. A generic summary is wasted space in the highest attention part of the page. A two line version naming the target role and three relevant terms is one of the fastest tailoring wins available.
Stop retyping the same application.
Save your answers once. ApplyAgents fills Workday, Greenhouse, Lever, and more.
Get 3 autofills freeNo credit card. You always click Submit.