Somewhere out there’s the candidate who meets 100% of the job ad: every year of experience, every tool, every nice-to-have. That person doesn’t exist, and the company posting the ad knows it. The job goes to whoever applied anyway.
Here is the thing nobody tells you when you’re scanning a posting and counting the boxes you don’t tick. A job description isn’t a contract. It’s a wish list — written by a hiring manager imagining their dream hire on a good day, padded by HR for legal cover, and copied half-wholesale from the last person who held the role. Treating it as a pass/fail exam is how good candidates talk themselves out of jobs they’d be great at.
Let’s fix the way you read these ads, because the fix is mostly mental, and then it becomes a one-line habit that gets you applying to roles you’d otherwise have skipped.
The ad is inflated on purpose (and by accident)
Job ads balloon for reasons that have nothing to do with you. A manager lists everything the perfect person would have, then a recruiter adds a few more to “raise the bar,” then someone pastes in a paragraph from a template. By the time it’s posted, the ad describes a person who would be overqualified for the actual day-to-day work.
You can see the inflation if you know where to look. “Five years of experience” for a role a sharp person learns in eighteen months. “Proficiency in” six different tools when the team really uses two. The classic — an entry-level posting that somehow demands five years of experience, which is a contradiction the company hasn’t noticed in its own ad. When a posting reads like a unicorn shopping list, that’s not a high bar. That’s a sloppy ad.
The skill is learning to tell a real requirement from a wishful one. The phrasing usually gives it away.
“5+ years in B2B SaaS, expert in Salesforce, HubSpot, Marketo, and SQL; MBA preferred.”
“Has sold software before, can learn a CRM fast, and is comfortable with data. The four-tool list is one person’s wish; the MBA is decoration.”
Words like preferred, nice to have, bonus, ideally, and a plus are the company telling you these are optional. Words like must, required, and essential are the real gate, and even those are softer than they sound. The honest split is usually three or four genuine core requirements buried in a list of twelve.
What “core requirements met” actually means
Here’s the rule that changes everything: if you meet the core requirements, you’re qualified to apply. Full stop. Not “qualified to be guaranteed the job” — qualified to be in the conversation, which is all applying ever buys you.
Core requirements are the two-to-four things the role genuinely can’t function without. For a marketing coordinator: can you write clearly, manage a content calendar, and use a couple of standard tools without hand-holding? For a junior developer: can you actually build the thing in the main language? Everything else — the specific framework, the industry, the exact years — is teachable, transferable, or negotiable.
A useful test: imagine your first ninety days. If you could realistically do the core of the job competently by month three, you meet the bar. The gaps that close themselves in a few weeks of normal onboarding aren’t gaps the hiring manager is losing sleep over.
Run the posting through this before you decide: “Do I meet the handful of must-haves, and roughly 60% of the full list overall?” If yes, you apply. If you’re missing one must-have but it’s something you’ve done a close cousin of, you still apply and address it head-on. The only honest “no” is missing two or more genuine, non-negotiable core skills with nothing adjacent to show.
The research: who applies, and who talks themselves out of it
You may have heard the often-cited finding from an internal Hewlett-Packard report, popularized in Harvard Business Review: women tended to apply for jobs only when they met about 100% of the listed qualifications, while men applied at around 60%. The headline gets quoted as a confidence gap, but the follow-up detail is the part that matters for you: when people were asked why they didn’t apply, the most common reason wasn’t “I didn’t think I could do the job.” It was “I didn’t think I’d get hired, and I didn’t want to waste my time.”
Sit with that. The barrier isn’t ability. It’s a private guess about the gatekeeper: a guess made with zero information, because you can’t see who else applied, how desperate the team is, or how flexible the manager actually is. You’re folding a hand you haven’t seen.
The cost of that guess is asymmetric, and badly so. Apply to a stretch role and miss? You lose forty minutes and get a form rejection. Annoying, sure, but rejection emails are survivable. Don’t apply at all? You lose a job you might have gotten, and you’ll never know. One of those outcomes is recoverable in an afternoon. The other one is invisible and permanent.
How to apply at a partial match
Applying at 70% isn’t about bluffing your way past the gaps. It’s about being honest about them while making the hiring manager focus on what you bring. Three moves do most of the work.
One: lead with the overlap, not the gap. Your resume and first lines should hammer the core requirements you do meet, with evidence. Don’t bury your strongest match on line nine. If you’re newer to the field, this is where knowing how to talk about transferable experience turns a thin-looking history into a real case — the babysitting-to-project-management translation is more legitimate than you think.
Two: name one gap, then neutralize it. Don’t pretend a missing skill isn’t there — managers can read a resume. Acknowledge it in a sentence and immediately show the adjacent thing you’ve done, so the gap reads as “quick to close” rather than “can’t do this.”
“I know I don’t have direct experience with Tableau, which is a requirement, but I’m a fast learner and would love the chance to grow into it.”
“The ad lists Tableau; I’ve built the same kinds of dashboards in Power BI, including a weekly sales view the leadership team still uses. Picking up Tableau is a tool switch, not a new skill.”
Three: show, with one concrete result. A specific outcome buys more credibility than three adjectives. “Cut our onboarding from two weeks to five days by rewriting the setup guide” beats “strong communication skills and detail-oriented” every time, because it’s checkable and it sounds like a person who’s actually done things.
That same instinct works in a cover letter, where most people retreat into cardboard.
“I am writing to express my strong interest in this position. I believe my skills and experience make me an excellent fit for your dynamic team.”
“I run the email program for a 12,000-subscriber list and grew open rates from 19% to 31% in a year by killing the corporate voice. Your posting wants someone to do exactly that, at bigger scale — which is the job I want next.”
When the gap is real — and when the ad is the red flag
To be fair: sometimes you genuinely shouldn’t apply. If the role needs a credential you legally must hold — a nursing licence, a P.Eng., a CPA for a senior accounting seat — that’s a hard gate, not a wish. And if you’d be missing every single core skill, you’re not stretching, you’re reaching past your arm.
But before you blame yourself for a “mismatch,” check whether the ad is the problem. A posting that demands ten years for a junior title, lists fifteen must-haves, and offers a vague salary isn’t describing a high bar — it’s often a sign of a team that doesn’t know what it wants. Learning to spot the red flags in a job description saves you from internalizing a rejection that was really about their mess, not your résumé. And if you’re early-career and the ad’s “requirements” read like they were written for someone a decade in, the move is to write a resume that leads with capability instead of tenure and apply anyway.
The confidence is a decision, not a feeling
You will rarely feel ready to apply to a stretch role. That feeling isn’t data; it’s your nervous system overweighting the gaps and ignoring the match. The people who get hired into roles slightly above their on-paper level aren’t braver by temperament. They just made applying a default action instead of a verdict on their own worth.
So flip the question. Instead of “Am I qualified enough to apply?” ask “Is there a real reason I’d be removed from the pile on day one?” Missing a legal credential is a reason. Being a bit light on years two through five of a wish list is not. If you can’t name a disqualifier, you apply — and you let the hiring manager do their own job, which is to decide. That decision is theirs. The application is yours.
Stop auditing yourself out of rooms you were allowed to walk into.
Open the tab with that job you’ve been side-eyeing — the one you keep not applying to. List its requirements in two columns: genuine must-haves on the left, nice-to-haves on the right. If you meet the left column and roughly 60% of the right, apply within the hour. If you’re light on words for the gaps, grab the bridging language from what to say when you have no experience and send it before you talk yourself out of it.
Wage and demand data: Government of Canada Job Bank; résumé phrasing guidance: Job Bank — How to write a good résumé. This is practical advice drawn from hiring patterns, not a guarantee — applying to a stretch role improves your odds, but no single application is a sure thing.



