Apply when you match the core of the job and are missing only the edges. A 60 percent match is usually worth an application if the missing 40 percent is tools, domain knowledge, or nice-to-haves. It is not worth it when the missing part is the job itself.
The useful skill is telling those two cases apart in about three minutes.
Split the posting into three buckets
Read the requirements and sort every line into one of these:
| Bucket | Meaning | Action |
|---|---|---|
| Core | The reason the role exists | You must have most of these |
| Adjacent | Related experience you could learn quickly | Address one in the cover note |
| Decoration | Tools, degrees, years, certifications | Ignore unless trivial to add |
Most postings have three to five core items, five to eight adjacent, and a long tail of decoration. A "60 percent match" by raw count often means you match all the core items and none of the decoration.
The core test
Ask: if I removed everything except the first two responsibilities, could I do the job on day one with a week of ramp-up?
If yes, apply. If no, the posting is aspirational and you will be filtered out by the hiring manager, not by software.
Handling the two most important gaps
Pick at most two gaps to address, and address them in the cover note, not the resume. The resume should show what you did; the note should explain the bridge.
A bridge sentence has three parts: the gap, the closest thing you have done, and the plan.
Example: "I have not run paid social at scale. I ran the organic program for a 40-store retail brand and managed a $12k test budget, and I have completed the platform certifications."
That is honest, specific, and short. Do not apologise and do not pretend.
What not to do
Three common mistakes that hurt more than they help:
- Listing skills you cannot discuss. An interview will find it, and it costs you the role.
- Rewriting the resume for every posting from scratch. Tailor the summary and the top three bullets; leave the rest.
- Applying to everything. Volume without fit produces rejections that make the search feel hopeless.
Our guide to tailoring a resume without lying covers the middle path.
Why the ATS is not your main problem
Applicant tracking systems filter on obvious mismatches, and most of them rank rather than reject. A human still reads the top of the pile.
The practical implication: use the same words the posting uses for the core skills, because ranking is keyword-driven, but do not stuff. A resume that reads well and contains the core terms will rank.
If you want to check the parsing side, our post on whether your resume passes ATS screening covers the mechanical issues, like tables and headers that break extraction.
A three-minute decision routine
- Copy the responsibilities into three buckets
- Check whether you match the core
- Name the two gaps you would address
- If you cannot name a bridge for either, skip it
Four applications you can defend beat forty you cannot.
When to apply anyway
Two exceptions to the skip rule:
- Internal or referral applications. A warm introduction changes the math on a partial match.
- Small companies. A ten-person company often writes a wish list and hires the person who can do most of it.
Tracking the search
Keep a simple log: company, role, match level, date applied, contact. Review it weekly. The pattern you are looking for is which match level produces replies, so you can spend your time there.
jobs.mehyar scores new postings against your resume and shows where you match, free, including a daily alert and an ATS audit of your resume.


