There is a specific way this answer goes wrong, and almost everyone does it. They describe a group that did a thing. "We had a project, we split the work, we delivered it on time." Every sentence is "we". By the end the interviewer knows a team succeeded but has no idea what you were, whether you led, followed, held it together or simply attended.
The fix is not to grab all the credit. It is to make yourself visible inside the group without erasing anyone else. That balance is the actual competency being tested.
The trap of "we"
When you say "we", the interviewer cannot score you, so they have to guess, and interviewers guess low. The habit is worth catching because it feels like modesty while functioning as invisibility.
Watch the difference:
- Invisible: "We realised the timeline was slipping, so we reprioritised."
- Visible: "I could see the timeline was slipping before the others had clocked it, so I mapped what was actually blocking us and suggested we drop two of the nice-to-haves. The group agreed and we protected the deadline."
Same event. The second version has a person in it. Note it does not steal anything: the group still decides, the win is still shared. You have just made your contribution legible.
What good teamwork looks like from the other side of the desk
Interviewers are not really asking whether you can cooperate. Most people can. They are probing for one of three things, and it helps to know which your example demonstrates:
- You made the team better, not just present in it. You unblocked someone, spotted a risk, mediated, covered a gap.
- You can subordinate yourself when the plan is not yours. Backing someone else's idea and executing it well is a genuine strength, and rarer than people think.
- You read the room. You noticed a quieter member being talked over, or tension building, and did something about it.
Pick an example that lets you show one of these clearly, rather than a generic "we all pulled together".
A worked example
"In my final year we had a group consultancy project for a real charity client, five of us, and it went wrong early. One member basically disappeared for the first fortnight, and the rest of us were annoyed and starting to work around him, which meant his section was going to be missing.
I did not want to escalate it to the tutor, because that felt like giving up on him, so I messaged him privately rather than in the group chat and asked if everything was okay. It turned out he was struggling with something outside university and had assumed we would all be furious, so he had gone quiet rather than face it.
We agreed a smaller, well-defined chunk that he could realistically deliver, and I checked in once without nagging. He got it done, and honestly his section on the funding landscape ended up being one of the strongest parts. We handed in on time and the client used two of our recommendations.
What I learned was that the obvious read on a quiet team member is usually wrong, and thirty seconds of asking beats two weeks of resenting."
Why it lands
The candidate did not describe a smooth team. They described a team with a real fault line and showed judgement in how they handled it: a private message instead of a public callout, a boundary that was still generous (a smaller chunk, not a free pass), and a check-in calibrated so it was not nagging. That is emotional intelligence demonstrated through a decision, which is worth far more than the phrase "I have strong emotional intelligence".
It also resists the temptation to be the saviour. The teammate delivers his own work and gets credit for it. The candidate's role is the catalyst, not the star, and interviewers trust that more.
Common mistakes
Choosing a team that had no friction. A team where everything went perfectly gives you nothing to demonstrate. Mild conflict, a missed deadline, a disagreement over direction: these are the moments where teamwork is actually visible.
Being the lone hero. If your story is really about you rescuing four passengers, it is a leadership answer wearing a teamwork costume, and it makes you sound like someone who cannot delegate. If you have a genuine leadership example, save it for that question and choose something more collaborative here.
Forgetting the outcome. "And it went well" is not an outcome. What did the team produce, and what was your fingerprint on it.
No standout team example?
You have more than you think. A part-time shift where you covered for a colleague mid-rush, a sports side where you changed a tactic, a flatshare that had to sort out a genuine problem. The STAR structure works on any of these. What the interviewer wants is not a prestigious team, it is a clear view of you inside one.
The quickest way to hear whether your "we" has crept back in is to say the answer aloud and count the first-person verbs. If you can practise it and get the balance flagged for you, you will walk in already knowing your story has a person in it.