For developers applying to many roles

Bespoke CVs, every claim with receipts.

Add your CV once. Then give cv0 a job advert and get back a CV for that job, built only from what you've approved. Every line shows its proof.

Get early access How it works

Paste an advert, or drop a screenshot, PDF or Word file.

Alex Morgan

Senior AI / Backend Engineer

London · hybrid or remote

Summary

Backend engineer with nine years in Python and TypeScript, the last three building LLM features into production health and fintech products.

Experience

Freelance AI engineer 2023 – now

• Built a retrieval pipeline over clinical guidance documents, with an offline evaluation set that gates every release.

Proof Approved 2 Sep · in 3 CVs
CV
Original CV, line 14 · Freelance AI engineer · 2023 – now

• Designed tool-calling agents for claims triage, with human review on every action that writes data.

• Cut model spend by moving routine classification to a smaller model behind a confidence threshold.

Senior engineer, Example Payments 2019 – 2023

• Led the move from a monolith to event-driven services on Postgres and Kafka.

• Owned on-call and incident reviews for the payments platform.

Skills

Python, TypeScript, FastAPI, Postgres, pgvector, Kafka, AWS, LLM evaluation, retrieval

Covers 5 of 6 must-haves

1 weak, 1 with no evidence. Nothing has been stretched to fit it.

Must-have

  • Production Python Strong

    Nine years · summary and both roles

  • Retrieval for LLM systems Strong

    Built a retrieval pipeline over clinical guidance…

  • Evaluating LLM output Strong

    …offline evaluation set that gates every release

  • Regulated domain Strong

    Health and payments roles

  • Agent / tool-calling design Weak

    One project, under a year. Stated as is.

  • Kubernetes in production Missing

    No approved evidence. Left off the CV.

How it works

Your CV once, then one job at a time.

  1. 01

    Add your CV.

    Drop, pick or paste it. Approve or reject each role, project and skill it finds.

  2. 02

    Give it a job.

    Paste the advert, or drop a screenshot, PDF or Word file of the spec.

  3. 03

    See the fit.

    Every requirement is matched against what you’ve approved. Gaps are shown as gaps.

  4. 04

    Approve and share.

    You approve the exact CV and share a link to it. The application keeps the version you sent.

The receipts

Rewriters polish wording. cv0 starts from evidence.

Every line traces back to something you did and approved, starting with your own CV. For developers, more of it lives where a CV tool never looks, and that's next.

CV
Your existing CV, line by line.
omnirecall
Your archived AI coding sessions: what you built, debugged and shipped. Coming next
git
Commits in the repositories you choose. Coming next

The proof stays with you. The recruiter sees a clean CV.

Senior AI Engineer · Northwind Health

Covers 5 of 6 must-haves

1 weak, 1 with no evidence. Nothing has been stretched to fit it.

Must-have

  • Production Python Strong

    Nine years · summary and both roles

  • Retrieval for LLM systems Strong

    Built a retrieval pipeline over clinical guidance…

  • Evaluating LLM output Strong

    …offline evaluation set that gates every release

  • Regulated domain Strong

    Health and payments roles

  • Agent / tool-calling design Weak

    One project, under a year. Stated as is.

  • Kubernetes in production Missing

    No approved evidence. Left off the CV.

Honest fit

A gap is shown as a gap.

Each requirement in the advert is marked strong, weak or missing. If you can't back something up, cv0 says so and leaves it off the CV. Nothing is stretched to fit.

Weak evidence is stated as it is: one project, under a year, says exactly that.

Tracking

Tracking that doesn't lie.

  • Silence isn't rejection. Nothing moves to Rejected unless you move it.
  • Every figure shows its time window and how many applications it's based on.
  • Each application keeps the exact CV you sent.

Submitted 2

Staff Platform Engineer Northline Logistics No reply for 17 days
AI Engineer Fernhill Studio CV v1 · 6d

Screen 1

LLM Platform Engineer Corvid Analytics CV v2 · 4d

Interviews 1

Senior Backend Engineer Harbour Payments CV v3 · 3d

Funnel

Example · last 90 days · 14 applications · distinct applications, not events

  • Saved Starting point
  • Submitted 45% of saved
  • Screen 43% of submitted
  • Interview 67% of screen
  • Offer 1 of 4 · too few for a %

Shared CVs

See when your CV is opened.

  • Your main CV and each job's CV get their own link. Turn any of them off.
  • See which CV was opened, when, from where and on what device.
  • Link previews and known bots stay out of the count, and so do your own views.
  • Free, for as long as you have an account.
Opens
189
People, not bots
Links
4
Main CV and 3 jobs
Previews
6
Where it was shared
Last opened
Today
Any link

Opens

Last 30 days · 189 opens · a reload within 30 minutes counts once · UTC days

Last 30 days: 189 opens of your shared CVs: Main CV 57, Harbour Payments 56, Corvid Analytics 47, Fernhill Studio 29.

Opens by CV

Your main CV beside each job's

  1. Main CV 57
  2. Harbour Payments 56
  3. Corvid Analytics 47
  4. Fernhill Studio 29

Sources

Where the link was opened from

  1. Email 87
  2. linkedin.com 62
  3. Direct 40

Link previews

Apps that fetched a link card: where it was shared, not opens

  1. Slack 3
  2. Microsoft Teams 2
  3. LinkedIn 1

Your experience is yours.

Your sources are only searched where you allow it: you pick the projects and repositories.

Questions

No. Every line on a CV comes from a record you've approved, and every record quotes the line of your CV it came from. Anything reworded starts unapproved and stays that way until you approve it.

Give it a job.

See the fit, and a CV for that job, built from what you've actually done.

Get early access