How to turn your CV bullet points into interview stories

Your CV is probably the most carefully written thing you'll take into an interview, and it's usually the least prepared. You've spent hours getting each bullet point down to one line. Then the interviewer points at one and says, "Tell me more about that," and you're working out the story on the spot.

The useful way to think about a CV is that each bullet is an interview answer with the story taken out. The result is there, in compressed form. The situation, your reasoning and the difficulties have been cut for space. Getting them back is mostly a matter of asking yourself the right questions, and this guide walks through how.

If you're not familiar with the STAR structure, our STAR method guide covers it first.

What a CV bullet leaves out

A good CV bullet usually has three parts: a verb, a thing, and a result.

Reduced new starter onboarding time from three weeks to eight days by redesigning the induction programme.

That's a strong bullet. It's specific and it has a number. As an interview answer, though, it's missing almost everything the interviewer wants to hear:

• The Situation: Why was onboarding three weeks? Who noticed, and why did it matter?
• The Task: Was this your job, or something you took on?
• The Action: What did "redesigning" actually involve? What did you change first? Who did you have to persuade?
• The difficulty: What got in the way?
• The evidence: How was onboarding time measured, and over how many people?

The CV gets you the interview. The parts it leaves out are what you're scored on once you're in the room.

Five questions that unpack any bullet

For each bullet on your CV, answer these five questions in a few lines. Don't write paragraphs. Notes are enough.

1. What was it like before? This becomes your Situation. Aim for one or two specifics, such as a number, a complaint, or a deadline.
2. Why did it matter, and to whom? This sharpens your Task, and it tells the interviewer you understood the stakes, not just the job.
3. What did I do, in order? This is your Action. List the steps, and for the most important one, add why you did it that way.
4. What got in the way? A person, a system, a deadline, a lack of budget. This is often what makes a story interesting, and it's what CV bullets leave out completely.
5. How do I know it worked? This is your Result, and where the number came from.

The answers to question 4 are usually the ones that make a story memorable, and they're also the answers to most of the follow-up questions you'll get. It's worth spending a little longer on that one.

Worked example 1: a bullet with a number

The examples below are illustrative and the people are fictional.

The bullet:

Reduced new starter onboarding time from three weeks to eight days by redesigning the induction programme.

Unpacked, as notes:

1. Before: HR coordinator at a 300-person housing association. New starters spent most of their first three weeks waiting: laptop not ready, system access requested one at a time, training sessions only ran monthly.
2. Why it mattered: Managers were complaining that new staff couldn't take on work for nearly a month. Two people had left in their first six weeks the previous year, and both mentioned a slow start in exit interviews.
3. What I did:
   • Mapped every step from offer accepted to first real piece of work, with dates, for the last ten starters.
   • Found that most of the delay was IT access, requested only after the start date.
   • Moved the IT and system access requests to the day the contract was signed, using one combined form instead of four, because IT said the separate requests were what slowed them down.
   • Changed monthly training to a recorded version plus a fortnightly live Q&A.
4. What got in the way: IT were wary of setting up accounts before people started, for security reasons. Agreed accounts would be created but stay locked until the first morning.
5. How I know: Tracked "days to first assigned task" for the next 15 starters. Average was eight working days. Exit interviews in the following year didn't mention onboarding.

As a STAR answer, around two minutes:

I was an HR coordinator at a housing association with about 300 staff. Managers kept telling us that new starters couldn't take on real work for nearly a month, and two people who'd left early the year before had both mentioned a slow start.

I wanted to get people doing real work within their first two weeks.

I started by mapping every step for our last ten starters, from accepting the offer to their first assigned task, with dates. Most of the delay turned out to be IT access, which we only requested once someone had started, and through four separate forms. So I combined those into one form and moved it to the day the contract was signed. IT were understandably wary of creating accounts early, so we agreed the accounts would be set up but locked until the first morning. I also replaced the monthly training session with a recording and a fortnightly live Q&A, so nobody was waiting weeks for a slot.

For the next 15 starters, the average time to a first assigned task was eight working days, down from about three weeks. The two-week target was one I'd set myself, so it was good to see it met with a bit to spare.

Notice how much of the answer comes from question 4. The IT concern, and how it was resolved, is the part that shows judgement. It isn't on the CV at all.

Worked example 2: a "responsible for" bullet

Not every CV bullet is an achievement. A lot of them describe duties.

The bullet:

Responsible for weekly performance reporting to the senior leadership team.

This is harder, because there's no story in it yet. A duty is something you did every week. A story is something that happened once. The trick is to find a moment inside the duty where something changed or went wrong.

Ask yourself:

• Was there a week when the report was wrong, late, or questioned?
• Did you change anything about how it was done?
• Did someone ask for something new, and you had to work out how to provide it?
• Did the report ever lead to a decision you can point to?

Say the answer to the third question is yes. Unpacked:

1. Before: Weekly report was a 12-page PDF of tables. Leadership team rarely discussed it.
2. Why it mattered: The new operations director said in a meeting that she didn't read it because she couldn't find what had changed.
3. What I did: Asked her and two other directors what decisions they actually used it for. Cut it to one page: five numbers, each with last week and the four-week trend, and a short "what changed" note at the top. Kept the full tables as an appendix for anyone who wanted them.
4. What got in the way: The finance director preferred the full tables. Kept them in the appendix, so nothing was lost for him.
5. How I know: The one-page summary became the first item on the leadership agenda. Within two months, the director asked for the same format for the monthly board pack.

That's now a strong answer to "Tell me about a time you improved something", "Tell me about a time you dealt with a senior stakeholder", and possibly "Tell me about a time you used data to influence a decision". It came from a bullet that looked like it had nothing in it.

Worked example 3: a team achievement

The bullet:

Delivered migration of 40,000 customer records to a new CRM system on time and under budget.

The risk with bullets like this is that the achievement belonged to a team, and the bullet doesn't say which part was yours. That's normal on a CV. In an interview, it's the first thing a good interviewer will probe.

So before you unpack the rest, answer a sixth question: what was my part, specifically?

Say the honest answer is: "I wasn't the project lead. I was responsible for data cleansing, and I ran the testing for the customer service team." That's fine. It's still a good story, it's just a narrower one. The Situation is the migration. The Task is the data cleansing. The Actions are what you did to get 40,000 records clean, and the Result is how many errors made it through, or didn't.

Telling the narrower story well is far better than telling the wide story vaguely. And if the bullet on your CV implies you led the whole thing, it's worth either rewording it or being ready to explain your part clearly the first time you're asked.

One bullet, several competencies

Once a bullet is unpacked, you'll often find it answers more than one question. The onboarding story from example 1, for instance:

The facts don't change. What changes is which part you spend the most time on. That's useful, because it means a handful of well-unpacked bullets can cover most of a competency interview.

It's still worth having a few different stories, though. If every answer comes back to the onboarding project, the interviewer will start to wonder what else you've done.

Check every number before the interview

Every number on your CV is an invitation to "How did you measure that?" Before an interview, go through each one and make sure you can say where it came from.

• If you can back it up, note the source and the period. "From the HR system, the 15 starters between March and August."
• If it's an estimate, be ready to say so. "That's an estimate from my own tracking, it wasn't formally measured." That's an acceptable answer.
• If you can't remember where it came from, consider softening it, on the CV and in your answer. "Roughly halved" is better than a precise figure you can't explain.

This matters more than it might seem. A number that falls apart under one follow-up question doesn't just weaken that answer, it makes the interviewer wonder about the others.

Bullets that won't hold up

Going through your CV this way sometimes turns up bullets you'd struggle to talk about. Usually they're one of these:

• Too old. Something from several roles ago where you can't remember the detail. Either do the work to remember it, or move it lower down so it's less likely to come up.
• Mostly someone else's. A team result written as if it were yours. Reword it to reflect your part.
• Vague on purpose. "Supported key strategic initiatives." If you can't turn it into a story, the interviewer probably can't either. Replace it with something you can talk about.

It's much better to find these at home than in the interview.

Going the other way: better stories, better CV

Unpacking your bullets tends to improve the CV too. Once you've answered the five questions, you'll often find the bullet was underselling the work, or selling the wrong part of it.

The onboarding bullet, for example, could become:

Cut new starter time to first assigned task from three weeks to eight working days by moving IT access requests to contract signature and replacing monthly training with recorded sessions.

It's a little longer, though it now says what you actually did, which gives the interviewer a better question to ask.

Keeping it all in one place

This is the part Career Canvas is built for. Send us your CV and we turn every project into a STAR story, laid out on one screen. Pick a competency, such as stakeholder management, and the projects that fit light up, each with a one-line reason why.

We don't invent anything. A result only appears where you can back it up, and you approve every word before it goes live, which is the same standard you'd want to hold your CV to anyway.

See an example canvas or get started free.