In this article
Before you start
This page is one step of the behavioral interview questions guide.
Why interviewers ask this
A teamwork story that rambles leaves the interviewer unable to tell what you personally did, and that is the one thing the question exists to reveal. A behavioral question is a question that asks about a specific past experience rather than a skill or an opinion. ORISE (accessed 2026-10-26) says these questions look at how candidates reacted in specific situations and lists teamwork among the usual topics. Wikipedia (accessed 2026-10-26) describes STAR as a technique employers use to evaluate candidates on such questions. The research behind this style of interview is old: Janz (1982) compared patterned behavior description interviews, which ask candidates to describe their past behavior, with unstructured interviews.
A weak teamwork answer describes a happy group and never says what the speaker did. A strong answer shows a real team, a real obstacle, one clear personal contribution and an outcome the team shared. Teamwork questions also sit next to neighbors such as interpersonal communication and influencing without authority, so a good story can often serve more than one of them.
Teamwork STAR from first principles
- Teamwork STAR answer
- A teamwork STAR answer is a short spoken story about working with other people that follows the order situation, task, action, result, names the team once in the situation, and uses "I" in the action so the listener can see your own part.
- Contribution line
- A contribution line is a sentence in the action step that says what you personally did, in the first person and with a verb, such as "I wrote the draft" instead of "we got it done".
In plain words
Think of a game recap. "Our team won" says nothing about the player who scored. A good recap names the game, the goal that was needed, who made the pass and the final score. A teamwork STAR answer is that recap about your own work. The analogy breaks in one place. A recap is written by an observer, but in your answer you are the narrator, so you must pick your own part out of the group.
The STAR method is a structured way to answer behavioral and situational questions, and STAR stands for situation, task, action and result (Indeed, accessed 2026-10-26). In one precise sentence, a teamwork STAR answer names the team once, then follows your own steps to a result. The story can come from work, school or volunteering, as long as your own action is clear.
Step 1: Situation gives the context and names the team
The situation is the part of the answer that gives context: where you were, who was on the team and what was at stake. Indeed (accessed 2026-10-26) summarizes it as context for your answer. For a teamwork question this is the one place where "we" and "our team" are the right words.
Input: a real project with other people in it. Output: one or two sentences with the team size, the deadline or stake, and the trouble. In the sample answer below the situation is a team of five, a three-week deadline and a delay of four days (all illustrative), and it takes 24 words.1 Leave out the company history and the names of every person. The interviewer needs just enough to picture the problem.
You now know what to set up. Next you state the part that was yours.
Step 2: Task states your goal and your role
The task says what you were trying to achieve and what your role in it was. The University of Cincinnati page frames it as your goal; Indeed (accessed 2026-10-26) frames it as the challenge and your role. Some performance methods call this step "Target" rather than "Task" (Wikipedia, accessed 2026-10-26).
Input: the situation. Output: one sentence that separates your responsibility from the team's. A goal you can measure helps. The Cincinnati page gives a college newspaper example whose task is to raise advertiser numbers by at least 15% over the previous year (University of Cincinnati, accessed 2026-10-26). In the sample answer the task is to own the data export piece and bring the team back on schedule, 21 words.1
Now the interviewer knows the problem and your job in it. The next step is the one they listen to most.
Step 3: Action says what you did, in the first person
The action is the step where you describe what you did, and it is where a teamwork answer is won or lost. Both the University of Cincinnati and Indeed (accessed 2026-10-26) tell you to say "I" instead of "we" here to show your individual contribution. Indeed adds that this part needs the most in-depth description because it largely indicates your fitness for a role.
Input: the task. Output: two or three contribution lines. (wrong) "We talked it over and we got it done." (right) "I listed every open task with its owner, then wrote the draft interface and asked the teammate who knew the consuming side to review it."
Saying "I" does not mean taking all the credit. Put other people in your verbs: you asked, reviewed, handed over or agreed with them. That shows teamwork and your own part in the same sentence. The sample action takes 49 words, the largest share of the answer: the action holds 36.8% of the words of the sample answer. The result holds 29.3%, the situation 18.0% and the task 15.8%.1
Step 4: Result gives outcomes and what you learned
The result is what happened because of your actions, plus what you took from it. Indeed (accessed 2026-10-26) advises focusing on two or three main results and saying what you learned. The Cincinnati newspaper example reports re-engaging 15 former advertisers and winning five new contracts, which raised new advertisers by 20% (University of Cincinnati, accessed 2026-10-26).
Input: what changed after your action. Output: an outcome the team shared, a measure if one exists, and one lesson. The same page says that when the outcome was not positive you can focus on your strengths and resilience. The sample result shows a shipping date moved from four days late to one, plus a changed habit, in 39 words.1
You now have the four parts. The figure shows them in order.
Step-by-step description
- Name the team and the context.
- State your goal and role.
- Say what you did, using I.
- Give outcomes and a lesson.
- The situation names the team.
- The task states your goal and role.
- The action uses I for your own steps.
- The result gives outcomes and what you learned.
Knowing it is half the job. Saying it is the other half.
Interview Clozo is an AI interview copilot for real interview rounds: it hears the question and puts a strong answer on your screen, and you say it in your own words. See the features or how it works.
Start Free Trial →The Staff-level answer
Tell me about a time you worked well on a team.
Last spring our team of five had three weeks to ship a customer reporting page, and two weeks in we were four days behind. My job was to own the data export piece and to get the team back on schedule without cutting the tests. I listed every open task with its owner and saw that two of us were blocked on the same unfinished interface.
I wrote a draft of that interface that evening, asked the teammate who knew the consuming side to review it, and we agreed it in one thirty-minute call. We shipped one day late, not four, with every test intact. The review process I used became our habit for any shared interface, and I learned to raise a blocker on day one of a delay, not day ten.
This is an illustrative example, not a real person's story. It has 133 words, which is about 53 to 61 seconds at an assumed pace of 150 to 130 words per minute.1 As an editorial guide, 60 seconds at 130 words per minute is 130 words and 90 seconds at 150 words per minute is 225 words; no primary source sets an ideal length.1 The spoken structure: set the scene with the team, state your job, give two or three things you did, then close with the outcome and the lesson.
What makes it Staff-level: it names a blocker, shows one personal action that unblocked other people, and ends with a change that stayed in how the team works.
Compare a weak version of the same story, which has 27 words and three uses of "we" and no use of "I":1 (wrong) "Our team was behind on a project. We talked about it and we worked together and we finished it. It went well and the team was happy." The strong answer has four "I" and three "we", so the team is present and so are you.1
Text description of the diagram
- The action holds 36.8% of the words of the sample answer.
- The result holds 29.3%, the situation 18.0% and the task 15.8%.
The rubric
| Dimension | Weak answer | Strong answer | Staff answer |
|---|---|---|---|
| Structure | Wanders; the listener cannot tell where the story starts or ends. | Four parts in order, with the action longest. | Same, plus one line on why this story fits the question. |
| Your contribution | Says "we" throughout, with no personal step. | Names two or three things you did, using "I". | Shows what you did to unblock or lift other people. |
| Teamwork evidence | A friendly group with no obstacle. | A real obstacle and how you worked with others' roles. | Shows how you changed the way the team works. |
| Result | Vague: "it went well". | A concrete outcome and what you learned. | Outcome, a measure where one exists, and a change you kept. |
| Follow-up readiness | Cannot add detail when asked. | Can expand any step on request. | Has a second story ready for a different skill. |
This rubric is our advice on what a strong answer shows. It is not any company's scoring sheet.
Three variants of this question
Tell me about a time you helped a teammate who was struggling
Set up the teammate's problem neutrally in the situation, then use the action for what you did: noticing, offering help, sharing a method or handing over a task. Avoid blaming the teammate, and close with what changed for them and the team.
Tell me about a time you were not the leader
State your role as a member in the task step, then show the support you gave in the action: unblocking someone, covering a gap or raising a risk. The influence without authority page covers the case where you had to move people without a title.
Tell me about a team project that did not go well
Keep the situation and task honest, then let the result carry what changed. The Cincinnati page says that when the outcome was not positive you can still focus on your strengths and resilience (University of Cincinnati, accessed 2026-10-26).
Common mistakes
- (wrong) "We decided, we built it and we shipped it." The listener cannot find you. (right) "I proposed the split, I built the export and we shipped it together."
- (wrong) Spending most of the time on the situation. The background is not what is being judged. (right) Give the context in a sentence or two and spend the time on the action.
- (wrong) Taking all the credit: "I fixed the whole project." (right) Say what you did and whom you worked with: "I wrote the draft and asked a teammate to review it."
- (wrong) "It turned out fine." (right) Give two or three outcomes and one lesson, as Indeed advises.
- (wrong) Reciting a memorized script word for word. (right) Prepare the story, rehearse it aloud for clarity and be ready to expand any part when asked.
Follow-up questions
How long should a teamwork STAR answer be?
No primary source sets an ideal length. As an editorial guide, aim for about a minute to a minute and a half spoken, then stop and let the interviewer ask for more. The common interview questions page shows the same pacing on other questions.
Can I use a school or volunteering story?
Yes. The University of Cincinnati page says to recall recent experiences that show skills such as teamwork. A school, internship or volunteering story works too, as long as your own action is clear.
Should I mention a mistake I made in the team?
Yes, if it is real, small enough to recover from and told without blaming a teammate. Say it in one sentence inside the action or result, then say what you changed afterwards.
How do I say "I" without sounding like I take all the credit?
Name the team once in the situation, then use verbs that involve others: "I asked", "I handed over", "we agreed". Your contribution stays visible and so do your teammates.
Which other questions can the same story answer?
A good teamwork story often fits questions on decision making and on Amazon's Leadership Principles, so prepare a few stories and change the emphasis. A story where you learned from a flaw can also feed the greatest weakness question.
- Teamwork STAR is one real story in four parts: situation, task, action, result.
- Name the team once in the situation, then use "I" in the action.
- Give the action the most detail; it shows your fitness for the role.
- Close with two or three outcomes and one lesson, even if the result was mixed.
- Rehearse the story for clarity; do not memorize a script.
Sources
- STAR Method for Behavioral Interviews — University of Cincinnati Career & Co-op Support (accessed 2026-10-26), 26 Oct 2026
- Using the STAR method to ace interviews — ORISE, Oak Ridge Institute for Science and Education, a US Department of Energy institute (undated page, accessed 2026-10-26), 26 Oct 2026
- Initial comparisons of patterned behavior description interviews versus unstructured interviews — Journal of Applied Psychology 67(5) (Janz, 1982), 1 Oct 1982
- How To Use the STAR Interview Response Technique — Indeed Career Guide (date of the fetched copy; accessed 2026-10-26), 10 Sep 2026
- Situation, task, action, result — Wikipedia (accessed 2026-10-26), 26 Oct 2026
