"Tell me about a time you worked in a team": how to answer, with examples
Updated · 4 min read
"Tell me about a time you worked in a team" is probably the most common competency question there is. You'll see it on graduate scheme forms, retail applications, university interviews and senior job interviews alike, sometimes in disguise: "Describe a time you collaborated with others", "Give an example of a successful group project".
What the employer is really asking
Nearly every job involves working with other people, so they want evidence that you:
- pull your weight and deliver your part on time
- listen to other people and value what they bring
- help the group when it gets stuck, rather than waiting for someone else to
- can handle disagreement without it turning into a falling-out
The trap is describing the team instead of yourself. "We built an app and it went well" doesn't tell them anything. They need to know what you did to make the team work.
How to structure it
Use the STAR method: a sentence on the Situation, a sentence on your Task, most of your words on your Actions, then the Result. For teamwork, the best actions usually involve one of: organising how the team worked, helping a teammate, sorting out a disagreement, or bringing a skill the team was missing.
Example 1: a university group project
In my second year I was one of five students building a booking app for a local gym, worth 40% of our module mark. Three weeks before the deadline we were behind, because two of us had been building the same feature without realising. I suggested a 15-minute stand-up every morning and set up a shared task board so everyone could see who was doing what. I also paired with our newest team member on the payments screen, the part she was least confident with. We caught up within a week, handed in two days early and got 74%, the highest mark in the cohort. I've used short daily check-ins in every group project since.
- A clear problem the team faced, not just "we did a project".
- Specific actions that are obviously the writer's own.
- A measurable result and a lesson they kept using.
Example 2: a part-time job
I worked Saturdays in a busy café where the morning rush regularly overwhelmed the team of four. Orders were getting mixed up and customers were waiting up to 15 minutes. I noticed we all crowded the till and coffee machine at once, so I suggested we each own one station during the 9 to 11 rush: one on the till, two on drinks, one on food and clearing. I offered to train the newer staff on the coffee machine so anyone could cover it. The manager agreed to try it for a month. Waiting times dropped to around five minutes, complaints stopped, and the system was adopted for weekday shifts too.
- Shows teamwork in a non-office setting, which is completely valid.
- The writer spotted the problem, proposed the fix and helped others.
- Before and after numbers make the result concrete.
Example 3: working with someone difficult
In my first graduate role I shared a reporting project with a colleague who often rewrote my sections without telling me, which led to duplicated work and a missed draft deadline. Rather than escalate it, I asked if we could grab a coffee and talk about how we were splitting the work. It turned out he was worried about the client's reaction, because a previous report had gone badly. We agreed he'd own the client-facing summary and I'd own the analysis, with a 10-minute review together before anything went out. The next three reports went out on time with no rewrites, and our manager asked us to work together on the following quarter's project.
- Stays fair to the other person; no blaming.
- Shows the writer tried to understand the other side.
- Ends with a practical agreement and a clear improvement.
Common mistakes
- Saying "we" all the way through. Swap in "I" wherever it was genuinely you.
- Picking an example where nothing went wrong. A team that sailed through gives you nothing to talk about. Pick one with a problem you helped solve.
- Spending half the answer on background. One or two sentences of context is plenty.
- Making yourself the hero and everyone else useless. Good teamwork answers make the team look good too.
- No result. Always say how it ended and, if you can, give a number.
Save it once, adapt it forever
You'll be asked this question dozens of times across a job hunt, worded a little differently each time. Once you've written a strong teamwork answer, keep it, with its shorter versions, so the next form takes minutes instead of an evening.
Frequently asked questions
- Can I use a university or school example?
- Yes. For graduate and entry-level roles, group projects, societies, sport and volunteering are expected and perfectly good examples.
- Should I talk about a time the team failed?
- You can, if you show what you did to help and what you learned. But for a straight teamwork question, an example where your actions helped the team succeed is usually stronger.
- How do I answer if I prefer working alone?
- Be honest but balanced. Say you work well independently, then give an example showing you also collaborate well when the work needs it. Almost every role needs both.