Describe a Time You Worked in a Team: Example Answers

Teamwork questions are the ones students most often answer with a story about the team and not about themselves. “We all pulled together and got a great mark” is a review of the group; it tells the interviewer nothing about you. The question is asking which part was yours, what went wrong in the middle, and what you did about it for the other people in the room. It turns up in nearly every Kira set, in Sauder’s and Queen’s Commerce videos, and in supplementary applications as “describe a time you contributed to a group.”

By the AcceptMe team 7 min read Updated

What the interviewer is listening for

Students hear “teamwork” and reach for the project that went best, on the theory that a happy team is the point. It isn’t. The interviewer already assumes you can be pleasant in a group; almost everyone can. They’re listening for three things:

  • Your specific role. Not “we” for ninety seconds. Which part was yours, what you decided, what you were not good at. If any other member of the team could tell the story word for word, it isn’t your story yet.
  • Friction. Every real team has a moment where two people wanted different things, someone went quiet, or the plan stopped working. The story needs that moment, because how you behaved in it is the only evidence of teamwork there is. A team that never disagreed is a story about luck.
  • What you did for the group, not just for yourself. The strongest teamwork answers contain a moment where you made someone else’s work easier: you took the task nobody wanted, covered for the person who was drowning, or changed your own plan so the group’s plan would hold.

Any question in this family can be answered with a story that has those three parts. The STAR structure gives you the order; the trick with teamwork is keeping the “A” in the first person.

Three example answers

Example one: a school project that stalled

In Grade 11 I was in a group of four for a biology ISU, a twenty-four slide presentation on antibiotic resistance. For the first ten days the group chat was basically me sending links and nobody replying. One person had never made a slide deck before and was clearly avoiding it, and another wanted to do the whole thing the night before, which she said out loud. So I did the boring thing: I split the deck into four sections by what people were actually good at, gave the person who was avoiding it the section with the most pictures and the least writing, and took the data section myself because nobody wanted it. Then I booked two twenty-minute calls instead of one long one, because I’d noticed people would show up for twenty minutes. The night-before person still did most of hers late, but it was one section, not the deck, and we got 88. What I’d point to is that my job turned out not to be the content. It was the calendar, and I didn’t know that was a job until nobody else did it.

Example two: a part-time job on a Friday close

I work at a pizza place, and Friday closes are three of us: one on the counter, one on the ovens, one on dishes. Last fall a new guy started on dishes, he was fifteen, and every Friday he was still going at half past midnight while the two of us stood around waiting to lock up. The shift lead’s view was that dishes was his job and he’d get faster. Mine was that all three of us were staying late either way. So I asked if we could try rotating: whoever finished their station first swapped onto dishes for ten minutes. She wasn’t keen, because it meant the counter was empty for ten minutes, so I offered to do it only after the last order. We tried it for three Fridays and the close went from about 12:40 to 12:10, and he stopped looking like he wanted to quit. The thing I learned is that at a job, teamwork is mostly noticing who is drowning before the manager does, and then asking instead of just doing it, because the manager has reasons you can’t see from the dish pit.

Example three: robotics, when my part was useless

I’m on our school’s robotics team, on the code side. Build season is six weeks, and by week four the build team was still two weeks behind, which meant the three of us on code had written a full drive program with nothing to test it on. We were annoyed, and honestly we said so in a way that wasn’t useful. The build lead’s point, when I actually asked, was that they were down to two people because someone had left the team in January. So I moved over to build for a week, mostly drilling and wiring, which I’m bad at and don’t enjoy. We lost a week of code polish, but the robot drove at the regional and we placed ninth out of twenty-two, which for us is good. I keep thinking about the fact that my part being excellent and untestable was worth exactly nothing. The team’s result is the only one that counts, and sometimes that means doing the job you’re worst at.

Story shapes that work

  • The divider. The group had no plan; you built one that matched tasks to people. Strong because the role, the friction and the “for the group” part are all visible. Example one.
  • The swap. You moved to where the team needed you, away from where you wanted to be. Rare in student answers, and readers know it. Example three.
  • The ask. You noticed a person struggling and asked the person in charge to change something, rather than either ignoring it or going around them. Example two.
  • The quiet one. Someone else’s idea was better than yours and you backed it, publicly, and helped make it work. Undersold, because it feels like a story about not doing anything, but it is the one most interviewers wish they heard more.

The one that quietly backfires

The story that goes: we had a project, we all worked really hard, we communicated well, everyone did their part and we got a great result. Told that way, it puts the interviewer in a bind. Nothing in it is false, but there is no “I,” no moment where anything went wrong, and no decision. They cannot score it because there is nothing in it to score. It ends up as a story about a nice group of people who were not, as far as anyone can tell, you. The “great result” is a second problem on its own. The most common gap we see in a first run is a result with no weight: “we did really well,” where “we got 88” or “the close went from 12:40 to 12:10” would tell the reviewer the size of what happened.

The tell is the pronoun count. If your first four sentences are all “we,” you are reviewing the team. The fix is not to switch to “I” everywhere, which produces the opposite failure: the story where you did the whole project yourself while the others let you down, which is a story about not being on a team at all. The fix is to find the one moment where you did something that changed what the group did, and start the story a sentence before that moment.

A test for any teamwork story: name the moment where the group would have done something different if you had not been there. If you can, build the answer around it. If the honest answer is “it would have gone about the same,” pick a different story, even a smaller one.

Other ways the question gets asked

  • Describe a time you contributed to a group.
  • Tell me about a time you worked with someone very different from you.
  • Tell me about a team that struggled. What did you do?
  • What role do you usually take in a group, and why?
  • Describe a time you had to rely on other people.
  • Tell me about a time you disagreed with your team.

Same story bank, same three parts. The variations shift the emphasis: for “contributed to a group,” lead with the thing you did for other people and keep the result short. For “someone different from you,” the friction is the difference, so name it plainly (a night-before person and a plan-early person, a talker and a quiet one) and spend the answer on how you adjusted. For “what role do you usually take,” answer with the role and then prove it with a thirty-second version of one of these stories, because a role with no story is just a personality-test word. For “disagreed with your team,” you are being asked the conflict question in a friendlier costume, and it wants the conversation you had.

Where to go from here

Teamwork and leadership are asked side by side and get confused in the same direction: the leadership guide explains that leadership needs you to have moved the group, while teamwork only needs you to have moved for it. If the friction in your best story was a real argument, the conflict guide shows how to tell it without a villain. If you are convinced your only teams were school groups, the no-ECs guide pulls stronger material out of a part-time job and a family. Then say it out loud: AcceptMe’s Story Bank coach will interview you about teamwork, ask which part was yours and where it got awkward, and keep nudging until the outline holds together; students are usually surprised that a few scrappy half-answers is all it needs to get there. Teamwork is free, and the interview tool will put one of the six variations above on a clock and show you the transcript, so you can count the “we”s yourself.

Keep reading