Crosshire
Miscellaneous·Hiring·13 min read·17 July 2026

A fit score that shows its work.

Most tools match keywords and hand you a number you can't argue with. This one reads a whole CV against a whole job description, scores the fit honestly, and cites every skill back to the line it came from — then tells both sides of the desk the truth: worth applying, or worth screening?

Crosshire's matcher — the fit-scoring product at fitscore.crosshire.ch — does one thing, deeply: it reads a single CV against a single job description and returns an honest fit. A score with its worst case, every skill traced to the line that proves it, the gaps named out loud, and a clear verdict. Not keywords. Not a ranking you can't interrogate. About fifteen minutes, and the same engine serves both sides of the desk. This is the tour of what it does and how to use it.

01What it is

Two questions, one engine

It answers a single honest question, asked from two directions. The reading underneath is identical — only the reader changes.

For candidates
Worth applying?

Stop sending CVs into the void. Paste a job description, upload your CV, and get an honest Summary — score, evidence, verdict — before you spend an evening on a cover letter for a role that was never going to land.

Live
For recruiters
Worth screening?

Drowning in CVs for one role? FitScore reads each one against your JD with cited evidence and ranks candidates by real fit — so you know who's worth a thirty-minute call before you read a CV in full.

Live

Same engine, two perspectives. It's tuned today for data, software and AI roles across the DACH region and the UK — the taxonomy, the scoring calibration and the skill ontology are built for those specifically; adjacent fields still work, with less precision.

02The problem

Not an information problem — a signal problem

FitScore names the shape of it plainly, from both ends of the same broken exchange:

The candidate side

A hundred applications. Four replies. No offer. Weeks poured into roles that were never going to land — with no way to tell, in advance, which five were worth the effort.

The recruiter side

Five hundred CVs for a single role. Thirty minutes each to find the five worth screening. The signal that matters is real — it's just buried under everything that isn't.

The job market doesn't have an information problem; it has a signal problem. Most AI tools make it worse — helping people apply to more roles, faster, with even less context. That's volume, not signal. FitScore takes the opposite line: read deeply, score honestly, cite the evidence, and tell both sides the truth.

03What you get

Six things, read from both sides

Every pairing produces the same six things — each one written for whoever is reading it.

Honest fit score
Candidates

A score with its worst-case range. You see the upside and the downside before screening exposes it.

Recruiters

A score per candidate with a confidence range — decide who's worth a call before reading the CV in full.

Cited evidence
Candidates

Every skill traced to the line in your CV. If we couldn't verify it, we say so — never silently drop or accept a claim.

Recruiters

Every skill matched to the CV with the specific quote. No hallucinations, no keyword-stuffing tricks.

Skills telemetry
Candidates

A visual map of when you used each skill, at which company, for how long.

Recruiters

Spot recency bias and skill drift at a glance — whose Python is from 2018, whose is from 2024?

Honest gaps
Candidates

What will hurt in screening, with brief advice on how to address each gap.

Recruiters

What's missing in each candidate, mapped to your JD's specific requirements.

Clear verdict
Candidates

Strong fit · Worth applying · Conditional · Address gaps · Don't apply. No false confidence.

Recruiters

Top candidates ranked, conditionals flagged, weak fits dropped — with reasoning for each.

Downloadable PDF
Candidates

Send your Summary to the recruiter as your application context.

Recruiters

A per-candidate briefing PDF for your hiring manager — no more thirty-minute CV reads.

04Selling point · the verdict

The verdict, and its worst case

The headline is one word, but it never arrives naked. It sits on a rung you can read at a glance — and it carries the downside, not just the upside.

Strong fitThe evidence clears the bar with room to spare.
Worth applyingA real fit — apply, and lead with the strengths that carry it.
ConditionalClose, but it hinges on one or two things worth clarifying first.
Address gapsA named gap stands between you and a yes — here's what to fix.
Don't applyThe honest call is no — better heard here than after a week of silence.

Beneath the verdict sits the Crosshire Score, 0–100, banded so the number becomes a judgement: 85+ reads Excellent, 70+ Good, 55+ Fair, below that Poor. And it always shows its worst case alongside its best — because a score that hides its downside is exactly the thing a screener will find for you.

05A worked example

One real match, in full

Abstract is easy to trust and easy to dismiss. So here is one whole Summary, start to finish — a senior data architect scored against a mid-level Data Analytics Consultant contract (Databricks/Azure, 100% remote, ~5 months). Every company name is anonymized; everything else is exactly what the engine returned.

The verdict
66 / 100 — Conditional match. An overqualified senior architect willing to take a mid-level engagement. Worst case 64 if the German-level read comes in low; no upward lift pending. Confidence 0.78.
Skills coverage
4 of 5 required skills found · 80% JD match. Three strong-recent, one partial (BI), none via transfer, one missing (ML).
What the JD really is
Archetype fit: Analytics Engineer 85% · Data Engineer 65% · Data Analyst 50% · ML Engineer 30%. A pipeline-heavy role wearing a consultant title.
The one-line read
Core data engineering and Databricks are an outstanding fit; the only mechanical gap is dashboard-development depth on the BI side.

Underneath the headline, the score is decomposed skill by skill — recent activity separated from lifetime, and each dimension marked match, transfer, or gap:

DatabricksCore · match. 4.25y active in the last 5, 7.33y lifetime — Expert, well past the 1.5y bar. Asset Bundles, Unity Catalog RBAC, Delta optimization, Photon.
Microsoft AzureCore · match. 2.17y recent, 8y lifetime — Data Factory, Data Lake Gen2, Azure DevOps.
ETL / ELT pipelinesCore · match. 4.83y recent via Airflow, dbt, and Kafka — three Expert-level constituents active in the window.
Analytics & BICore · transfer. 3.83y recent — but Power BI appears as a pipeline sink, not dashboard authoring. Related, not verbatim.
Machine LearningCore · gap. Not in the CV. Listed as a must-have, but flagged by the JD's own quality checks as a likely template artefact.

Then the evidence — traced back to the roles it was earned in, most recent first. This is the part a screener would otherwise reconstruct by hand:

CompanyYearsRoleDBAzureETLBIML
Contoso Analytics2025–2026Senior Data Architect / Data Engineer×
Fabrikam Marketplace2024–2025Senior Data Engineer×
Northwind Pharma2023–2024Senior Data Engineer×××
Tailspin Tools2023Senior Data Engineer×××
Litware Energy2022–2023Senior Data Engineer××
Coho Health2021–2022Senior Data Consultant×
Proseware Indices2018–2021Senior Data Architect×
Wingtip Retail2018Senior Data Engineer×
Woodgrove Bank2015–2018Database Architect / Data Engineer×××××
Earlier roles2004–2015Senior Data Engineer & Database Architect×××××

used — core skill  ·   used — transferable  ·  × not used at this role  ·  10 roles, 2004–2026

The strengths and the gaps are named just as plainly — five things carrying the fit, two things pulling against it, each with what to do about it:

What's working — five strengths, +58 pts
  • Databricks at Expert level, 2.33y in the 3-year window — past the 1.5y/3y bar with headroom (Asset Bundles, Unity Catalog RBAC, Delta optimization, Photon).
  • ETL breadth across Airflow, dbt, and Kafka — exactly-once delivery, DAG authoring, dbt macro/SCD frameworks, all Expert-level.
  • A direct role-shape precedent — a Databricks medallion analytics delivery for e-commerce stakeholders: Azure cloud, dbt, dashboard integration, 100% remote, same short-contract format as this JD.
  • Azure footprint across Data Factory, Data Lake Gen2, and DevOps in recent roles — platform-level breadth, not a single tool.
  • Seven short-term contracts (8–34 months) since 2018 — a proven capacity for rapid onboarding, directly matching a 5-month engagement.
Honest gap 1 · analytics BI — must-have, mediumThe BI depth is consumption-oriented: Power BI and Tableau show up as pipeline sinks across the roles, with no DAX authoring, RLS design, or dashboard build — while this role explicitly wants dashboard development with stakeholders. Transferable, and the engine says how to close it: frame pipeline-design-for-BI as an analytics-enablement competency, or ship one Power BI report on a live Databricks dataset and the perceived gap closes within a week.
Honest gap 2 · machine learning — must-have, lowNo ML evidence anywhere in the CV — but the JD lists ML as a must-have while never mentioning it in a single responsibility. The engine catches the contradiction, downgrades ML's weight to 0.4, and flags it as a likely template artefact rather than a real blocker. The advice is not to bluff — it's to ask the recruiter whether ML is real before adjusting the pitch.

And where it cannot be certain, it says so, and hands you the exact question to ask — instead of guessing:

Verify before decidingThe JD infers German B2 for client-facing communication, but the language read lands at 0.65 confidence — below the engine's own 0.7 threshold — so it refuses to score it as settled. The candidate's German is B1/B2: Met if the bar is B2, Partial if it's really C1. So the Summary surfaces the one question worth asking first — "Do client meetings need higher fluency, or is a collaborative team environment standard?" That single clarification is the difference between a 64 and a 68.

That is the whole shape of it: a number with its worst case, the skills decomposed and dated, the evidence traced to real roles, the gaps named with remediation, and the one thing to confirm before anyone spends a screening slot. Decision-support — not the decision.

06How to use it

Two paths, three steps each

There's nothing to configure. Whichever side you're on, it's three moves to a Summary.

As a candidate

  1. Paste the job description you're eyeing.
  2. Upload your CV.
  3. We email your Summary in about fifteen minutes — score, evidence, verdict.

As a recruiter

  1. Post your JD — free, and it comes back with a red-flag analysis of the posting itself.
  2. Drop in candidate CVs.
  3. We rank them with cited evidence, reasoning attached to each place.
07The differentiator

How it stays honest

The honesty isn't a tone; it's a set of rules the engine is held to on every Summary.

Held to, on every pairing
  • Every skill cited to your CV. Never fabricated.
  • Skills it couldn't verify are flagged "Listed only — not verified."
  • Hard requirements separated from wishlist items.
  • Recency weighted separately from lifetime experience.
  • Scores include worst-case ranges. No false confidence.
  • AI processing disclosed — Anthropic Claude, Google Gemini.
  • GDPR-native. EU-region data processing where possible.
  • Decision-support, not the decision. The call is yours.
And how it's builtBuilt in Europe, hosted in the EU, GDPR-native by default rather than as an afterthought. Your CV is encrypted at rest, deletable on request, and never sold or shared. Scoring runs on Claude and Gemini with EU-region processing — and, unusually, every line of the product's code is written by AI agents under human review, with a person approving each change before it ships. The score is there to help you triage in seconds; it is never the decision.
08Beyond the summary

What else is in there

The Summary is the front door. Behind it sits the rest of the toolkit.

Skills telemetry
A timeline of every skill — when it was used, where, for how long, and how recently — so "knows Python" becomes "used Python daily, most recently last year."
The Summary, dissected
Why the score is what it is: the signals behind it, the skills with their provenance, the concerns, the gaps with remediation advice, and a short outreach pitch you can actually send.
CV generator
Turn a parsed profile into a clean, structured CV — evidence-backed, not embellished.
Public profile
A shareable profile at your own handle, backed by the same cited evidence — a link you can hand a recruiter instead of a PDF into the void.
Recruiter pipelines
Rank a whole pool against one role, see the pool's collective gaps, and track candidates through screening.
JD red-flag analysis
Post a job description on its own and get its concerns and role archetypes flagged — before a single CV lands against it.
09Try it

Run one real pairing

The fastest way to feel the difference is to score one thing that matters: your own CV against a job you're actually considering, or one real candidate against a role you're actually hiring for. Each capability here can earn its own close-up later — the score and its range, the cited evidence, the telemetry, the recruiter pipeline — but the overview is best tested, not read.

Try it now
Free during early access — the full Summary, cited evidence and a public profile, no card. Sign in with Google or email, and score one real pairing.
Candidates & recruiters · one engine · cited evidence.
The method, in the product's words
How it works & how it stays honest
The two paths, the honesty rules, and the scope it's tuned for — straight from the product pages.
The sister product
German that grades itself
The same honest-scoring instinct, applied to language learning: writing and speaking read and marked, error by error.

Written from the live product — the verdict ladder, the score bands and the honesty promises are taken from what's shipped at fitscore.crosshire.ch, not a projection. — Crosshire.

© 2026 Crosshire Journal · Made in EU Written from a working product