The short answer: name the team result in one sentence, then spend most of your answer on the part that would not have happened, or would have happened worse, without you. Give one piece of evidence for that part, credit at least one colleague by role, and stop. The interviewer is not asking whether the team did well. They are asking what you, specifically, added.
That sounds simple, but this question catches two very different kinds of candidate. Some talk only about “we” and leave the interviewer unable to tell whether they did anything. Others claim the whole success and sound as if they worked alone. The scenarios below show how to find the honest middle in five common situations.
What the question is really measuring
Many competency-based interviews are scored against a short list of behaviours, and this question usually feeds two of them at once. The Scottish Government’s candidate guide to the Civil Service Success Profiles defines Working Together as the ability to “form effective partnerships and relationships with people both internally and externally”, and Delivering at Pace as taking “responsibility for delivering timely and quality results with focus and drive”. One is about the team, the other about you. A good answer gives evidence for both.
There is also a quieter test: whether you understand how teams succeed at all. Your contribution does not have to be the headline feature. Being the person whose work arrived on time and to standard, or the person who made roles and deadlines clear, is a real role, and you can describe it as one.
The three-part split
Before choosing a story, divide the success into three parts in your notes:
- The team outcome. What was achieved, with a number if you have one you can stand behind.
- Your slice. The specific task, decision or behaviour that was yours. If you cannot name it in under ten words, you do not yet know your role well enough to answer.
- Everyone else’s slice. Who did what else. You will mention this briefly, but knowing it stops you overclaiming and prepares you for the follow-up “Who else was involved?”
As a rough guide, in the answer itself give the outcome about 15% of the time, your slice about 70%, and the others the remaining 15%. The UK National Careers Service describes the STAR method’s Action step as “the action you took”, and that is where your slice belongs.
Scenario 1: you led the work
The risk here is sounding as if leadership was the contribution. “I led the team” is a job title, not an action. Say what leading involved on this occasion: the decision you made, the conflict you settled, the plan you rewrote.
Illustrative answer (operations team lead): “Our warehouse team cut order-picking errors noticeably over one quarter. My part was the diagnosis and the new routine. I went through a month of error reports and found most mistakes happened on two shifts where new starters were picking alone. I paired every new starter with an experienced picker for their first two weeks and changed the shift handover so errors were reviewed the next morning rather than at month end. The experienced pickers did the coaching, and they deserve most of the credit for how quickly the new starters improved. My contribution was spotting the pattern and redesigning the routine so they had time to do it.”
Notice what the answer does: it names the outcome, isolates two concrete actions, and gives credit to a group by role without giving away the candidate’s own part.
Scenario 2: you were one contributor among many
This is the most common situation and the easiest to undersell. Pick the one piece that most clearly carried your name, even if it was small, and show how it connected to the result.
Illustrative answer (data analyst): “The marketing team’s campaign beat its sign-up target. I was one of six people on it, and my piece was the audience analysis. I found that our existing customer list contained a segment that had never been targeted separately, built the list, and wrote the brief explaining why it might respond differently. The creative team built the campaign; my analysis decided who saw it first. When the results came in, that segment had the highest response rate, so the team used the same approach in the next campaign.”
Scenario 3: your role was behind the scenes
Coordinators, testers, assistants and support staff often think they have no answer to this question. They usually have the best one, because their contribution is easy to isolate: without it, the visible work would have failed or slipped. Describe the failure you prevented.
Illustrative answer (administrative assistant): “Our department moved offices over a single weekend without losing a working day. I didn’t carry any boxes. My role was the schedule: I built the move plan with the facilities team, checked every person’s equipment list against the IT order, and caught that twelve desks had been booked without network points. Because that was fixed on the Thursday, everyone could log in on Monday morning.”
This is reliability in action. Say plainly that your work was not glamorous; interviewers tend to trust candidates who are realistic about the size of their role.
Scenario 4: you joined late, or the success was mostly someone else’s
Honesty works in your favour here. If you joined a project three weeks before launch, say so, and talk about what you did in those three weeks. If a colleague clearly drove the result, say that too and describe how you supported them. Interviewers often follow up with “What would have happened without you?” A candidate who has already sized their role accurately handles that question easily.
Illustrative answer (junior software developer): “I joined the payments project for its last month, so the architecture and most of the build were done before I arrived. The lead developer deserves the credit for the design. What I owned was the test coverage for refunds, which was the part with the fewest tests. I wrote the missing tests and found two cases where partial refunds were calculated incorrectly. They were fixed before launch.”
Scenario 5: your best example is from university or a first job
Group assignments work well for this question because the split of work is usually documented. Choose one with a clear outcome (a grade, a competition result, a client brief delivered) and use the same three-part split. Avoid stories where the main point is that other members did not pull their weight; that answers a different question about conflict, and it can make you sound as if you are still annoyed.
Illustrative answer (graduate): “Our final-year group project won the department prize. There were four of us. I took responsibility for the survey: designing the questions, getting it approved by our supervisor and collecting 200 responses in two weeks. The others wrote the literature review and the analysis, and one of them presented it. Without the survey data there would have been nothing to analyse, so I see my role as the foundation the rest of the project was built on.”
“I” or “we”: a quick check
Read your draft answer aloud and listen to the pronouns. Neither extreme works.
| If your answer sounds like this | What the interviewer hears | Fix |
|---|---|---|
| “We” in every sentence | Unclear what you did; possibly nothing | Switch to “I” for every action you personally took |
| “I” in every sentence, no one else named | Overclaiming; may be hard to work with | Name at least one other contribution by role |
| “I helped with” or “I was involved in” | A vague, passive part | Replace with the verb for what you did: built, checked, decided, wrote |
| “We” for the outcome, “I” for the actions | A clear, credible role inside a team | Keep it |
Follow-up questions to prepare
- “What would have happened without you?” Answer in one sentence. If the honest answer is “someone else would have done it more slowly”, say that; it is still a contribution.
- “Who else contributed, and how?” Use roles rather than names.
- “What would you do differently?” Pick something within your own slice, not a criticism of colleagues.
- “How did you measure the success?” Only quote figures you can explain. If you do not know the exact number, give the direction and the source (“the monthly report showed errors falling”) rather than inventing precision.
Put the same split on your CV
The interviewer may have chosen this question because a line on your CV says “part of a team that delivered” something. That phrasing invites exactly this probe. Rewriting such bullets so your own action leads (“Built the audience segment for a campaign that exceeded its sign-up target”) makes the CV stronger and gives you the first sentence of your interview answer. The resume examples library shows this action-first pattern across different roles, and the ATS resume score checker can flag bullets that are vague or missing keywords.
Frequently asked questions
How long should my answer be?
Around 90 seconds to two minutes. Keep the team outcome to one or two sentences and spend most of the time on your own actions.
Is it wrong to say the success was mostly someone else’s?
No, if it is true. Say so, then describe your part accurately. Interviewers often check claims with follow-up questions, and a candidate who sizes their role honestly is more credible than one who claims everything.
What if the team succeeded but my part went badly?
Choose a different example if you can. If this is your only strong team story, be brief about what went wrong in your part, say what you did to recover, and focus on what you would now do differently.
Can I use the same story as my answer to “Tell me about a project you are proud of”?
You can, but expect a different emphasis. That question is about why the work mattered to you; this one is about separating your contribution from everyone else’s. Preparing two or three team stories gives you room if both questions come up.
Sources
- Success profiles: candidate guide (behaviour definitions), Scottish Government
- The STAR method, National Careers Service (UK)