Adapt a resume to one job description by matching evidence to the work, not by copying every phrase.
Harvard recommends tailoring the resume to the position. The practical map here is an editorial method for doing that transparently.
A practical method
- Save the specific posting and highlight essential tasks, tools, outcomes, and constraints.
- Rank the top three requirements by emphasis and evidence you possess.
- Map each requirement to a concrete job, project, or training example.
- Reorder the summary and bullets to surface the strongest matches; leave unsupported gaps visible rather than disguising them.
- Check the final version against the posting and confirm every term is accurate.
Worked example: from first attempt to usable result
- Task: Adapt a resume to one job description by matching evidence to the work, not by copying every phrase.
- First output/attempt: Copying a posting’s keywords into a skills block even though the candidate has never used the named tool.
- Mistake/weakness: Keyword copying creates claims that fail follow-up questions and does not show the reader where the capability was applied.
- Human correction: Build a requirement-to-evidence map, use the employer’s wording only when it describes genuine experience, and identify adjacent evidence honestly where a direct match is missing.
- Quality check: For each prominent requirement, locate one true example. Circle terms that appear only in the posting; remove them unless you have supporting proof. Illustrative match table: 3 of 5 high-priority requirements had direct evidence; the other 2 stayed marked as gaps.
- Final usable result: Posting asks for monthly reporting and Excel. Resume evidence: “Prepared monthly service-volume summaries in Excel and flagged recurring backlog categories for supervisor review.”
- Resume bullet: Illustrative resume bullet (use only if true): “Matched verified experience to vacancy requirements and documented direct, adjacent, and developing skills.”
A completed direct / adjacent / missing map
| Posting requirement | Evidence status | Final edit decision |
|---|---|---|
| Monthly Excel reporting | Direct: saved report template and task notes show pivot-table summaries. | Keep the exact Excel task in the recent experience bullet. |
| Salesforce case queues | Adjacent: candidate used another case-management system and can describe comparable queue work. | Say “case-management queue,” name the actual system, and do not claim Salesforce. |
| SQL querying | Missing: no coursework or work sample supports it. | Do not add it as a skill; list it as a gap in the private application note and decide whether to learn or target a different role. |
Before submission, verify the report claim against the saved template and experience notes. Record the posting URL/date, final file name, and any requirement deliberately left out; the illustrative “three rows reviewed” is an editing record, not a fit score.
A beginner exercise you can complete today
Use one posting to create a five-row match table: requirement, evidence, wording to use, gap, and next action. Keep it with the tailored file so you can explain every choice.
Pass check: Produce one dated copy and a five-row evidence map. Pass when every mandatory requirement is addressed truthfully, the first third shows the strongest match, and no copied term lacks a proof source. Keep the posting, map, and final draft so you can repeat the process for the next vacancy.
Frequently asked questions
Should I copy the job-description wording?
Use exact terms when they truthfully name your work. Do not claim an unfamiliar tool or task to match a phrase.
Do I need to rewrite every bullet?
No. Prioritize the summary, top relevant bullets, and skills; keep other accurate experience concise.
Decisions that change the approach
Tailoring means selecting and ordering relevant proof, not copying the posting. Extract requirements as verbs and outputs: analyze what, coordinate whom, maintain which records, or deliver which service. Then match each requirement to an example. Where you have adjacent experience, name the connection without pretending it is identical. Where evidence is absent, decide whether to build a sample or pursue a different vacancy.
| Situation | What to inspect | Next decision |
|---|---|---|
| Direct match | Same kind of task and comparable context. | Use precise shared language and show the example. |
| Adjacent match | Similar method, different field or audience. | Explain the transfer; do not imply identical scope. |
| No evidence | No work or sample supports the requirement. | Mark the gap and choose a learning or application decision. |
A keyword list is not a substitute for tailoring. Keep the vacancy’s exact technical term when it is true, and spell out common acronyms once if they may be unfamiliar. Do not claim a software product because the posting asks for it if you have only used a competitor; describe the transferable workflow and learn the named tool separately.
Prioritize requirements when space is limited
Suppose an operations-coordinator posting names accurate case notes as required, Excel as preferred, and a particular CRM as a plus. Preserve any mandatory credential or authorization first. Then rank duties repeated in the summary and responsibilities. A candidate with verifiable case documentation and spreadsheet reports can lead with those examples. If they have never used the CRM, leave it out of the skills list and record the gap privately.
When ten preferred items compete for space, give each a relevance score only after checking evidence: direct, adjacent, or absent. Use recent direct proof before a weaker keyword match; do not delete dates or required application-history fields. A short practice task may show willingness and current learning, but it is not prior experience with the employer’s system. Keep the factual history stable while changing order, emphasis, and wording to suit the posting.
Choose a practical next step
Use this to select accurate terms after ranking requirements. the resume-keywords guide. Use this to decide which proven capabilities belong in the skills section. the resume-skills guide.
Tailor the evidence, not the facts
Suppose a posting repeats “case documentation,” “cross-functional coordination,” and a named CRM. Highlight the first two only if your work supports them. If you used a different case system, describe the transferable task—recording status, ownership, next step, and resolution—then name the system you actually used. Do not replace its name with the employer’s tool. A hiring reader may ask what you did inside that product, and a false match is difficult to defend.
Use a three-column requirement map: phrase in the posting, your evidence, and edit action. “Coordinate with billing” could map to a real handoff you performed; the edit action may be to move that bullet higher, not rewrite the work into something stronger. “Five years of experience” is a time requirement, not a keyword to repeat. If you do not meet it, do not manufacture seniority; decide whether the posting allows equivalent experience or whether another role is a better fit.
Expected tailored version: the summary names the target function; the first few bullets surface the strongest truthful evidence; the skills list uses matching terminology only where accurate. A second version for another vacancy may reorder the same verified facts. The master document stays private and broad; the submission file is selective.
After editing, compare the old and new versions against the posting. Check that every added phrase has a proof location and that no useful evidence disappeared simply because it did not match one line of the ad. Preserve a copy of the posting with the application record so you remember which version and terms you used.
A final practical boundary
Use a simple version-control rule: one master file for verified history, then a named submission copy for each role. Keep the job title and date in the file name or application log, not inside a claim that changes the underlying facts. After tailoring, compare the submission copy with the master and check dates, titles, credential status, and ownership language. A targeted version should emphasize different true evidence—not make the same candidate appear to have different qualifications.
Sources
- Harvard College Guide to Creating a Strong Resume — Harvard recommends specific, active, fact-based resume language, tailoring to a position, clear organization, and checking how a PDF converts. Checked 2026-10-17.
- University of Michigan University Career Center: Resume Resources — Michigan recommends consistent scannable formatting, reverse chronology within sections, tailored experience, and bullets that add what/how/why or impact; its one-page suggestion is specifically for most undergraduates. Checked 2026-10-17.
- UC Berkeley Career Engagement: Resumes — Berkeley recommends matching resume evidence to required and preferred qualifications and focusing on results, transferable skills, and targeted accomplishments; its one-page advice is specifically for students. Checked 2026-10-17.