A sample report
For Alex Morgan, a made-up platform engineer, applying for a made-up Senior Platform Engineer role. This is what you'd see for your own CV and a job you want.
The job advert
Senior Platform Engineer, Brightwater Energy (Leeds, hybrid) You'll run the Kubernetes platform our 30 product teams ship on, on AWS. You will own our Terraform modules and CI/CD pipelines, take part in the on-call rota and lead post-incident reviews. You'll mentor engineers and help set platform standards. Must have: production Kubernetes (EKS ideally), Terraform, AWS, CI/CD at scale, incident response. Nice to have: Go, Argo CD, cost optimisation.
The match report
Match estimate
Confidence in this estimate: high
This is our estimate of how your CV reads against this one posting. No recruiter sees it: an ATS ranks you against everyone else who applied, not against a pass mark. Use the asks to strengthen below, not the number.
A strong match: your CV shows EKS, Terraform and CI/CD at the scale the advert asks for. The one must-have to make plainer is incident leadership.
Must-haves: you show 4 of 5. Nice-to-haves: 1 of 2.
The six-second read
Platform engineer who runs EKS for 14 teams
Relevant platform work at a similar scale; senior is believable.
- Ran the EKS platform for 14 product teams
- Deploy time cut from 25 to 8 minutes
First thing they will question
How much of the incident work you led yourself.
Level
The duties read as senior.
“mentor engineers” · “help set platform standards”
Your CV shows senior work too: the same level.
“Ran the EKS platform for 14 product teams” · “Mentored two graduate engineers”
Read from the work the advert describes, not its title, and from the scope your recent roles show. An estimate, like the score.
Say what you did in the incidents, not only that you ran reviews.
Ask yourself: Which incident did you lead, and what changed after it?
Mention Go only if you've written it.
Ask yourself: What have you built in Go?
Only close a gap you can defend in an interview. A requirement you cannot evidence is better left off than invented. Nice-to-haves are the ones the advert itself calls optional: missing some of them is normal.
- 1Name one incident you led
Incident response is a must-have.
- 2Put the 14 teams in your summary
It's the strongest sign of senior scope.
Suggested edits
Each says where it came from. Nothing changes the CV until it's accepted, and one that needs a fact only Alex knows can't be accepted until it's filled in.
- Backed by the CV
Before: Platform engineer with six years running AWS and Kubernetes for payments and health teams.
After: Platform engineer with six years on AWS and Kubernetes; runs the EKS platform 14 product teams ship on.
From your CV: "Ran the EKS platform for 14 product teams"
- Needs a fact from Alex
Before: Led the on-call rota of six engineers and ran post-incident reviews
After: Led the on-call rota of six engineers; ran post-incident reviews that [what changed after them?]
Your CV says you ran the reviews, not what they changed.
- Backed by the CV
Before: Moved 40 services from Jenkins to GitHub Actions, cutting deploy time from 25 to 8 minutes
After: Moved 40 services from Jenkins to GitHub Actions CI/CD, cutting deploy time from 25 to 8 minutes
From your CV: "Moved 40 services from Jenkins to GitHub Actions"
The cover letter
Every claim checked against the CV. Nothing in this letter says more than the CV does.
Now with your own CV
Import your CV, add a job you want, and see your own report in a minute. Free, no card.