Example fit report

Fictional candidate and posting

Imogen Tredwell × Senior Site Reliability Engineer

The candidate and the posting are fictional. Checked on October 21, 2026. The same posting returns this same report.

How to read it

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

Example fit report

1 · The score

Match score 96 out of 100 — Strong match

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

Must-haves · 10 of 11 + 1 partly
Nice-to-haves · 2 of 2
  • Covered must-have
  • Covered nice-to-have
  • Partially covered
  • 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 five years in site reliability, platform or infrastructure engineering roles.Must-have
    From the sample CVSenior Site Reliability Engineer
  • CoveredProduction experience running Kubernetes, ideally AKS.Must-have
    From the sample CVRun six AKS clusters hosting around 140 services; availability was 99.97% over 2025 against a 99.9% SLO.
  • CoveredStrong hands-on experience with Microsoft Azure.Must-have
    From the sample CVWrote the Terraform for all Azure infrastructure across four subscriptions, added drift detection to the GitHub Actions pipelines, and moved application deployments to Flux.
  • CoveredTerraform for infrastructure as code.Must-have
    From the sample CVWrote the Terraform for all Azure infrastructure across four subscriptions, added drift detection to the GitHub Actions pipelines, and moved application deployments to Flux.
  • CoveredObservability with Prometheus and Grafana or similar tools.Must-have
    From the sample CVPrometheus
  • CoveredExperience defining SLOs and error budgets with product teams.Must-have
    From the sample CVDefined SLOs and error budgets for 18 services with their product owners; paging alerts fell by 58% within six months.
  • CoveredYou have led major incidents as incident commander and run the blameless postmortems that followed.Must-have
    From the sample CVIncident commander for 23 P1 and P2 incidents in 2024 and 2025; after I introduced a runbook library and a severity matrix, median time to mitigate fell from 74 to 31 minutes.
  • CoveredAutomation in Python, Bash or PowerShell.Must-have
    From the sample CVAutomated server builds and patching with Ansible and PowerShell; monthly patching went from two days of manual work to a scheduled pipeline in Azure DevOps.
  • CoveredBuilding and maintaining CI/CD pipelines in GitHub Actions or Azure DevOps.Must-have
    From the sample CVWrote the Terraform for all Azure infrastructure across four subscriptions, added drift detection to the GitHub Actions pipelines, and moved application deployments to Flux.
  • CoveredSolid Linux administration.Must-have
    From the sample CVLooked after around 250 Linux servers running Red Hat Enterprise Linux and Ubuntu, and the VMware estate they ran on.
  • Partially coveredExperience running a service mesh such as Istio or Linkerd in production.Must-have
    From the sample CV

    Related area — “Led a four-week proof of concept of Linkerd on a staging cluster; after a cost and benefit review the team decided not to roll it out to production.” — not the one the posting asks for.

  • CoveredOperating managed PostgreSQL on Azure.Nice-to-have
    From the sample CVOperate Azure Database for PostgreSQL Flexible Server for 11 databases: backups, quarterly point-in-time restore drills and failover tests. Query tuning and schema design stay with the development teams.
  • CoveredExperience with GitOps tools such as Flux or Argo CD.Nice-to-have
    From the sample CVmoved application deployments to Flux

3 · What to lead with

Imogen Tredwell's strongest angle for this role

Running AKS in production with SLOs and incident command, the core of what this reliability team asks for

Points Imogen Tredwell could make, each backed by a line of the CV:

  • The posting's first duty is running AKS and the Azure services around it. The record shows six production clusters with availability measured against an SLO.

    From the sample CVRun six AKS clusters hosting around 140 services; availability was 99.97% over 2025 against a 99.9% SLO.

  • The posting asks for SLOs and error budgets set with product teams, and the record shows exactly that, with a measured effect on alerting.

    From the sample CVDefined SLOs and error budgets for 18 services with their product owners; paging alerts fell by 58% within six months.

  • Incident command is both a duty and a requirement, and the record shows 23 incidents led with a measured improvement in time to mitigate.

    From the sample CVIncident commander for 23 P1 and P2 incidents in 2024 and 2025median time to mitigate fell from 74 to 31 minutes

  • Owning the Terraform and the pipelines that apply it is a stated duty, and the record shows both.

    From the sample CVWrote the Terraform for all Azure infrastructure across four subscriptions, added drift detection to the GitHub Actions pipelines

A paragraph Imogen Tredwell could use

I am a site reliability engineer with eleven years in operations, working on Microsoft Azure since 2018. At Aireside Health Systems I run six AKS clusters hosting around 140 services, and I wrote the Terraform for all Azure infrastructure across four subscriptions. I defined SLOs and error budgets for 18 services with their product owners, and paging alerts fell by 58% within six months. I have been incident commander for 23 P1 and P2 incidents in 2024 and 2025, and median time to mitigate fell from 74 to 31 minutes. The posting asks for a service mesh in production. I led a proof of concept of Linkerd on a staging cluster, but I have not run one in production.

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.

  • The CV lineRun six AKS clusters hosting around 140 services; availability was 99.97% over 2025 against a 99.9% SLO.
    Framing

    Keep the AKS bullet first in the current role, since it answers the posting's first duty and first technical requirement.

  • The CV lineDefined SLOs and error budgets for 18 services with their product owners; paging alerts fell by 58% within six months.
    Numbers

    Keep the 18 services and the 58% drop in paging alerts visible, because the posting links SLOs to tuning alerting.

  • The CV lineIncident commander for 23 P1 and P2 incidents in 2024 and 2025; after I introduced a runbook library and a severity matrix, median time to mitigate fell from 74 to 31 minutes.
    Wording

    Mention blameless postmortems next to the incident command bullet, since the posting asks for both and the skills list already names them.

  • The CV lineLinux Systems Administrator · Chapel Allerton Hosting Ltd
    Length

    Keep the earliest role short, since the posting needs only solid Linux administration from it.

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 fitTry a sample candidate on your posting