Example: a CV compared to a job description

How to read it

The scoreHow much of the posting the CV covers.
Requirement by requirementEach requirement marked covered, partial or gap — with the CV line quoted wherever there is one.
What to lead withThe strongest angle, a draft paragraph and what tailoring would change.

Example fit report

1 · The score

How much of this posting the sample CV covers. Must-haves count more than nice-to-haves.

Must-haves · 8 of 9

Nice-to-haves · 3 of 4

Covered must-have
Covered nice-to-have
Gap

Scored against this posting only — not a grade for the CV. Every point came from the sample CV itself: nothing was invented, and gaps stay gaps.

2 · Requirement by requirement

13 requirements scored from this posting. Must-haves first.

CoveredAt least 6 years building production backend systems, with meaningful time on services where correctness matters more than feature velocity.Must-have
From the sample CV9 years of experience building high-throughput services in Go and Python on AWS
CoveredStrong, current Go. You should be comfortable being the person who reviews other people's concurrency code.Must-have
From the sample CVGo (primary, 7 years)
CoveredDeep experience with Kafka and event-driven architecture, including schema management and consumer failure handling.Must-have
From the sample CVBuilt the company's first Kafka deployment as the shipment-tracking event backbone, 6M events per day, with Avro contracts and a schema registry.
CoveredSerious PostgreSQL experience at scale, not just as an ORM target.Must-have
From the sample CVRebuilt the partitioning strategy for a 4.2 TB append-heavy Postgres table; p99 query time went from 1.8s to 190ms and vacuum-related incidents to zero across 11 months.
CoveredProduction experience on AWS and Kubernetes, including owning deployment and observability for your own services.Must-have
From the sample CVRolled out Prometheus, Grafana and structured logging across all 7 services; MTTD fell from 25 minutes to under 4 minutes.
CoveredDemonstrated incident command experience on high-severity production incidents.Must-have
From the sample CVIncident commander on 11 Sev-1 and Sev-2 payment incidents, including a 47-minute settlement outage during Black Friday 2021; follow-up work took repeat-cause incidents from 5 per quarter to 0 over the next three quarters.
CoveredExperience working inside a regulated environment such as PCI DSS, and comfort with the evidence and audit work that comes with it.Must-have
From the sample CVProduced PCI DSS v3.2.1 control evidence for the settlement service; passed 2 external audits with zero findings against my components.
CoveredTrack record of mentoring less experienced engineers and raising the standard of a team's engineering practice.Must-have
From the sample CVMentored 3 engineers (2 junior, 1 mid-level), 2 of whom were promoted within 18 months, and ran more than 40 technical interview loops.
GapHands-on experience with ISO 20022 message formats and SEPA Instant scheme rules.Must-have
Not in this CV — HireReady24 will not write it in.
CoveredTerraform or equivalent infrastructure as code.Nice-to-have
From the sample CVTerraform
CoveredgRPC for internal service communication.Nice-to-have
From the sample CVgRPC
CoveredGerman at conversational level (our compliance counterparties often prefer it).Nice-to-have
From the sample CVGerman (B1)
GapExperience with double-entry ledger modelling.Nice-to-have
Not in this CV — HireReady24 will not write it in.

3 · What to lead with

Tomas Vrabec's strongest angle for this role

Settlement-domain ownership at EUR 1.9bn volume, with incident command and PCI DSS audit evidence already in hand

Points Tomas Vrabec could make, each backed by a line of the CV:

I owned a Go/Postgres/Kafka settlement service at a volume and request rate comparable to what this role describes.
From the sample CVOwned the payout settlement service (Go, PostgreSQL, Kafka) processing EUR 1.9bn annual volume at ~2,400 requests/second peak.
I built exactly the correctness guarantees the role asks for on a live settlement path, not as a theoretical exercise.
From the sample CVIntroduced idempotency keys and exactly-once reconciliation on the settlement path, eliminating an average of 260 duplicate payouts per month.
I've run incident command on high-severity payment incidents through to reduced repeat-cause rates.
From the sample CVIncident commander on 11 Sev-1 and Sev-2 payment incidents, including a 47-minute settlement outage during Black Friday 2021; follow-up work took repeat-cause incidents from 5 per quarter to 0 over the next three quarters.
I've produced PCI DSS control evidence and been through external audits on the same kind of settlement component this role owns.
From the sample CVProduced PCI DSS v3.2.1 control evidence for the settlement service; passed 2 external audits with zero findings against my components.

A paragraph Tomas Vrabec could use

I've spent the last several years on the unglamorous but high-stakes part of payments and distributed systems: exactly-once semantics, partitioned Postgres, Kafka topic design, and making on-call survivable. At Norvane Pay I owned the payout settlement service — Go, PostgreSQL, Kafka — processing EUR 1.9bn in annual volume at around 2,400 requests per second at peak. I also produced PCI DSS v3.2.1 control evidence for that service and passed 2 external audits with zero findings against my components. More recently, at Trellis Health Data, I rebuilt the partitioning strategy for a 4.2 TB append-heavy Postgres table, taking p99 query time from 1.8s to 190ms, and replaced a homegrown cron scheduler with Temporal, cutting failed-workflow manual interventions from about 35 a week to 2. I mentor mid-level engine…

Every figure in it is from the sample CV, and nothing about the employer beyond the posting.

What tailoring would change

Read-only here. In the app, a suggestion tells the tailoring step what to emphasise — it never edits the CV itself.

Framing
Lead the CV with the Norvane Pay settlement role rather than the health-data role, since this posting is specifically about owning settlement and reconciliation.
The CV lineIntroduced idempotency keys and exactly-once reconciliation on the settlement path, eliminating an average of 260 duplicate payouts per month.
Numbers
Keep the 260 duplicate payouts per month figure visible near the top of the settlement bullets — it's the clearest evidence of the 'never double-paying' correctness bar the posting sets.
The CV lineProduced PCI DSS v3.2.1 control evidence for the settlement service; passed 2 external audits with zero findings against my components.
Framing
Keep the PCI DSS audit bullet prominent and adjacent to the settlement-ownership bullet, since the posting asks specifically about producing control evidence and working with external auditors.
Length
Trim or shorten the Aurelis Bookings entry — its Python/Django inventory-sync work doesn't speak to settlement, Kafka, or incident command, which this posting weights heavily.
Wording
The posting calls this 'safe replay of failed batches' — connect it to the failed-workflow recovery work already described.
Headline
Use a headline naming settlement ownership and incident command directly, since both are named requirements in the posting and both are backed by strong evidence.

Now check your own CV.

Paste your CV and a posting — free, no account. HireReady24 keeps them for up to 24 hours unless you save the report.

Check my fit Try a sample candidate on your posting