How to Check Your CV Against a Job Description (Without Faking It)
"Tailor your CV to the job." You've heard it a hundred times. It's good advice. It's also where a lot of people quietly cross a line.
Because "tailor" often gets read as "make it match." You see a requirement in the advert, and if your CV doesn't obviously cover it, the temptation is to reword something until it looks like it does. Stretch a responsibility. Borrow a phrase from the advert. Nudge a "familiar with" up to "experienced in."
That's not tailoring. That's writing a cheque your interview can't cash. Whatever you inflate to get past the screen, you then have to defend out loud to someone whose whole job is spotting the seams. The honest version of tailoring is more useful anyway... and it starts from the opposite instinct.
What does it mean to tailor a CV to a job description?
Honest tailoring isn't editing the CV to fit the advert. It's checking the CV against the advert to see where you genuinely fall short... and then deciding, requirement by requirement, what to do about each gap.
That reframe matters more than it sounds. If the goal is "make the document match," every gap is a writing problem, and the answer is always more words. If the goal is "find out where I actually stand," then some gaps are writing problems and some aren't, and telling them apart is the entire exercise.
What's the difference between tailoring and embellishing?
The gaps split into two kinds, and they need opposite responses:
Real but unwritten. The advert wants stakeholder management. You've done loads of it... you just never spelled it out on the CV because it felt obvious. This is a real match that's simply missing from the page. Add it. That's not embellishment, it's correction... you're making the CV tell the truth it left out.
Genuinely absent. The advert wants five years of something you have two of, or a skill you've never touched. No amount of rewording fixes this honestly. Here the honest move is to decide whether it's a dealbreaker, whether adjacent experience is worth framing plainly, or whether you prepare to address it head-on in the interview rather than paper over it.
The whole value is in telling those two apart. Faking blurs them together... you end up defending inflated claims and still exposed on the real gaps. Checking honestly separates them, so you fix what's fixable and prepare for what isn't.
There's a practical test for which kind you're looking at. Ask: if an interviewer asked me for a specific example of this right now, could I give one? If yes, it's real but unwritten — the evidence exists, it just isn't on the page. If you'd have to reach, invent, or talk around it, it's genuinely absent, and putting it on the CV only moves the problem to a room where you can't edit.
How do you check your CV against a job description?
By hand, the method is simple and a bit tedious:
- Pull the requirements out of the advert. Every skill, experience level, responsibility, tool and qualification it states or implies. Ignore the rest — salary, benefits, culture paragraphs and "we're a fast-paced team" filler aren't things a CV can evidence.
- Find the evidence for each one in your CV. Not "could I argue this?" — where on the page does a reader see it?
- Mark each requirement covered, missing-but-real, or genuinely absent.
- Act on each one honestly, per the split above.
Here's what that looks like on a real advert. Say it asks for a data analyst with advanced SQL, experience running experiments, line-management responsibility, and five years in the field. Your CV says you were a Senior Data Analyst for six years, lists SQL and Python, and describes "improving reporting across the commercial team."
- Advanced SQL — covered. It's listed and the seniority backs it up.
- Five years in the field — covered. Six years, stated plainly.
- Running experiments — missing but real. You ran A/B tests constantly. The CV never says so, because "improving reporting" was the tidier summary. Add it, with an example.
- Line management — genuinely absent. You mentored two juniors; you never had reports. Don't write "managed a team." Either frame the mentoring plainly as what it was, or go in ready to answer the question directly.
Two of those four are fixable in ten minutes without a word of exaggeration. One isn't fixable at all, and knowing that before you apply is worth more than a cleverly-worded bullet point.
Should you apply if you don't meet every requirement?
Usually yes — but the honest check is what tells you which kind of shortfall you're looking at, and they aren't equal.
Most adverts are a wish list assembled by several people, and a good chunk of it is aspirational. Missing two or three of a dozen "requirements" is normal and rarely decisive, particularly when they're tools rather than experience. Tools are learnable and everyone knows it.
What's worth taking seriously is a gap in the shape of the role rather than its contents. Never having managed anyone, when the job is fundamentally about managing people. No exposure to the domain, when the domain is most of the difficulty. Missing a hard credential — a licence, a qualification, the legal right to work somewhere. Those aren't gaps you talk around; they're the job.
So the decision isn't "do I meet everything," it's:
- Is the gap central or peripheral? Peripheral gaps are worth a plainly-worded sentence and nothing more. Central ones need a real answer before you apply, not during the interview.
- Do I have adjacent evidence? Mentoring isn't line management, but it's honest neighbouring evidence and it's much better framed as what it is than dressed up as what it isn't.
- Can I close it before the interview, truthfully? Sometimes the answer is a weekend with the documentation and a small project you can actually talk about. That's a real fix. Adding the skill to your CV without doing that isn't.
The point of checking honestly is that you end up making this decision deliberately, once, with the requirements in front of you — instead of discovering it in the third round.
What makes this hard to do on your own?
Two things, and they're both about objectivity rather than effort.
The first is that you know what you meant. When you read "improving reporting across the commercial team," you see the six months of experiment design behind it, so it reads as covered. A stranger sees a sentence about reporting. You're not checking your CV — you're checking your memory, with the CV as a prompt.
The second is that you want the job. Every ambiguous requirement gets the benefit of the doubt, because marking it a gap means more work or, worse, deciding not to apply. That pressure runs one way, and it runs quietly.
It's the same discipline as finding the questions your CV can't answer, just pointed at a specific advert instead of a general interviewer — both are versions of the same underlying problem, which is everything your CV doesn't say.
Can a tool check your CV against a job description?
Most tools in this category will do it by counting. They compare the advert's words against your CV's words, give you a match percentage, and tell you which keywords to add. That's a string comparison dressed up as advice, and it optimises for exactly the wrong thing: it rewards you for pasting in language you can't back up.
ChatBotCV's job-advert cross-check works the other way round. It reads the advert for what it actually requires, turns each requirement into the question an interviewer would ask about it, and checks whether your CV can answer that question — so a requirement you genuinely cover in different words counts as covered, and a keyword you've pasted in without evidence doesn't help you.
It won't reword your CV to match the advert. That's the one thing it deliberately won't do, because that's the line between honest tailoring and faking it. It shows you the real gaps against the real target. What you add back is up to you... and stays true.