JD tailoring
How to tailor your resume to a job description
Tailor your resume with a requirement-to-evidence checklist. Learn what to reorder, what to rewrite and how to handle requirements you cannot support.
By Resume Home · Updated . Illustrative examples are fictional: replace sample identities and experience with your own facts before applying.
In short
To tailor a resume, read the job description, identify the work and qualifications it asks for, and connect those requirements to evidence from your own experience. Reorder and clarify relevant content while keeping the underlying facts unchanged. Review requirements you cannot support instead of adding them as skills you do not have.
Key takeaways
- Read the work the posting describes, then map each requirement to something you actually did.
- Change emphasis before adding content: reorder, choose the right bullets and use the posting's terms only when they are true.
- Check every edit against the original fact, then read the final file once without the posting beside it.
1. Read the work, not just the job title
Identify the tasks the role will perform, the skills it names and the evidence the employer asks for. Separate stated requirements from preferences where the posting makes that distinction. If the wording is ambiguous, keep that uncertainty visible rather than pretending to know the employer's screening policy.
Look for repeated responsibilities and concrete deliverables. A frontend role asking for design collaboration and accessible forms gives you a different emphasis from a role mainly asking for data visualisation. Do not assume all jobs with the same title want the same resume.
2. Map each requirement to something you actually did
Make a small working checklist with the requirement, your evidence and a possible edit. Use your projects, employment, education and volunteering as appropriate. Distinguish direct experience from related experience and from a genuine gap.
3. Change emphasis before adding more content
Bring the most relevant experience into view. Reorder projects, choose the bullets that demonstrate the role's responsibilities and make the summary specific to the work you can support. Keep dates, employers and the level of your responsibility accurate.
Use the posting's terminology when it is a truthful description of the same work. Naming React is appropriate if you used React. Replacing a tool you used with a different tool from the posting is not tailoring. Avoid repeating keywords without explaining what you did with them.
Before
Built a dashboard for a course project.
After
Built the project's React dashboard and worked with a designer on form layouts.
Why it works: This wording highlights relevant tools and collaboration, assuming both details are in the applicant's actual experience.
4. Check the evidence behind each change
Review each rewrite against the original fact, not against how polished it sounds. Check whether the edit adds a number, implies ownership of a team result or changes the context. If an important contribution was left out, add a specific description of it; if a sentence describes experience you do not have, remove it. Tailoring should make relevant experience clearer without creating new qualifications.
5. Review the application you will send
Read the final document once without the job description beside it. It should still make sense as a clear account of your experience. Then compare it with the posting again to see whether the relevant evidence is easy to find.
Check contact details, employer names, dates and exported formatting. Follow the submission instructions. Keep track of the version you sent so that your interview preparation uses the same claims.
Before-and-after resume tailoring examples
Both examples are fictional and assume every detail in the revised version is already in the applicant's experience. Tailoring changes what leads and what is left out; it does not add what is not there.
Before
Software developer with experience in web applications.
After
Frontend developer who builds accessible React forms and works closely with designers.
Why it works: The summary now leads with the two things the posting asks for most, both drawn from the applicant's own projects.
Before
Skills: JavaScript, HTML, CSS, Git, Python, Excel, React
After
Skills: React, JavaScript, HTML, CSS, Git, Python
Why it works: React, which the posting names, moves to the front; Excel, unrelated to the role, is dropped. Nothing new is claimed.
Put these ideas into practice
Tailor a resume to a job description
Bring your resume and job description together, review suggestions and choose which changes to use.
Try itShould you apply if you don’t meet every job requirement?
Separate missing evidence from missing experience: show transferable skills, describe related work and handle real qualification gaps honestly.
Read moreResume bullet points: examples, action verbs and writing tips
Turn responsibilities into clear resume bullet points. See three before-and-after examples, evidence prompts and ways to write honestly without metrics.
Read moreHow to turn your resume into a tailored cover letter
Turn resume facts into a cover letter that explains fit for one job. Includes a fact-to-paragraph example, a complete fictional letter and a final checklist.
Read moreHow to make an ATS-friendly resume
Make your resume easy for applicant tracking systems and people to read: headings, file type, layout choices and how to check what an application picked up.
Read more
Further reading
Independent career resources for further reading. Listing a source does not imply an endorsement of Resume Home.