Interview Questions to Ask Candidates About Teamwork
Behavioral questions about how a candidate works alongside other people: disagreements and how they ended, relying on someone who was not delivering, giving and taking feedback from peers, handing work over, and the kind of team they do badly in.
The questions
Open any question for the note
Tell me about a team you enjoyed being part of. What made it work?
Why ask it
An easy opener that tells you what conditions they need. Someone who names clear ownership and honest reviews wants something different from someone who names a friendly atmosphere.
Tell me about a time you disagreed with a teammate about how to do something. How did it end?
Why ask it
Ask how it ended, not how they handled it, and you get an outcome instead of a technique. Candidates who report always being right in these stories are describing something other than collaboration.
Tell me about a team decision you disagreed with. What did you do after it was made?
Why ask it
Separates disagreement from obstruction. The answer you want involves arguing the case, losing, then supporting the decision. Quiet non-compliance afterwards is the pattern to listen for.
Describe a time you depended on someone who was not delivering. What did you do?
Why ask it
Listen for whether they spoke to the person before escalating, and whether they took on the work silently. Doing it all themselves feels heroic and usually hides the problem until it is too big to fix.
When did you last ask a colleague for help, and what did you ask for?
Why ask it
Candidates who cannot recall asking for help either do not need it, which is rare, or find it costly to ask, which will slow their first year in any new team.
When have you changed your mind because of something a colleague said?
Why ask it
A specific example means they actually listen. Generic agreement that other perspectives are valuable, with nothing behind it, is the common non-answer here.
Tell me about feedback you gave a peer that was difficult to give.
Why ask it
Peer feedback has no authority behind it, which makes it harder than managing. Ask what words they used and whether the working relationship survived.
Tell me about feedback you received from a peer. What did you do with it?
Why ask it
The useful detail is whether anything changed. Candidates who only recall praise from colleagues have either not been given much or have not taken it in.
Describe a time you handed work over to someone else. How did you prepare them?
Why ask it
Handovers are where teams lose weeks. Someone who mentions writing things down, walking the person through it, and staying reachable afterwards has been on the wrong end of a bad one.
Tell me about working with someone whose working style was very different from yours.
Why ask it
Watch whether they describe adapting or waiting for the other person to change. Answers that reduce the difference to a personality flaw in the colleague are worth probing.
When have you stepped back and let someone else lead?
Why ask it
Shows whether they can be a contributor as well as a driver. Ask what they did while not leading, since useful support is more specific than simply staying out of the way.
When have you picked up something that was drifting without being asked?
Why ask it
The counterweight to the previous question. You are looking for someone who can read when a gap needs filling, and who told the rest of the team they were filling it.
Tell me about a time credit for shared work went to the wrong person.
Why ask it
The answer shows how they raise something uncomfortable that concerns their own standing. Both silence and public confrontation are common; a direct private conversation is the answer that scales.
How do you make sure quieter people in a meeting get heard?
Why ask it
Practical answers exist: asking someone directly, collecting input before the meeting, following up afterwards. Answers about creating a safe space with no mechanism behind it are aspiration, not practice.
Tell me about a team under real time pressure. What did you do about coordination?
Why ask it
Under pressure most teams stop communicating. Candidates who describe a daily check-in, a shared list, or splitting work explicitly have learned this the hard way.
Describe a conflict between two other people that affected your work.
Why ask it
Tests judgment in a situation where they had no authority. Listen for whether they stayed out of it, took a side, or found a way to keep the work moving around the dispute.
What do you do when you can see a project going wrong and it is not your call?
Why ask it
You want someone who raises it once, clearly, to the person who can act, and then keeps working. Saying nothing and being able to say afterwards that they knew is the pattern to avoid hiring.
Tell me about working across a time zone, language or site difference.
Why ask it
Distributed work rewards written clarity and punishes casual assumption. Concrete answers mention overlap hours, writing decisions down, and checking understanding rather than tone.
What have you done that made a team run better after you left it?
Why ask it
Reveals whether they build anything durable: a template, a rota, a document, a habit. Many strong individual contributors have nothing to point to here, which is useful to know.
What kind of team do you not do well in?
Why ask it
The most informative question in the set, and the one candidates least expect. A specific answer, such as struggling without clear ownership, helps you judge fit honestly. "I get on with everyone" ends the conversation early.
Assessing teamwork in an interview
Practical guidance for the conversation itself
Ask for outcomes, not intentions
- Every question should end in what happened, not what they believe about collaboration.
- If a story has no friction in it, ask for a different one. Frictionless examples tell you nothing about behaviour under strain.
- Ask who else was involved and what that person would say about it. Candidates recalibrate quickly.
- Ask about the last time rather than a typical time. Recent examples are harder to polish.
- Note whether the candidate ever names their own contribution to a conflict, not just their response to someone else's.
Follow-ups that do the real work
- 1"What did you actually say to them?" Turns a summary into observable behaviour.
- 2"What did they say back?" Reveals whether the conversation happened as described.
- 3"How was the relationship afterwards?" Distinguishes resolving a conflict from winning one.
- 4"What would you do differently?" Shows whether they have reflected or simply moved on.
- 5"Who else knew about it at the time?" Tests whether problems get surfaced or contained.
Patterns worth noting
- Every difficult colleague in every story is unreasonable, and the candidate is never part of the problem.
- Conflict is resolved only by escalating to a manager, with no attempt at a direct conversation first.
- The candidate absorbed a colleague's unfinished work repeatedly and told nobody.
- Strong stories about leading, none about contributing while someone else led.
- Fluent language about psychological safety and inclusion with no concrete example attached to it.
Practical setup
Pick six, not twenty
Six questions with real follow-ups tell you more than twenty asked once. Choose the ones matching your team's actual friction points, such as handovers, remote work, or peer review.
Involve a future teammate
Have someone who will work alongside the hire ask two of these questions. They hear things a hiring manager does not, and they will have to live with the decision.
Score each question separately
Rate the answers as you go rather than forming one overall impression. Warmth in an interview is easy to mistake for collaboration, and the two come apart in practice.
Check with a reference
Ask a former colleague, not only a former manager, what the candidate was like to share a deadline with. That is the question managers often cannot answer.