A role you actually want goes live at 2pm. You haven't touched your CV in eighteen months. So you spend the night rewriting bullet points instead of sleeping, ship something half-baked at 1am, and hope. This is the default experience, and it's a design failure — not a discipline failure.
The usual fix is a nicer template. That solves the wrong problem. A prettier version of one generic document is still one generic document. What you actually need is a different document for every job — and a way to know it's any good before you send it.
§ 01The problem with one CV
One CV, fifty roles. Every recruiter sees the same template, and none of it speaks to what their specific job asked for. The signal that matters — the part of your history that maps to this role — gets buried under everything else you've ever done.
Worse, a static CV rots. The project you shipped last quarter, the scope that grew, the decision that paid off — none of it makes it in, because updating the document is a chore you only do under deadline pressure.
§ 02What "ready" actually means
A CV is never "done." It's an artifact rendered from your work history for a specific audience at a specific moment. Treat it as the output, not the source, and "ready" stops being a state you maintain by hand.
Capture your work once, as a living technical review. The CV becomes a downstream render — regenerate it per role instead of rewriting it from scratch at midnight.
§ 03Tailoring per job description
Paste the job description. Get three variations, each emphasizing a different slice of your history — leadership, hands-on depth, breadth. Pick the one that fits, edit any bullet, export. The whole loop takes minutes, not a sleepless night.
Tailoring isn't embellishment. The rules are simple:
- Re-emphasize what you actually did — never invent what you didn't.
- Lead with the experience that maps to this role, not your résumé's chronology.
- Drop the bullets that don't earn their place for this specific job.
§ 04The fit score, before you send
You apply, you wait, you get ghosted — and nobody tells you whether the gap was your experience, your framing, or just bad fit. A fit score closes that loop up front: it scores the application against the JD on a 0–100 scale, surfaces the gaps per skill, and gives you a verdict.
If it's a stretch, we say so. If it's a no, we say that too. The point isn't to flatter you into applying — it's to spend your effort where it can land.
§ 05Versioning your career
Every bullet is editable and every version is preserved. Fork a CV, tweak it for one company, roll it back later. Your technical review evolves like a codebase — update it once, and everything downstream moves with it.
§ 06Final thoughts
Stop treating the CV as a document you maintain and start treating it as output you generate. Capture your work, tailor per role, score the fit before you send. Standard profiles are free — no hidden paywall for job seekers — so there's nothing stopping you from being ready the next time a role goes live at 2pm.