Should you apply when you don't meet every requirement?

Apply if you meet most of the core requirements — the three to five things the role cannot do without — and ignore the wish list below them. Long postings are often assembled from older ones, so length is not difficulty. Licences and clearances are not negotiable, and no applicant tracking system rejects you at a published percentage.

The posting that asks for ten years of a five-year-old framework is not testing you. It is a document three people edited, none of whom removed anything. Reading it as a specification rather than a wish list is what stops qualified people applying, and it is the only part of this you control.

• Separate the three to five must-haves from the wish list before you decide anything else
• Impossible combinations — a junior title with a decade of experience, a stack that did not exist that long — usually signal a copied posting, not a real bar
• Some requirements are absolute: licences, security clearances, legally required credentials
• Restate adjacent experience in the posting's own vocabulary rather than leaving the reader to translate it
• Name your largest real gap in one sentence, then say what you have instead — do not hope nobody notices
• Record which stretch applications get replies, so you learn where your actual ceiling sits rather than guessing at it

Why are so many postings unrealistic?​

Four reasons, none of them about you. Requirements accumulate: a team copies the last posting for a similar role, adds what the new hire should also cover, and removes nothing. Hiring managers list the ideal candidate rather than the viable one, because writing down what you would love costs nothing. Some employers inflate deliberately, believing it filters for confidence — it mostly filters out people who read carefully. And occasionally the list is written backwards from an internal candidate who already has the job. All four produce the same document: three to five real requirements buried in fifteen lines.

How do you tell a must-have from a wish?​

Look at what the role cannot function without on day one: usually a core technical competency, a minimum viable experience level, and sometimes genuine domain knowledge. Everything else — a specific tool, an exact industry, a certification you could sit in a quarter, a degree you have equivalent experience for — is negotiable more often than not. Two signals help: requirements listed first are usually the ones the hiring manager wrote, and a requirement stated with a threshold ("must hold", "required by law", "active clearance") is different in kind from a preference.

To do the split in writing rather than in your head, the Matched Requirements tab on a Job Based Resume lists every requirement as a Direct Match, a Smart Match or Missing, with checkboxes to filter to the missing rows. Reading those is faster than re-reading the posting a fourth time.

What is the threshold for applying anyway?​

Roughly 70% of the core requirements — a rule of thumb about your own judgement, not a fact about anybody's software. It is useful for one reason: it forces you to count the must-haves instead of reacting to the length of the list. Count five core requirements, find you cover four, and the decision makes itself.

Keep it strictly separate from the claim repeated everywhere else, that applicant tracking systems forward resumes above a 70% keyword match and reject below it. There is no such published rule. Screening thresholds, where they exist at all, are configured by each employer for each requisition, and nobody outside the company can tell you what one is set to.

FluxResume does show a number, and it is worth being precise about it. The match score on a Job Based Resume has documented bands — below about 50% weak, 50–70% good, 70%+ strong, 85%+ excellent. That describes how well one of your resumes lines up with one posting inside FluxResume. It is not an employer's threshold, no external system reads it, and a high score does not mean an employer will agree.

How do you address a gap without apologising?​

Name it in one sentence and follow it immediately with the closest thing you do have. "The role asks for PMP certification. I have eight years running projects at that scale and I sit the exam next month" is a complete answer. Two sentences of throat-clearing before it is not.

Three moves cover most gaps:

• Adjacent experience. Life sciences against a healthcare requirement, project management against a product role. State what actually transfers — regulatory work, roadmap ownership, user research — rather than asserting that it transfers.
• Their vocabulary, not yours. If the posting says "customer success" and your title said "account management", write customer success. That is not keyword games; it removes a translation step from a reader with forty applications open. Should you customize your resume for every job? covers how far to take it.
• A specific plan, not enthusiasm. "Actively developing" means nothing. A named course, a dated exam, or a project you already shipped means something.

To find the gap before you write any of that, a general AI assistant handles this task well, and AI Chat takes the same prompts. Two worth keeping:

Compare my current skills — [list them] — against the requirements for [job title]. Identify the gaps and give me a 90-day plan to close the two that matter most.

I am a [current role] with [X years] in [field], considering a move to [target role]. Compare specialising in [skill A] against [skill B] for that move, and say which is the shorter path and why.

Treat the answer as a draft: it does not know your market and it will invent confident specifics, so the useful output is the shortlist of gaps, not the plan. Asked about roles rather than skills, Career Navigator runs a ten-question quiz and builds a graph of lateral moves, level-ups and specialisations from a role title — also reachable from its product page.

When should you not apply?​

When the gap is a licence, a clearance, or a credential the job legally requires, the answer is no, and the rest of this post does not apply. Everything above assumes the missing pieces are learnable or substitutable. A medical licence is not.

The other three cases: you lack the core competency outright rather than a version of it; you are missing several critical, non-transferable requirements at once; or the level and salary are far enough from your experience that the mismatch is the message. Applying anyway is not ambition but volume, and volume is the fastest way to generate silence — the subject of why you're not getting interview callbacks.

Track stretch applications separately from safe ones. A handful a month, recorded on your board in Pipeline with the reply or the silence beside them, tells you within a quarter where your ceiling sits. Job search organisation covers the weekly review that turns those records into a decision.

Questions people ask about job requirements​

Do employers really expect every requirement?​

Rarely. Most postings describe an ideal candidate assembled from previous versions of the same document, and hiring teams routinely interview people who miss items on the list. The exception is any requirement stated as a legal or regulatory condition — those are enforced exactly as written, because the employer has no discretion over them.

Should I mention a missing certification?​

Yes, once, in a single sentence, and only if the posting lists it as required. Say what you have instead and give a date if you have one. Leaving it unmentioned invites the reader to assume you did not read the posting; explaining it across a paragraph makes the gap the subject of your application.

Does applying under-qualified hurt future applications there?​

Not in any way you can measure. Recruiters see far too many applications for one stretch attempt to register. What does register is applying to every role a company posts regardless of fit, which reads as untargeted. Two or three considered applications a year at a company you want is fine.

How do I reframe experience from another industry?​

Lead with the mechanism rather than the sector. Say what problem you solved, at what scale, with what result, and use the posting's own words for the parts that are genuinely the same. "Managed a $10M portfolio across twelve stakeholders" carries across industries; "eight years in logistics" does not. Sector is context, not headline. Doing that across the whole document, rather than one bullet, is how to write a resume when you are changing careers.

Originally published January 2025. Reviewed and rewritten for FluxResume in August 2026.