How to Tailor a Resume to One Job Posting

Why a generic PDF loses

Recruiters compare your page to one posting, not to your whole career. If the posting asks for GST and Excel and those words only appear in a buried internship, the match looks weak even if you did the work. Tailoring isn't lying. It's ordering and naming.

Twenty minutes, four passes

1. Print or split-screen the job description. Highlight tools, methods, and must-have duties.
2. Rewrite the summary so the first sentence names that job family (analyst, coordinator, nurse) and one matching tool.
3. In each relevant role, move the matching bullets to the top. Cut bullets that belong to a different kind of job.
4. Add missing tools to Skills only if you can discuss them. Export a PDF named for that company if you like, and keep a master file in MineResume for the next application.

Example

Posting: “Junior accountant — Tally, bank recs, GST.” Your master resume leads with a retail job. For this file, lead the accountant internship, put Tally in Skills, and write one bullet on reconciliations. Keep the retail job shorter.

What not to do

• Don't copy the posting paragraph into your summary.
• Don't add a keyword in white text.
• Don't submit the same two-page file to a one-page campus drive.

The arithmetic that makes twenty minutes worth it

Sit with the numbers for a second. A recruiter spends ten seconds on your page before deciding it's worth ten minutes. Those ten seconds are spent comparing you to the posting, not to some abstract standard of "good resume." Which means the same document, same facts, same career, can screen as a 60% match on one day and a 90% match the next — purely because of ordering and naming. Twenty minutes of tailoring per application feels expensive when you've got forty openings in your tabs. It isn't. Forty generic sends with a 3% callback rate gives you about one interview. Fifteen tailored sends at 10-12% gives you the same one or two interviews, with less volume, less rejection, and files you can actually defend on a call. The tailoring isn't the cost; the blind applying is. Our job search system article builds this into a weekly pipeline, and this method is the unit task inside it.

Pass one properly: extract, don't just highlight

"Highlight keywords" is the advice everyone gets and nobody executes well, because highlighting everything is the same as highlighting nothing. Force the extraction into three columns on a scrap of paper or a note app. Column one: the nouns the posting repeats — tools (Tally, GA4, Epic), artifacts (BRD, reconciliations, discharge summaries), and team types. Column two: the verbs it uses for the work — own, support, drive, maintain, coordinate. These matter because they're the verbs your bullets should steal. Column three: the must-haves with hard edges — "2+ years," "BSc required," "night shift willingness." Anything in column three that you don't have is a qualification decision, not a writing problem; find out before you spend twenty minutes polishing for a rejection. Do this on the actual text of the posting, not the job title. "Financial Analyst" at one company is Excel and forecasting; at the next it's SQL and dashboards. The description tells you which one this is.

Rewrite the summary for one posting (worked example)

Watch the same real background bend to two different asks. Person: two years at an IT services firm, mostly support tickets plus some internal Excel automation. Posting A (Business Analyst): "Junior BA needed; documentation, stakeholder meetings, SQL helpful." Summary A: "Support engineer moving into business analysis — two years documenting recurring issues into SOPs, running weekly call checks with a US client team, pulling ticket reports in SQL." Posting B (Data Associate): "Reporting associate; Excel, dashboard maintenance, attention to detail." Summary B: "Reporting-focused IT associate — built and maintained the team's Excel escalation dashboards (pivot tables, VLOOKUPs) used daily by two managers for two years." Same person. Nothing invented. Each version simply puts the true thing the posting wants inside the first sentence, the way the summary guide prescribes. Notice both also carry a number, because a summary without a quantity is just a sentence wearing a suit.

Reorder and rename, never rewrite history

Inside each job entry you get three honest moves and no others. Move: the bullet that matches the posting goes first, because first bullets get read and third ones don't. Cut: the bullet that belongs to a different career — the event-organizing line doesn't help an accounting application, and a screener feels the mismatch even when you can't name it. Rename: your official title can carry a market translation in parentheses when the internal name is noise ("Associate II — Billing Pod (Accounts Receivable Analyst)"). What isn't on the menu: changing dates, promoting yourself a level you never reached, claiming a tool you touched in one training session, or making an eight-month internship sound like two years. Every one of those survives the resume and dies at the reference check or the joining-form stage, and the cost of getting caught is bigger than the cost of the job you didn't get.

The audit before you export

Three checks take five minutes and catch almost every tailoring sin. One: search your file for each column-one noun from the posting. Present and true — fine. Present but false — delete it; you just talked yourself into something you can't defend. Absent but genuinely true somewhere — now you have a place to put it. Two: run a diff against your master file, literally or mentally. The changes should read as reordering, renaming, and cutting — if you see a new fact, stop and ask whether it's true or just eager. Three: read the whole page in thirty seconds as if someone else wrote it. Does a stranger know within five words of the summary which job you're aiming at? If the answer is "maybe," the summary still names your past instead of your target. The pre-upload checklist covers the file-level mechanics after this content audit passes.

Two postings that want opposite things

You will hit weeks where the same background needs three different resumes: a data-analyst application wants SQL loud, an operations application wants process ownership loud, and a completely different industry wants neither word near the top. The trap is one "compromise" file that leads with both, reads as confused, and matches neither. The workflow that works: keep one master with every true bullet ever earned, in every vocabulary you've developed. Per serious application, duplicate it, tailor the copy, and export with a name that tracks the target — Firstname_Lastname_Analyst_Company.pdf. Keep the copies. Not for re-use, for memory: when a recruiter three weeks later asks "what did you apply as?" you can open the exact file they saw and speak to it. That consistency is its own credibility signal, and it's how the builder's duplicate-and-export flow is meant to be used.

Why switchers and freshers must tailor harder

If your job titles and history already match the posting, tailoring is housekeeping. If they don't, tailoring is the entire argument. A career changer has one paragraph — the summary plus the first bullet of one job — to connect the old world to the new one, which is exactly the craft covered in the career-change article. A fresher has even less raw material, so every true detail carries weight: the project that used the posting's named tool, the coursework that matches the must-have list, the part-time job where you actually owned money or people or deadlines — see the fresher guide for placing them. For both groups, the rule flips from "tailoring helps" to "tailoring is the difference between two documents with the same facts, one of which reads as a fit." The facts rarely change between those two documents. The order and the nouns do.

One more thing: the same posting deserves a second read

Read the posting twice, and put the second pass on the responsibilities rather than the requirements. The requirements section is written by committee and padded with wish-list items; the responsibilities paragraph is what the hiring manager actually needs done in the first ninety days. When those two lists disagree about what matters — requirements say AWS, responsibilities say "maintain the reporting nobody else wants to do" — trust the responsibilities. That's the human signal inside the keyword noise, and it tells you not just which words to place but which achievement to lead with. This is the one tailoring skill no ATS cheat-sheet can hand you, because it isn't about the machine at all.

More structure: our guides on ATS format and summaries.