JD tailoring
Should 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.
By Resume Home · Updated . Illustrative examples are fictional: replace sample identities and experience with your own facts before applying.
In short
When your resume does not cover a requirement, first ask whether the experience is missing or merely absent from the document. Add accurate evidence you omitted. Describe related experience as related, and leave genuine gaps honest. Decide whether to apply using the posting's stated requirements and the role itself, rather than a universal match percentage.
Key takeaways
- Tell omitted evidence, related experience and a genuine gap apart before you edit anything.
- Add real evidence you left out, and describe related experience as related.
- Decide whether to apply from the posting's stated requirements, not a universal match percentage.
Separate three different kinds of gap
A missing keyword does not always mean missing experience. You may have done the work using different wording, or left it out because the base resume focused on another role. Search your own records before deciding that nothing supports the requirement.
There is also a difference between related experience and direct experience. A nearby tool or responsibility may show a useful foundation, but it should not be renamed as the exact qualification the employer asks for.
- Omitted evidence: you have the experience, but the resume does not explain it.
- Related experience: you have a useful foundation, but not the exact requested skill or context.
- Genuine gap: you have not done the work and have no evidence to claim it.
Required vs preferred qualifications: deciding whether to apply
Many postings separate what they require from what they would like. A missing preferred qualification need not stop you applying. For required ones, tell mandatory credentials, such as a licence, apart from skills or experience where an employer may accept an equivalent background, and weigh how much each gap matters rather than counting them.
- Required, minimum or must-have: the work the role depends on. Check each against your own evidence.
- Preferred, desired or nice to have: helpful extras. Show the ones you have and do not stretch for the rest.
- An unlabelled list: read the duties to see which skills the daily work actually depends on.
Add real evidence you left out
Suppose a posting asks for customer communication and your resume says only 'processed support tickets'. If your role also included explaining account setup to customers, that detail may belong in a bullet. Check what you actually did before adding it.
Write down the specific interaction, your responsibility and the outcome before revising the bullet. 'Make me sound experienced with customers' is too vague to guide accurate writing; a concrete account of the work gives you something useful to describe.
Before
Processed support tickets.
After
Resolved support tickets and explained account setup steps to customers.
Why it works: Use the second wording only if customer explanations were part of the work. It addresses missing evidence rather than creating new experience.
Explain related experience without claiming equivalence
Describe what transfers and what does not. A volunteer coordinating an event can explain scheduling, participant communication and resolving logistical problems. That is useful evidence for a coordination role, but it is not the same as having managed a professional department.
Similarly, using one interface framework may provide a foundation for learning another. Keep the tool you actually used in the resume. If you are studying the requested tool, describe the current learning or project accurately instead of claiming professional proficiency.
Decide whether to apply, and check your wording
There is no universal percentage of requirements that makes an application worthwhile. Read the specific posting, consider which requirements are stated as essential and decide whether your evidence supports a reasonable application. Ask the employer for clarification when a requirement's meaning is unclear and a contact route is available.
Do not turn a gap into a credential through stronger wording. Check any claimed contribution against your own experience. If it is not yours, remove it and consider a concrete learning or project opportunity for the future.
- Is this a requirement I genuinely meet but have not described?
- Does my related experience need an explicit limit or context?
- Can I defend every accepted statement in an interview?
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 itHow 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.
Read moreEntry-level software engineer resume: example and writing guide
Write an entry-level software engineer resume using projects, coursework and transferable experience. Includes a fictional example and a review checklist.
Read moreHow to write a cover letter with no professional experience
Write a first-job cover letter using coursework, volunteering and projects. Includes a fictional complete letter, paragraph prompts and common mistakes.
Read more
Further reading
Independent career resources for further reading. Listing a source does not imply an endorsement of Resume Home.