The CV you haven't touched
in three years is costing you

Note: we use "CV" and "resume" interchangeably here. Same document, different name depending on where you are (resume in the US, CV in the UK and most of Europe).

Ask ten professionals when they last meaningfully updated their CV. Most will answer with some version of "during my last job search", which was two, three, sometimes five years ago. The document sitting in their Downloads folder isn't just outdated. It's actively misleading about who they are now.

Then the moment comes: layoff, recruiter outreach, a role they actually want, a quick turnaround on a referral. They pull up the ancient file and have to reconstruct 2–3 years of work from memory, half of which they've forgotten the specifics of. The result is a worse CV than they could have written if they'd been keeping up with it the whole time.

This is one of the most widely shared unforced errors in career management. It's also one of the easiest to fix. The fix isn't a bigger rewrite. It's smaller, more frequent maintenance.

Why reconstruction doesn't work

Memory decays faster than people realize. Specific numbers (how much ARR grew, how many direct reports you had in Q3, how long the project actually took) are the most perishable, and specific numbers are exactly what makes a CV bullet strong versus generic.

The person looking at their CV two years after the fact and trying to describe a project typically produces something like: "Led migration of services across infrastructure, improving performance and reliability." The actual, remembered-at-the-time version would have been: "Led migration of four services off legacy queue to Kafka over eight weeks; reduced p95 latency from 180ms to 62ms and cut on-call incidents by 40%."

The second bullet is ten times stronger than the first. It's the version that would have been written in the moment. It's also the version that now doesn't exist, because nobody wrote it down, and you can't recall numbers from two years ago.

Reconstruction fails because it's compressing years of detailed work into a few words from a fading memory. Maintenance works because it captures the detail while it's still sharp.

What "keeping your CV current" actually means

Not "rewrite the whole thing quarterly." That's both too much work and wrong in scope: most of the CV doesn't need to change.

What it means in practice is three different kinds of updates, at three different cadences.

1. The quarterly wins log (15 minutes per quarter)

Once a quarter, spend fifteen minutes adding 2–5 new bullets to a running "wins log." Not polished CV copy: just the raw material for future CV copy.

Each bullet should include:

• What you actually did
• The specific outcome or number
• The time context (Q2 2026, not "recently")

This is not an exercise in self-promotion. It's a memory capture exercise. You're writing down things you'd otherwise forget, not for the CV yet, just so the material exists when you need it.

Examples of what belongs in a wins log:

• "Shipped feature X; lifted activation from 18% to 27% in first three weeks post-launch."
• "Led hiring for two senior ICs; both accepted offers within 30 days of first contact."
• "Refactored billing service; cut webhook latency from 800ms p99 to 120ms."
• "Ran pricing experiment; found 18% lift at higher tier, informed Q3 pricing reset."
• "Mentored three junior team members; one promoted to senior in six months."

Keep it in a plain text file, a Notion page, or a dedicated doc. It doesn't need to be pretty. It needs to exist.

2. The semi-annual CV pass (60 minutes every six months)

Twice a year, open the main CV. Go through recent roles. Ask:

• Which of the wins log items belong as new bullets on the current role?
• Which existing bullets are now less representative of the work and should be replaced or edited?
• Are there skills to add to the skills section? (Tools you've started using, certifications you've completed, languages you've improved.)
• Has the summary become stale? If your focus has shifted (you moved from pure IC work to half-time team lead, say) the summary needs to reflect that.

This is a focused editing session, not a full rewrite. An hour is usually plenty.

The value: the CV is always close to shippable. When a recruiter messages or a role comes up, you're not starting from a two-year-old document: you're starting from one that's at most six months stale.

3. The annual narrative review (30 minutes, yearly)

Once a year, step back and ask a different question: does this CV tell a coherent story about where my career is heading?

If you've been an IC for six years and your target is moving into management, the CV needs to show leadership signals (mentorship, hiring involvement, RFC authorship, team-lead-by-osmosis) that you might not have highlighted when you were focused on individual output. If you're pivoting from one industry to another, the CV needs to describe your current work in language that reads as relevant to the target industry.

This review is less about what happened and more about what story your CV implies. The story should point in the direction you want your career to go, not just describe where it's been.

The specific signals that indicate staleness

If you haven't touched your CV recently and are wondering whether it's stale, these are the tells.

Recent roles have fewer bullets than older roles. If your three-year-old role has six bullets and your current role has three, the CV is stale. The current role should have the most detail because it's the most recent and usually the most relevant.

No dates in the last twelve months. Check the "certifications" section, the "projects" section, any ongoing responsibilities. If the most recent date on the document is 18 months ago, the CV hasn't been opened in at least a year.

Skills section lacks tools you use daily. Pull up the skills section. Are the tools you actually spend time in every day represented? Or is the list a museum of tools you used two jobs ago? Common staleness: using GraphQL / Kubernetes / dbt / Snowflake for a year or more and the CV still lists only the stack from your previous job.

The summary describes your past role. If your summary still says "product manager at SaaS companies" but you've been a director for the past eighteen months, the document is operating on old identity.

You forget whether something is on it. If you have to open the file to remember what it says, you're not treating it as a living document. It's archival material.

The reason this gets skipped

Maintaining the CV feels like a chore with no immediate payoff. You're not job-searching. You're not due for a review. The document will sit in a folder anyway.

Three reasons this reasoning is wrong:

1. Opportunity is unpredictable. The roles that matter most often come when you're not looking: a recruiter reaching out with a surprisingly good fit, a friend telling you about an opening at their company, a promotion opportunity at a different team. These events have compressed timelines. Having a near-current CV means you can respond in a day instead of a week, and in a week the opportunity might be gone.

2. The quarterly log captures memory that would otherwise decay. Even if you never update your CV, keeping the wins log preserves material you'd otherwise lose. Two years from now, the log will still have the specific numbers from today. That asymmetry compounds.

3. Maintenance is cheaper than reconstruction. Fifteen minutes per quarter × 4 = 1 hour per year. Reconstruction when you next need the CV seriously is 6–10 hours of frustrated recall. The maintenance path uses less total time and produces better output.

The tools question

You don't need a dedicated tool for this. A Notion page, a text file, a Google doc, anything works. What matters is that it exists and you actually add to it.

The tools that do help are the ones that keep your CV close to shippable at all times. A tool that stores your career history as structured data and produces polished output from it means "updating your CV" stops being a manual formatting exercise. Which is dramatically lower-friction, which means you're more likely to actually do it.

The key shift is mental, not tooling: treating the CV as a living record of your career, updated a little regularly, rather than as a document you painfully build from scratch every few years. The tooling just follows from that decision.

A simple annual schedule

If you want a concrete rhythm, here it is:

• First week of each quarter: 15 minutes. Add wins log items for the quarter that just ended.
• First week of July: 60 minutes. Mid-year pass. Edit CV bullets, update skills, revise summary.
• First week of January: 90 minutes. Year-end pass: the same bullet/skills/summary edit as July, plus a narrative review of where the last year went and where the next one is pointing.

Total annual time: about 3 hours. Return: a CV that's always close to shippable, and specific career details preserved while still fresh.

The closing thought

The person who spends 3 hours a year maintaining their CV has a materially better document than the person who spends 15 hours every 3 years reconstructing it from nothing. The math is obvious once you see it. The psychology of "I'll do it when I need it" is what keeps most people from seeing it until they urgently need the output and discover they've lost the input.

Don't wait to need it. Keep it current, in small increments, and the document will always be ready when the opportunity is. For what to actually do with a fresh CV when an opportunity does come, see CV tailoring: what actually changes from one application to the next.

Jobiz is built to make the small-quarterly-update habit low-friction enough to actually stick, which is usually the real blocker. If the maintenance keeps falling off, that's the part worth outsourcing.