How strong is your application, really?

A 60 is not a rejection. An 85 is not an interview. The score tells you whether to apply, tailor, or skip.

Why it matters

Evidence, not keywords

Most tools count how many of the job's keywords show up in your CV. Trackr checks something harder: whether you actually evidence each requirement with specifics, scope, and outcomes. A buzzword you mention counts for far less than a result you can show.

Your gaps, named

You see which of the role's requirements your CV meets, which it only partly addresses, and which it misses, each one named. Not a vague composite number, but a list you can act on: add a project, reframe an experience, or move on.

Every CV variant, scored separately

Keep 2 to 15 CV variants in Trackr. Each one is graded independently against the same role, so you can see which version of your story stands up best, without guessing.

What the score actually measures

Trackr doesn't count keywords. It reads the role's real requirements and, for each one, asks a sharper question: have you evidenced it, or only stated it?

Stating a requirement is claiming it: listing a skill, echoing a phrase from the posting. Evidencing it is showing it: the project, the scope, the outcome, the numbers. An application built on claims reads thin to a recruiter, so it scores thin here. One that backs its claims with proof scores strong.

The requirements that matter most to the role carry the most weight, so clearing the core of the job counts for more than ticking a nice-to-have. And an application that reads as padded, stuffed with the posting's own wording instead of your own evidence, is marked down, because that's exactly how a human screener and an automated one both read it.

What you get back is a single Application Strength score from 0 to 100, a band from Weak to Strong, and a plain breakdown of what's strong, what's thin, and what's missing.

The score is a signal, not a verdict. Real hiring decisions include things the score can't see: how the interview goes, who the hiring manager is, and which application they happened to read first. We will never tell you a score means you have the job.

Illustrative example
Your Application Strength
82/100

Your strong evidence

A relevant requirement is supported by a specific project and its result.

Your thin evidence

A skill is listed, but its scope or outcome needs a clearer example.

Your missing evidence

A role requirement is not evidenced in this CV. Add genuine experience if you have it.

This is an illustration, not your result or the scoring formula. Your review depends on your CV and the selected role. It is not an interview prediction.

Frequently Asked Questions

What is a good Application Strength score?
80 and above is Strong: your CV evidences the role's core requirements, so apply with confidence. 60 to 79 is Solid, with a few gaps worth firming up first. 40 to 59 is Thin: the fit is there on paper but the evidence isn't. Below 40 is Weak, and the breakdown tells you what's missing.
What score should I aim for?
Aim for Strong (80+) on the roles you want most, but don't chase 100. A top score on every application usually means you're only applying for jobs you already do. A Solid score on a stretch role can be the right bet, as long as you close the gaps the breakdown names before you apply.
Is this a CV checker?
Yes, but a specific kind. It doesn't give your CV one generic rating. It checks and scores your CV against one job description at a time, so the same CV can come out Strong for one role and Thin for another. That's the review that matters when you're deciding whether to apply.
How does it compare my CV with the job description?
It pulls the role's requirements out of the job description and weights them by how central they are to the job. Then it checks your CV for evidence of each one: the project, the scope, the outcome. Each requirement comes back as met, partly met, or missing, and those roll up into your score.
Isn't this just keyword matching?
No, and that's the point. Keyword matching rewards you for repeating the job description's language, which both recruiters and screening tools have learned to discount. Trackr grades whether you evidence each requirement with real specifics. A CV stuffed with the right words but no proof scores low here, on purpose.
Is the analysis done with AI?
Yes. Trackr uses LLMs (OpenAI primary, with fallbacks) to read your CV against the role. Personal identifiers are stripped from the CV before any prompt is built, so the model sees your skills, experience, and dates, not your name or contact details.
Why is my application scoring low when I think I'm qualified?
Usually one of three things: you stated a requirement but didn't evidence it, your most relevant experience is buried below the fold, or the role uses different language for something you've done. The breakdown names which one, so you fix the specific thing instead of rewriting everything.
Does the score predict whether I'll get the interview?
No. It predicts whether your application reads as strong for the role. Interview decisions also depend on recruiter preferences, applicant volume, internal referrals, and timing. Use the score to decide where to spend tailoring effort, not as a guarantee.
Can I see how the score changes if I edit my CV?
Yes. Re-run it after editing. Trackr keeps the history per CV per role, so you can see whether your edits moved the strength up or down.
How many can I run per month?
One analysis uses one AI credit. Free covers 40 credits, Plus 290, Pro 820. Most active applicants use 30 to 100 credits a month.

Want to check by hand first? Read how to check your CV against a job description.

Ready to stop guessing?