Interview Recipes
Menu

Teamwork & collaboration

How a candidate works with people they don't control: sharing information and credit, addressing friction directly, and putting the team's result ahead of their own slice of it.

Teamwork questions have a rehearsal problem: every candidate has a we-pulled-together story ready, and it rarely tells you anything. What you actually need to know is how someone behaves when collaboration gets expensive: a teammate who isn't delivering, a decision that went against them, credit that landed on the wrong person.

That is where these teamwork interview questions live. They ask candidates to walk through friction they handled as a peer, without authority to lean on: disagreements settled directly, conflict between others that was starting to hurt the work, real help extracted from a team with its own priorities. Several deliberately ask for failure, like the team effort that collapsed or the working relationship that never worked, because the honest version of those stories shows how much of the team's result a candidate treats as theirs.

Use two or three in an interview, ask every candidate the same ones, and score each answer against the anchors on the card before you compare candidates.

Interview for it when

Most of what they deliver runs through people they don't manage.

Where this competency comes from

Teamwork is not our invention: it shows up, under different names, in every major validated competency framework. Our ten-competency taxonomy keeps what at least three of the four agree on. The full reasoning is in why structured interviews work.

The Great Eight (Bartram, 2005)
Supporting & Co-operating
UK Civil Service Success Profiles
Working Together
US OPM general competencies
Teamwork, Interpersonal Skills
Google’s four attributes
Googleyness

In the O*NET content model it maps to the work activities Establishing and Maintaining Interpersonal Relationships · Resolving Conflicts and Negotiating with Others · Coordinating the Work and Activities of Others and the work styles Cooperation.

O*NET mapping adapted from the O*NET content model (U.S. Department of Labor), used under CC BY 4.0.

The questions

All 12 cards in full: the question, why it works, the follow-up probes, and the anchors to score against. Still choosing competencies? Plan the interview first.

teamwork

Tell me about a real disagreement with a co-worker that the two of you had to settle yourselves. How did you open that conversation?

Why this works

The common failure modes are avoidance and escalation — routing around the person or over their head. Asking how they opened the conversation gets past "we talked it out" to whether the candidate can actually start a hard conversation with someone they'll sit next to tomorrow.

Follow-up probes

  • What was the disagreement really about, underneath the surface issue?
  • What did the other person say that you had to admit was fair?
  • How did the two of you work together afterward?

What good looks like

They went to the person before going anywhere else, can state the other side's position fairly, landed on something both could live with, and the working relationship survived — or improved.

Red flags

The conflict traveled through the manager or the group chat before it ever reached the person, the co-worker is a cartoon villain, "resolved" means the candidate won, or the relationship quietly died afterward.

Card page · add to recipe

teamwork

Tell me about two teammates whose conflict was starting to hurt the work. What did you do about it as their peer?

Why this works

Stepping into other people's conflict as a peer is optional, which is exactly what makes it signal. The question shows whether the candidate treats team friction as their problem too, and whether they can help without authority and without taking a side.

Follow-up probes

  • How did each of them describe the problem to you?
  • Did either of them resent you getting involved?
  • What changed for the work itself, not just the mood?

What good looks like

They heard both sides and can restate each fairly, intervened on the work impact rather than the personalities, and got the two talking to each other again instead of through an intermediary.

Red flags

They reported it to the manager and considered the job done, picked a side and helped it win, the fix was avoidance dressed up as harmony, or they claim teams they're on simply don't have conflict.

Card page · add to recipe

teamwork

Tell me about a working relationship that never really worked, even though you tried. What did you try, and where did it end up?

Why this works

Everyone has one of these; claiming otherwise is itself the answer. Asking for the unfixed case lowers the incentive to perform and separates candidates who kept the work professional through a bad fit from those who wrote the person off — including how honestly they weigh their own share of it.

Follow-up probes

  • What did you try that you genuinely expected to work?
  • What was your contribution to the standoff?
  • How did you keep the work moving anyway?

What good looks like

Several genuinely different attempts rather than one gesture, their own part in it named without prompting, the work insulated from the relationship, and a realistic account of where things settled.

Red flags

The other person carries the entire story, one token attempt was followed by permanent avoidance, the work visibly suffered and that's treated as inevitable, or every relationship they've ever had was apparently great.

Card page · add to recipe

teamwork

Tell me about a moment with a colleague you'd handle differently today. What did you do then, and what did the repair take?

Why this works

The rehearsed conflict story casts the candidate as the reasonable one; this asks them to be the problem. What they did after the moment — the walk back, the apology, the changed habit — shows whether they can own an interpersonal miss without a script for it.

Follow-up probes

  • When did you realize you'd gotten it wrong?
  • What did you actually say when you went back to them?
  • What does that colleague get from you differently now?

What good looks like

A real misstep rather than a humble-brag, a repair they initiated promptly and in person, the colleague's side of it described credibly, and a specific behavior that has changed since.

Red flags

The "mistake" was being too honest or caring too much, the repair was skipped because time heals, the realization only arrived when someone complained, or the story ends before the repair starts.

Card page · add to recipe

teamwork

Tell me about a teammate who wasn't delivering their share of the work. What did you try before anyone with authority got involved?

Why this works

The easy moves are silent resentment, quiet covering, and instant escalation — none of which fix anything. The question locates the candidate on that spectrum: whether they raised it with the person directly, and whether the team's result stayed protected while it played out.

Follow-up probes

  • How did you first raise it with them directly?
  • How did you decide what was yours to fix and what wasn't?
  • What happened to the team's commitments while this played out?
  • At what point would you have escalated, and to whom?

What good looks like

They went to the teammate first, plainly and without an audience, treated it as a work problem rather than a character verdict, kept the team's commitments covered in the meantime, and escalated with facts rather than grievances once direct attempts failed.

Red flags

They covered for the person silently to avoid "making it a thing", the first move was the manager, the account is about fairness to themselves rather than the team's result, or the teammate is dismissed as lazy with no attempt ever made.

Card page · add to recipe

teamwork

Tell me about a team decision that went against the position you'd argued for. What did you do once it was made?

Why this works

Anyone can commit to a plan they liked; losing the argument is where team-first behavior gets tested. The question shows whether the candidate can execute a decision at full effort without relitigating it — and whether their dissent stayed honest and on the record rather than moving to the hallway.

Follow-up probes

  • How visible was your support once the work started?
  • What would teammates say your effort looked like from outside?
  • Did the decision turn out right or wrong — and what happened then?

What good looks like

Dissent argued fully before the decision and then a clean switch to executing, support visible enough that a newcomer couldn't tell they'd opposed it, and the outcome revisited honestly — including when they turned out to be wrong.

Red flags

Agreement in the meeting and campaigning after it, effort quietly dialed down so the failure would prove them right, an "I told them so" delivered with relish, or going silent and calling it commitment.

Card page · add to recipe

teamwork

Tell me about a team effort that failed. Walk me through your own part in the failure.

Why this works

Failure stories reveal how a candidate divides up a shared outcome: weak answers audit everyone else's contribution and exempt their own. What they did as it sank — raise the alarm, double down on helping, or watch — separates people who own a team result from passengers.

Follow-up probes

  • When did you first suspect it was going wrong, and what did you do?
  • What did you personally do that you'd now do differently?
  • What did the team do with the wreckage afterward?

What good looks like

A concrete personal contribution to the failure named unprompted, evidence they raised the alarm or leaned in rather than spectated, and something specific they carried into the next team effort.

Red flags

The failure is fully explained by other people and circumstances, their own role shrinks to bystander, nothing was said at the time because "it wasn't my call", or the lesson is a platitude.

Card page · add to recipe

teamwork

Tell me about needing real work from a team that didn't report to you and had its own priorities. How did you get it?

Why this works

Most working life happens across teams that owe you nothing. The question surfaces the candidate's actual currency — relationships built before they were needed, asks shaped to the other team's interests, or authority borrowed from above — and whether the cooperation outlasted one favor.

Follow-up probes

  • What did your request look like from their side?
  • What did you change to make helping you easy?
  • What did you do when they first said no?
  • Would that team help you again today?

What good looks like

The other team's constraints understood and spoken to, the ask reshaped to fit their world, a no answered with a better approach rather than a louder one, and a relationship left healthier than before the request.

Red flags

Escalation as the opening move, cooperation extracted once with the bridge burned behind it, the other team cast as an obstacle throughout, or a manager did the actual getting.

Card page · add to recipe

teamwork

Tell me about being blocked on something only one unresponsive colleague could give you. Walk me through everything you tried.

Why this works

A stalled dependency is a small test with an honest reading: some candidates send the same email three times and file the missed deadline under someone else's name. "Everything you tried" invites the full sequence, showing whether they treat a colleague's silence as an excuse or as a problem to work.

Follow-up probes

  • What did you try after the second nudge failed?
  • What turned out to be competing for their attention?
  • At what point did you involve anyone else, and how?
  • What happened to your deadline in the meantime?

What good looks like

An escalating sequence of channels and framings rather than repeats, the ask made smaller and easier to answer, the block flagged early to whoever owned the deadline, and no bridge burned once it resolved.

Red flags

One email and a shrug with the outcome filed as the colleague's fault, or the opposite — an immediate cc to their manager; the colleague described with contempt; the ask never once adapted.

Card page · add to recipe

teamworksenior

Walk me through the hardest negotiation you've led with another team or an outside partner. What did you give up to get the deal?

Why this works

Asking what they conceded is the quickest way to tell a negotiator from a steamroller — a deal where the other side got nothing usually wasn't a negotiation. It also shows whether they mapped the other side's interests well enough to trade things they held cheaply for things they valued.

Follow-up probes

  • What did the other side actually need, versus what they asked for?
  • Which concession was hardest, and why that one?
  • How did the agreement hold up afterward?

What good looks like

The other side's interests mapped before positions hardened, concessions traded deliberately rather than surrendered under pressure, a walk-away point they can name, and an agreement both sides honored afterward.

Red flags

Victory described as the other side folding, concessions they can't name or reframe as generosity, no walk-away point ever defined, or a deal that needed renegotiating within weeks.

Card page · add to recipe

teamwork

Tell me about working closely with someone whose working style collided with yours. What did you change on your side to make it work?

Why this works

The framing blocks the comfortable exit of describing how difficult the other person was — the question is what the candidate adjusted. It separates people who can flex how they work from people who wait, politely, for everyone else to convert.

Follow-up probes

  • What specifically clashed — pace, planning, level of detail?
  • What did adapting cost you?
  • What did you refuse to change, and why?
  • What did you end up borrowing from their way of working?

What good looks like

The difference described as work habits rather than character flaws, concrete adjustments made on their own side, a line they held with a stated reason, and something genuinely borrowed from the other style.

Red flags

The other style is treated as simply wrong, all the adapting was expected from the other person, "we're just different" with no adjustment ever made, or the difference drifts from working style into personal territory.

Card page · add to recipe

teamworkjuniorsituational

In a team meeting, your manager singles you out for praise on a result that mostly came from a quieter teammate. Everyone's looking at you — what do you do?

Why this works

There's no free move: absorbing the praise is theft by silence, and an elaborate public correction can embarrass everyone including the teammate. Candidates without much work history still produce a scoreable answer about who they think results belong to when saying so costs them something.

Follow-up probes

  • What do you actually say, right there in the meeting?
  • Does anything change if the teammate isn't in the room?
  • What do you do after the meeting ends?

What good looks like

Credit redirected promptly and specifically — naming what the teammate did — without theatrical self-deprecation, plus a check afterward that the correction registered where it matters, and no fuss made about having done it.

Red flags

A vague "it was a team effort" that keeps the spotlight where it landed, a correction that happens only in private later if at all, or an answer optimized for how the candidate looks rather than for the teammate getting their due.

Card page · add to recipe

Often assessed alongside

A good interview covers four to six competencies, chosen for what the job turns on. Roles that need teamwork usually also lean on:

Hiring for a role that turns on teamwork?

Plan the interview and three short steps will work out which competencies your role needs, no account required. Or subscribe and get new vetted questions and interview guides as we publish them.