One career, five CVs: the same years, retold

A CV is not a record of what happened. It is an argument that you should be interviewed, assembled from things that happened. Which is why the same six years can produce five quite different documents without a single invented fact — and why the person who says “my CV just is what it is” tends to get fewer interviews than someone with less experience and more focus.

Below is one ordinary career, aimed at five roles. The CV examples library has full documents by role and career stage; this piece is about the editing decisions behind them.

The raw material

Six years, one sector — a mid-sized distribution business. The unedited list of what this person actually did:

• Two years on a customer support desk, then four in operations.
• Built the weekly stock report in SQL and Power BI, replacing a spreadsheet that took two days.
• Ran the pilot for a new warehouse management system across three sites, then the rollout to nine.
• Wrote the requirements document with the product team of the software vendor.
• Line-managed two junior analysts for eighteen months.
• Renegotiated two courier contracts, saving about 8% of outbound shipping cost.
• Reduced pick errors in the pilot sites by redesigning the pick path.
• Handled escalations from the top twenty accounts during the rollout.

Every version below uses only those facts.

What each reader is scanning for

Five versions of the same six years

1. Operations manager

Operations professional with six years in distribution, covering
warehouse process, courier contracts and reporting across nine sites.

- Rolled out a new warehouse management system from a three-site pilot
  to nine sites, cutting pick errors in the pilot group by a third.
- Renegotiated two courier contracts, taking ~8% off outbound shipping.

The SQL stays, but drops into the skills line. Cost and error rates lead, because an operations manager is hired to move exactly those two numbers.

2. Data analyst

Analyst with six years in distribution, specialising in operational
reporting: SQL, Power BI, and the messy warehouse data underneath.

- Rebuilt the weekly stock report in SQL and Power BI, replacing a
  two-day spreadsheet process with a two-hour refresh.
- Instrumented pick-error reporting across nine sites, which is how the
  pick-path redesign was measured.

Same rollout, different framing: it becomes the place where measurement happened. The courier negotiation drops to a single line, because a data hiring manager will not read past it.

3. Product manager

Operations specialist moving into product, with two years working
alongside a software vendor's product team on a warehouse management
system now live in nine sites.

- Wrote the requirements for the pick-path redesign and ran the
  three-site pilot that validated it before rollout.
- Owned the feedback loop between nine sites and the vendor's roadmap.

This is the hardest of the five, because the title has never been “product manager”. The summary says so plainly. What makes it credible is the artefact — a requirements document — and a pilot with a decision attached to it.

4. Customer success manager

Six years in distribution across support and operations, including
two years as the escalation point for the top twenty accounts during a
nine-site systems migration.

- Held the top twenty accounts through a nine-site WMS migration,
  handling escalations directly and keeping churn at zero.
- Started on the support desk: 40+ tickets a day, then built the
  reporting the desk now runs on.

The support desk, which the other four versions bury, becomes an asset here. Careers are full of experience that is embarrassing in one room and valuable in the next.

5. Project manager

Project lead with six years in distribution operations; delivered a
nine-site warehouse management rollout from pilot to completion,
working across operations, IT, an external vendor and site managers.

- Sequenced the rollout site by site, running the pilot first and
  carrying its findings into the remaining six.
- Coordinated vendor, IT and nine site teams; managed escalations from
  the twenty largest accounts throughout.

Note the vocabulary shift — sequencing, stakeholders, delivery — applied to identical events. That is the legitimate version of keyword matching: using the target discipline’s words for work you genuinely did.

The rules underneath

1. Change the target title, not the job title. The line under your name is positioning; the title inside a role is a fact.
2. Promote, demote, never delete a whole role. Gaps raise questions that emphasis never does.
3. Reorder the skills block. The first group should be the one the advert names first.
4. Re-point two or three bullets, not all of them. The most recent role does most of the work.
5. Use the target field’s vocabulary for what you actually did. Not for what you did not.

Doing it in ten minutes

Keep one master document with every bullet you have ever written for yourself — the long, unedited version nobody sees. Applying then becomes selection rather than composition: copy the master, change the target title, rewrite the summary against the advert, reorder the skills, cut it back to two pages, export.

The candidate who gets the interview is rarely the one who has done the most. It is the one whose document answers the question the reader actually had.

For the mechanics of the four lines at the top, see how to write a professional summary. For role-specific full examples, the CV examples library is organised the same way this article is.