Interview questions for teamwork, with a scoring rubric
On this page
- What "teamwork" actually means, separated from being agreeable
- Ten questions, with strong answers, red flags and a follow-up
- A 1-4 rubric for teamwork
- Rehearsed versus real: how to tell the difference
- Which roles this matters most for
- Mistakes to avoid when scoring this
- A checklist before this interview
- Questions people ask
Interview questions for teamwork work when they ask what the candidate specifically did inside a group, not how they feel about working with others. Below is a bank of ten questions built that way, each with what a strong answer sounds like, a red flag, and a follow-up probe, plus a rubric, a way to catch a rehearsed team story, and the roles where this competency matters most.
This differs from how to assess soft skills in interviews, which covers the general method, and from behavioral interview questions with a scoring rubric, whose "collaboration and conflict" section covers four different questions focused on disagreement. This page is about coordinating, sharing credit and carrying a fair share of the work, with none of the same questions.
What "teamwork" actually means, separated from being agreeable
A candidate can be pleasant in every meeting and still be a poor teammate: taking credit alone, leaving gaps for others to cover, or withholding information that would have helped a colleague. Score three specific behaviors instead of a general vibe:
- Coordinating. Making handoffs work, closing gaps between people, and keeping others informed without being asked.
- Sharing credit and information. Naming who else contributed, and passing along what they learn instead of holding it as an advantage.
- Carrying a fair share. Picking up slack when it is genuinely needed, and saying something when someone else consistently does not.
Ten questions, with strong answers, red flags and a follow-up
| Question | What a strong answer sounds like | Red flags | Follow-up probe |
|---|---|---|---|
| Tell me about a project where your part depended on someone else finishing theirs first. | Describes checking in proactively before the deadline, not just waiting, and what they did if the handoff was late. | The story is entirely about waiting passively, or blaming the other person with no mention of following up. | "At what point did you check in, and what did you say?" |
| Describe a time you knew something that would have helped a teammate, and you told them before they asked. | A specific piece of information, why it mattered to the teammate, and that they shared it unprompted. | Cannot think of an example, or the information was shared only after being asked directly. | "What would have happened if you had kept that to yourself?" |
| Tell me about a project that went well because of the team, not because of any one person. | Names specific contributions from at least two other people, in addition to their own, without minimizing either. | Every version of the story circles back to the candidate's own role as the deciding factor. | "What's one thing a teammate did that you couldn't have done yourself?" |
| Describe a time a teammate was struggling to keep up, and you noticed before a manager did. | Describes noticing specific signs, addressing it directly and kindly with the person first, and what actually changed. | Went straight to the manager without speaking to the person, or ignored it because "not my job." | "What did you say to them directly, and how did they respond?" |
| Tell me about a time you picked up extra work because a teammate was out or overloaded. | A specific instance, what they picked up, and whether they said anything if it became a pattern rather than a one-off. | No example, or describes doing this constantly with visible resentment and no attempt to raise it. | "Did this happen more than once with the same person? What did you do differently the second time?" |
| Describe a time you had to hand off unfinished work to someone else. | Describes what they did to make the handoff usable: documentation, a walkthrough, flagging the risky parts. | The handoff is described only from their side, with no mention of what the receiving person actually needed. | "What's the one thing you made sure to tell them that wasn't written down anywhere?" |
| Tell me about a time credit for a result went to the wrong person, or wasn't shared fairly. | Describes what they did about it directly and constructively, whether that meant correcting it in the moment or letting a small instance go without resentment. | Long, detailed grievance with no resolution, or describes taking credit from someone else as the "right" outcome. | "Looking back, is there anything you'd do differently in how you raised it?" |
| Describe joining a team partway through a project that already had its own way of working. | Describes learning the existing workflow before pushing changes, and one specific way they adjusted to fit in. | Immediately changed the team's process to match their own preference without understanding why it existed. | "What was one thing the team did that you disagreed with at first but came to understand?" |
| Tell me about a decision your team made that you didn't fully agree with, but went along with. | Raised the disagreement through the normal channel, then supported the decision fully once it was made, without undermining it afterward. | Complied outwardly but describes quietly working around the decision or badmouthing it to others. | "How did you make sure your reservations didn't show up in how you executed it?" |
| Describe a time you asked a team for help on something you could have muscled through alone. | A specific reason for asking rather than pushing through, what they asked for exactly, and how it changed the outcome. | Cannot recall ever asking, framing it as a strength ("I always figure it out myself"). | "What made you decide to ask that time instead of just doing it yourself?" |
A 1-4 rubric for teamwork
| Dimension | 1 — Weak | 2 — Developing | 3 — Solid | 4 — Strong |
|---|---|---|---|---|
| Coordinating across a handoff | No example, or waits passively for others without following up | Follows up but only after a deadline is already missed | Checks in proactively before a handoff is due | Same, plus builds in a buffer or documentation so a late handoff doesn't stall others |
| Sharing credit and information | Every story centers on their own role; no unprompted information-sharing example | Shares information when asked; gives credit only when prompted | Names specific teammates' contributions unprompted; shares useful information proactively | Same, plus visibly makes others look good, not just accurate |
| Carrying a fair share of the load | No example of covering for someone, or resentful, unaddressed over-carrying | Covers occasionally but never raises it if it becomes a pattern | Covers when genuinely needed and raises a repeated pattern constructively | Same, plus distinguishes a one-off need from a pattern before it builds resentment |
| Committing to a decision after disagreeing | Undermines or works around decisions they disagreed with | Complies outwardly but the disagreement leaks into execution | Raises disagreement through the normal channel, then executes fully | Same, plus actively supports the decision to others rather than staying neutral |
Rehearsed versus real: how to tell the difference
"I'm a great team player" is one of the safest things a candidate can say, which is exactly why it tells you nothing. Three checks separate a rehearsed team story from a real one:
- Count the other names. A real team story usually has at least one other specific person in it, with a specific thing that person did. A rehearsed story keeps every other person vague ("the team," "everyone") because the candidate was never actually paying attention to what anyone else contributed.
- Ask what would not have happened without them, specifically. A genuine contributor can name one concrete thing that depended on them. A candidate borrowing a team's success as their own answer tends to restate the overall result rather than their specific piece of it.
- Ask about the version where it didn't go well. Ask for a time coordinating with a team went badly, not just well. A rehearsed teamwork answer usually has no failure mode ready; a candidate with real experience can describe a specific breakdown and what they'd do differently.
Which roles this matters most for
| Role type | What to weight most |
|---|---|
| Cross-functional roles (product, program management, operations) | Coordinating handoffs between groups that don't report to the same manager |
| Engineering and other build-in-pairs work | Sharing information and credit, and picking up when a teammate is blocked |
| Sales teams with shared quota or account handoffs | Fair sharing of leads, credit and coverage during absences |
| Healthcare and shift-based work | Reliable handoffs where a gap directly affects patient or customer safety |
| Individual-contributor roles with little day-to-day collaboration | Weight this competency lower; ask instead about occasional cross-team dependencies |
Mistakes to avoid when scoring this
| Mistake | What it costs you |
|---|---|
| Scoring likability in the interview as teamwork | You hire someone pleasant to interview, not necessarily someone reliable to depend on |
| Accepting "we" without ever asking what the candidate specifically did | You cannot tell a genuine contributor from someone who rode along |
| Treating a preference for solo work as a red flag on its own | You filter out strong individual contributors who collaborate fine when needed |
| Not asking about a team failure, only successes | You miss how they behave when coordination actually breaks down |
A checklist before this interview
- At least one question asks for a specific handoff, not a general team success story.
- You are ready to press on "we" until you hear what the candidate specifically did.
- At least one question asks about a team situation that went badly, not only well.
- You have decided whether coordination, credit-sharing, or fair workload matters most for this role.
- You are not scoring a preference for independent work as a teamwork weakness by default.
Interview Signal ticks off each must-ask question as it gets covered on the call and keeps the exact quote behind every score, so a teamwork rating in the debrief is backed by what the candidate said about a specific handoff, not a general impression of how agreeable they seemed.
Questions people ask
How do I tell if a candidate actually contributed, or is describing their team's work as their own?
Ask what they specifically did, not what 'we' did, and ask what would not have happened without them. A candidate who was genuinely central can usually name one thing the team would have missed without their specific contribution.
Is a candidate who prefers working alone automatically weak on teamwork?
No. Preference for focused solo work is a work style, not a teamwork deficit. Score whether they can work well with others when the job requires it, not whether they would choose to if given a free option.
Should I ask about a team conflict here, or is that a separate competency?
Keep conflict handling separate. This bank covers coordinating, sharing credit and information, and carrying a fair share of the load; a dedicated set of questions on disagreement and conflict gives you a cleaner, separately scoreable signal.
What if the candidate has mostly worked on small teams with no formal structure?
Score the behavior, not the team size. A two-person team still has handoffs, shared credit and uneven workload moments; ask for those specifically rather than assuming a small team means no real teamwork evidence exists.