Team player interview questions: 30 questions that can be failed, what a strong answer contains, and how to score them consistently

"Are you a team player?" No candidate has ever said no. The question survives because it feels relevant and costs nothing to ask, and it tells the interviewer precisely as much as it costs. Team player interview questions are worth getting right, because collaboration is one of the few things a person specification asks for that almost never gets assessed, and one of the few weaknesses that shows up in the first month rather than the first year.

This article gives 30 original questions in six groups, each with what a strong answer contains and the weak answer to watch for; explains how to define teamwork for the job before you interview; shows how to score the answers consistently; sets out the fairness rules; and warns about what "team player" too often means.

What you ask at interview should be what you review afterwards. See how New Dynamics performance reviews keep the behaviours you hired for in the same place as goals, feedback and development.

First, define what teamwork means in this job

The Skills Builder Universal Framework defines teamwork as “working cooperatively with others to achieve a shared goal”, and its early steps are practical: working with others when appropriate, keeping to time reliably, taking responsibility for completing tasks, and helping others. Later steps move towards improving how the team itself works.

That gives a better starting point than the word "team player", because it is about observable behaviour. Before you write questions, answer four things about the job:

1. Who does this person depend on, and who depends on them? A nurse on a ward, a developer in a squad and a field engineer working alone all need different collaboration.
2. What does a handover look like here? Most teamwork failures are handover failures.
3. Where will they have to disagree? With peers, with a manager, with a customer, and how is that expected to go.
4. What would a difficult colleague cost us? If the answer is "not much", stop screening for it and screen for something that matters.

30 team player interview questions

Ask each candidate the same questions. Follow every answer with the same two probes: "what exactly did you do?" and "what happened next?". The value is in the detail.

Dependability

1. Tell me about a commitment you made to a colleague that became difficult to keep. What did you do? Strong: told the person early, renegotiated, delivered the revised promise. Weak: the deadline moved and nobody found out until it passed.
2. Describe a time you had to hand work over mid-way. How did the next person find it? Strong: a handover the other person could use without asking; names the specifics. Weak: "I left them my notes."
3. When did you last let a team down? What did it cost and what changed afterwards? Strong: a real example, owned without excessive self-criticism, with a concrete change. Weak: a disguised strength, or nothing comes to mind.
4. How do you decide what to do first when two colleagues need you on the same day? Strong: asks about impact and deadlines, tells both what to expect. Weak: first come, first served, or whoever is loudest.
5. What does a colleague need to know about how you work in your first week with you? Strong: self-aware and specific: response times, preferred channel, when they are unreachable. Weak: generic positives.

Giving and taking help

6. Tell me about the last time you asked for help at work. What made you ask when you did? Strong: asked early, was specific about what was needed. Weak: never asks; struggled alone for a week.
7. Describe a time you helped a colleague when it slowed your own work. How did you decide? Strong: weighed the team's outcome, told their own manager. Weak: either never helps, or helps indiscriminately and misses their own commitments.
8. How do you offer help to someone who has not asked for it? Strong: offers without taking over; asks rather than assumes. Weak: rescues, or waits to be asked.
9. Who taught you the most in your last job, and what did you do to make that happen? Strong: active about learning from colleagues; names what they did. Weak: passive, or credits only formal training.
10. Tell me about a time you had to take over someone else's unfinished work. Strong: fixed it without a campaign about whose fault it was. Weak: the story is mostly about the other person's failings.

Disagreement and repair

11. Describe a disagreement with a colleague about how to do something. How did it end? Strong: the substance of the disagreement, a decision, a working relationship afterwards. Weak: "we never really disagree", or a victory story.
12. When did you last change your mind because of something a colleague said? Strong: a specific argument that landed, and what they did differently. Weak: cannot think of one.
13. Tell me about a time you disagreed with your manager's decision and had to deliver it anyway. Strong: made the case once, properly, then committed and did not undermine it. Weak: either silent compliance or quiet sabotage.
14. How do you raise a problem with someone's work? Strong: directly, privately, about the work; a real example. Weak: goes to the manager first, or says nothing.
15. Describe a working relationship that went wrong. What was your part in it? Strong: names their own contribution without self-flagellation, and what they did to repair it. Weak: the other person was impossible, full stop.

Sharing credit and information

16. Tell me about a success in your last job. Who else made it happen? Strong: names people and what each contributed, unprompted. Weak: "I" throughout a project that plainly involved others.
17. What is something you know at work that others would struggle without? How do you make sure they are not stuck? Strong: documented it, trained someone, made themselves replaceable. Weak: enjoys being the only one who knows.
18. Describe a time you shared information that made someone else's job easier. Strong: anticipated the need. Weak: shares only when asked.
19. How do you keep people informed when your work affects theirs? Strong: a routine, not a heroic effort; specifics about frequency and channel. Weak: "I keep everyone in the loop."
20. Tell me about a mistake you made that affected other people. Who did you tell, and when? Strong: told the people affected immediately, then fixed it. Weak: fixed it quietly and hoped.

Working across differences

21. Describe working closely with someone whose approach was very different from yours. Strong: adapted, found the value in the difference, names it. Weak: the difference is described as a defect.
22. Tell me about working with a team in another function, site or country. What was hard? Strong: concrete friction and how they handled it. Weak: "communication", with no example.
23. How do you work with someone you do not personally like? Strong: professional and specific; the work got done. Weak: claims to like everyone.
24. Describe a time you had to include someone who was being left out of a decision. Strong: noticed, acted, without making a scene. Weak: has never noticed.
25. What do you do when you join a team that already has its own way of doing things? Strong: learns the reasons before proposing changes; earns the right to suggest. Weak: arrives with the answers, or never suggests anything.

Improving how the team works

26. Tell me about a change you suggested to how your team worked. What happened? Strong: a real change, adopted or rejected for reasons they understood. Weak: no example, or a change imposed on others.
27. How would you know, in your first month here, whether this team is working well? Strong: names observable things: handovers, decisions, how disagreement goes, whether people ask for help. Weak: "the atmosphere".
28. Describe a meeting you improved. Strong: small, practical, specific. Weak: has never thought about it.
29. What is the most useful feedback a colleague, not a manager, has given you? Strong: remembers it, acted on it, can say what changed. Weak: only manager feedback, or none.
30. If we hired you and it did not work out with the team, what would the most likely reason be? Strong: honest self-knowledge about conditions they need. Weak: deflection, or a rehearsed weakness.

How to score the answers

The US Office of Personnel Management's guidance on structured interviews describes them as an assessment method that measures job-related competencies “by systematically inquiring about their behavior in past experiences and/or their proposed behavior in hypothetical situations”, and lists what makes them work: they can evaluate competencies that are hard to measure by other methods, “e.g., Interpersonal Skills”; “all candidates are asked the same predetermined questions in the same order”; and “all responses are evaluated using the same rating scale and standards for acceptable answers”.

In practice, four steps:

1. Choose six to eight questions from the groups that match the collaboration this job needs, and use the same set for every candidate.
2. Write down what an acceptable answer contains before the first interview, using the strong and weak notes above as a starting point, and agree it with the other interviewer.
3. Rate each answer on the same scale, immediately, with a note of the evidence rather than an impression.
4. Compare candidates question by question, not overall impression by overall impression, and record the reasons for the decision.

Keeping it fair and lawful

Acas's guidance on interviewing job applicants sets the rules that matter here: questions “must not discriminate”; “if possible, each interview should be carried out by more than 1 person to reduce the risk of discriminating”; interviewers should be prepared and understand discrimination law; “it's a good idea to ask each applicant the same questions where possible”; by law you must ask anyone coming to an interview to tell you if they need reasonable adjustments; and any notes or recordings must be stored securely and confidentially, following data protection rules.

Two specific traps with teamwork questions:

• Social questions dressed as teamwork. What someone does at the weekend, whether they will come to the pub, whether they have children who limit their evenings: none of these measures collaboration, and some of them are unlawful to consider.
• Screening for sameness. Asking for someone who will "fit in" and rejecting people who work differently is how a team stops improving. Ask whether the person can work with difference, not whether they resemble the team.

The euphemism problem

"Team player" is sometimes an honest description of a job that genuinely depends on other people. It is sometimes a euphemism for compliant, sociable, or willing to be available at any hour. If what the advert means is "does not push back", the interview will select for it and the team will get worse. Before the questions go on the sheet, say out loud what the phrase means here; if it will not survive being said out loud, take it off the person specification. Our guide to interview questions to ask candidates covers the wider question set, and why teamwork matters covers what a working team actually needs.

After the hire

Collaboration is the easiest thing to assess in the first month and the least often reviewed. Put one teamwork behaviour from the interview into the new starter's probation objectives, name the colleague who will see it, and ask about it at the first check-in. A person who interviewed well and hands over badly is a problem you can fix in week three and cannot fix in year two.

Frequently asked questions

What are good team player interview questions?

Questions about specific past behaviour that a candidate could answer badly: what they did when a commitment became hard to keep, how a colleague found the work they handed over, the last time they asked for help, a disagreement and how it ended, who else made their biggest success happen, and what they would change about how a team works. Avoid "are you a team player?", which cannot be failed.

How do you assess teamwork in an interview?

Define what teamwork means in the job first, choose six to eight behavioural questions covering dependability, help, disagreement, sharing, difference and improvement, ask every candidate the same questions in the same order, write down what an acceptable answer contains before you start, and rate each answer on the same scale with the evidence noted. That is the structured-interview method the US Office of Personnel Management describes.

How should a candidate answer "are you a team player?"

Do not answer with an adjective. Give one example with the detail an interviewer can check: what the team was doing, what you specifically did, what happened, and what you would do differently. Name the other people and what they contributed. A story with names, dates and an outcome beats any amount of enthusiasm.

Are there teamwork questions you should not ask?

Yes. Anything that goes to a protected characteristic or to someone's life outside work, including social availability, family, age, health or beliefs. Acas says interview questions must not discriminate, that more than one interviewer reduces the risk, and that applicants must be asked about reasonable adjustments.

What is the difference between a team player and a pushover?

A team player achieves a shared goal with other people, which includes disagreeing well, raising problems and saying no to work that would break a commitment. A pushover agrees. Questions about disagreement and repair are the ones that separate them, which is why they belong in every teamwork interview.

Your next step: write the sheet before the first interview

1. Answer the four questions about what teamwork means in this job.
2. Choose six to eight questions and agree what an acceptable answer contains.
3. Book two interviewers, the same questions in the same order, and a rating scale.
4. Put one teamwork behaviour into the probation objectives for whoever you hire.

For the wider selection process these questions sit inside, read and download our recruitment and selection guide. The guide is free to read, and the PDF uses our short download form.

Want the behaviours you hired for to show up in probation objectives and reviews, on your own form? Book a New Dynamics demo and bring your current interview sheet. You can also email contact@new-dynamics.com.