Am I a good fit for this job?

“Qualified” is the wrong test

Almost nobody meets 100% of a job description, including the person who eventually gets hired. Postings are written as a wishlist — the hiring manager lists the ideal candidate, then compromises in the real world, because that ideal candidate rarely applies. Treating the list as a pass/fail exam is how strong people rule themselves out of jobs they'd be offered.

This isn't a pep talk; it's well documented. The widely cited finding — popularised by Harvard Business Review from an internal review at Hewlett-Packard — is that people frequently hold off applying until they meet every listed criterion, when meeting most is plenty. The cost of that habit is invisible: you never see the offers you didn't apply for. So the first move is to stop scoring yourself out of the room.

Read the posting for must-haves vs nice-to-haves

The skill is separating the few requirements that genuinely gate you from the long tail of preferences. They're usually written in different language, once you know to look:

• Must-haves are specific and binary — a security clearance, a licence, a work-authorisation status, a named language you'll work in daily, sometimes a hard floor on years for a regulated role. Miss one of these and it really is a no.
• Nice-to-haves are everything hedged — “bonus,” “preferred,” “familiarity with,” “a plus,” or a named tool that's really a stand-in for a transferable skill. A posting that wants “experience with Kafka” almost always means “you understand event streaming,” and your equivalent counts.
• Seniority is the quiet one. The biggest single fit question is whether you're at the level being hired for, because that's what the whole loop calibrates against — see why strong candidates get rejected for how badly a level mismatch goes, in either direction.

Run yourself against the must-haves and the level honestly. If you clear those and a solid majority of the rest, you're a real candidate — gaps and all. Every role guide on this site spells out the typical level, years, and what the bar actually tests, which makes the seniority call easier to get right.

Your gaps are the plan, not the verdict

Here's the reframe that changes how you apply: a gap you know about is an asset. It's the thing you prep. If a posting wants distributed-systems depth and yours is thin, that's the system-design story you rehearse, the angle your cover letter and interview answers get ahead of. The candidate who walks in having named and prepped their two weakest areas beats the one who hoped nobody would ask.

The gap you don't know about is the dangerous one — it surfaces live, in the round, with no preparation behind it. So the goal before applying isn't a perfect match; it's an honest map: where you're strong, where you're light, and which of the light spots an interviewer is most likely to probe.

The fast way: a fit score in a minute

You can do all of this by hand, and it's worth learning to. But it's also exactly what Calibrd was built to do in a minute. Paste a real job description and it reads the posting against your CV and returns a Fit score from 0 to 100, with a plain-English band — Strong match (80+), Good fit with gaps (65–79), or Notable gaps — and, critically, a count of the specific experience gaps an interviewer is likely to probe, each one something you can prep.

Each of those gaps is more than a flag. Under the score, the Experience gaps section names the area, marks it major or minor, explains why it matters at this level, and gives you a concrete suggestion for how to close it — plus, where they exist, the books, articles, and courses to actually fill it. So the distance between you and the role you want stops being a vague worry and becomes a short, ordered study plan you can start this week.

That turns “am I a good fit?” from a gut feeling into something you can see before you spend an evening on the application. A 72 with three named gaps is a different decision — and a different prep plan — than a 48. And because the same scan predicts the likely interview questions and benchmarks the comp for that role and level, the answer to “should I apply?” comes with the start of “how do I prepare?” attached.

So what do you actually do

1. Stop scoring yourself out. Assume a 60–70% match is applyable unless you miss a real must-have.
2. Split the posting into must-haves and nice-to-haves, and check yourself against the must-haves and the level — not the whole list.
3. Write down your two or three biggest gaps. Those are your prep list, not a reason to close the tab.
4. If you want the honest map fast, scan the JD against your CV for a fit score and the specific gaps to prep.