Teamwork interview questions: 15 to ask and what to listen for

Teamwork interview questions ask candidates how they've worked with others, so you can judge collaboration from real examples.

Every hiring manager or client wants a team player, but that means different things on a nursing unit and a sales floor. Good interview questions about teamwork turn that vague request into evidence you can compare across candidates.

Teamwork interview questions by theme

The 15 questions below fall into five themes, so you can pick the ones your role needs. Behavioral questions ask what a candidate did, starting with "Tell me about a time." Situational questions ask what they would do, starting with "What would you do if."

If the role manages people, pair these with leadership interview questions that test how the candidate directs a team.

Collaboration on shared goals

These show whether the candidate sees their own work as part of a bigger team result.

1. Tell me about a time your team hit a goal none of you could reach alone.

2. Describe a project where your work depended on someone else's, and how you kept it moving.

3. What would you do if your team agreed on a goal but not on who owns each task?

Handling disagreement

These show how a candidate pushes back on an idea without damaging the working relationship.

4. Tell me about a time you disagreed with a teammate about how to do the work.

5. Describe a team decision you didn't agree with and how you handled it afterward.

6. What would you do if a coworker kept missing deadlines that held up your work?

For roles with frequent friction, such as customer support, add a few conflict resolution interview questions on this theme.

Supporting teammates

These test whether a candidate notices when others need help and then acts on it.

7. Tell me about a time you helped a struggling teammate when it wasn't your job.

8. Describe how you brought a new team member up to speed in your last role.

9. What would you do if a teammate was about to make a mistake that would affect a client?

Working across teams or remotely

These matter most for roles that hand work between departments, shifts, or time zones.

10. Tell me about a time you got something done with a team you didn't manage.

11. Describe how you kept a remote or hybrid team informed without meeting in person.

12. What would you do if another department kept changing its requests after your team started?

Giving and taking credit

These show whether a candidate shares wins openly and owns mistakes in front of others.

13. Tell me about a team success and what each person contributed to it.

14. Describe a team project that went wrong and which part of the problem was yours.

15. What would you do if your manager praised you for work a teammate mostly did?

What strong and weak answers sound like

A strong answer names one real situation, the candidate's role, their actions, the outcome, and who helped. A weak answer stays general or ends with someone else as the problem.

Example strong answer and what it shows

Say you ask a warehouse supervisor question 6 and hear this answer.

"Our inbound team kept finishing late, which pushed my pick crew into overtime. I asked their lead what was slowing them down and learned two scanners were broken. We shared one of ours until theirs were replaced, and both teams got back on schedule. I made sure my crew and their lead both got credit in our weekly meeting."

• Specific role: the candidate owned the pick crew and acted within that job.
• Actions: they asked a question before assuming the other team was at fault.
• Outcome: both teams got back on schedule, which gives a clear before and after.
• Credit to others: they named their own crew and the other team's lead.

Red flags in answers

The clearest red flags are answers that are all "I", blame others, or offer no real example. Say a sales rep answers the same question by saying they do their part and a slow coworker is their manager's problem. That answer has no situation, action, or outcome, and it pushes the problem onto someone else.

• All "I": the candidate claims team results and never names a teammate.
• Blame: every story ends with a coworker or another department at fault.
• No example: the candidate describes what they "always" do instead of one real event.
• Vague outcome: the story stops before anyone learns whether the work succeeded.

Follow-up probes to ask every candidate

Use the same short set of follow-up probes with every candidate so the extra detail is fair to compare. OPM's structured interview guidance describes high-structure interviews as asking all applicants the same lead and follow-up questions, scored against benchmarks of proficiency.

• Role: ask what their part was and what other people owned.
• Action: ask what they did first and why they started there.
• Outcome: ask how it turned out and how they knew it worked.
• Reflection: ask what they would change if it happened again.

Write these probes into your structured interview guide so every interviewer uses the same wording.

How to score answers

Score each answer on a 1 to 5 scale with written anchors, and use the same questions for every candidate. Start from the competencies the job needs, which come from job analysis, a review of what the work requires day to day.

OPM's research summary notes that questions built on job competencies show high validity and strong agreement between raters. For a nurse role, that might mean weighting handoffs between shifts. For a remote developer role, it might mean cross-team work and written updates.

Agree on which themes count most with the hiring manager or client before the first interview.

Scoring guide

Use these anchors as a starting point, then rewrite them in the language of the role.

• Score 1: the candidate gives no real example or blames others for the outcome.
• Score 2: the example is real but vague about their own role and actions.
• Score 3: role and actions are clear, but the outcome is thin or others get no credit.
• Score 4: role, actions, and outcome are clear, and teammates get credit.
• Score 5: everything in score 4 is there, plus reflection on what they'd change.

Have each interviewer score alone, right after the interview, before reading anyone else's notes. A shared interview scorecard keeps the anchors in front of everyone and makes scores easy to compare.

Check scores before the team compares notes

Check that every interviewer used the same anchors before anyone averages or discusses scores. If two interviewers gave the same answer a 2 and a 5, review the anchors together before settling on a score. A gap that wide points to unclear anchors, and fixing them makes your next round of teamwork interview questions more useful.

Build your question set before the next interview

Pick the themes that matter most for the role, choose one question from each, and write your anchors first. Then share your teamwork interview questions, probes, and scoring guide with every interviewer so everyone asks and scores the same way.