Interview Questions to Ask Candidates About Teamwork
These are for hiring managers and panels choosing questions to ask in an interview about teamwork. Most of the 57 are behavioral: they ask what a candidate did on a real team, not what they believe about teams. They run in the order an interview can take them: the candidate's role on a team, day-to-day collaboration, disagreement, accountability, feedback, and last the kind of team they fit, where the questions turn to preferences. If you came for interview questions to ask about collaboration, the second group ends with four on colleagues who work differently, teammates never met in person, other departments and people the candidate had no authority over.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Team role
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.
Think of the last project you finished with other people. Which part of it was yours?
Why ask it
Teamwork stories drift into 'we', and this brings the answer back to one person. If two follow-ups later you still cannot say what the candidate did themselves, write that down as unknown instead of filling the gap with a good impression.
Tell me about joining a team that was already up and running. How did you find your place in it?
Why ask it
Whoever you hire will be doing exactly this in their first month with you. Good answers involve watching how things were done before proposing changes, asking who owned what, and one small early contribution the team had been wanting.
When have you stepped back and let someone else lead?
Why ask it
A candidate with nothing but leading stories may struggle as one contributor among several. Find out what they did while not leading, since useful support is more specific than staying out of the way.
When have you picked up a piece of work that was drifting, without anyone asking you to?
Why ask it
Initiative only counts as teamwork when the others know about it. You are looking for someone who noticed the gap, filled it, and told the team they had, so nobody else started the same job.
What role do you tend to end up playing on a team, whatever your job title says?
Why ask it
People answer with a label: the organiser, the sceptic, the one who writes things up. Ask for the last meeting or project where they played it, because a label with no occasion behind it is a self-image.
Tell me about a stretch when your team's morale was low. What did you do about it, if anything?
Why ask it
'If anything' gives permission for an honest answer, and 'I kept my head down' is one. Where they did act, something small and aimed at the cause, such as getting an unclear priority settled, is worth more than a story about cheering people up.
Who is the best teammate you have worked with, and what did they do that you have copied?
Why ask it
The description is the standard the candidate holds other people to. 'Copied' asks for a changed habit, such as sending a summary after every meeting, so admiration with nothing borrowed from it is a thinner answer.
In your last role, how much of your week was spent working alone and how much with other people?
Why ask it
A calibration question with no right answer. Someone who has worked mostly solo for three years can still be a fine hire, but their teamwork examples will be older, and you should compare their split with the real one in your role.
What have you done that made a team run better after you left it?
Why ask it
The answer shows whether they build anything that outlasts them: a template, a rota, a checklist, a habit of writing decisions down. Plenty of capable people have nothing to point to, which is worth knowing before you hire one into a team whose processes still need building.
Collaboration
When did you last ask a colleague for help, and what did you ask for?
Why ask it
A recent, specific request, such as a second opinion on a draft or an hour of someone's time on a spreadsheet, suggests asking is routine for them. If nothing comes to mind, find out whether help was hard to get on their last team or hard for them to ask for.
Tell me about helping a colleague with something that was not your job. What did it cost you?
Why ask it
The cost is the part that sorts the answers. Help that came out of spare time is easy; help that delayed their own work required a decision, and you want to hear whether anyone was told about the trade.
Describe a time you handed work over to someone else. How did you prepare them?
Why ask it
A poor handover does its damage after the person who made it has moved on, so nobody tells them. Someone who mentions writing things down, walking the person through it and staying reachable afterwards has probably received a bad one.
How do you keep teammates up to date on your work without flooding them?
Why ask it
It asks for a habit, so follow with 'what did you send last week?' Useful answers match the channel to the news: a short written update for progress, a call the same day for anything that changes someone else's plan.
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. If you hear about creating a safe space and no method, ask what they did in the last meeting they sat in.
Tell me about something only you knew how to do on a team. What did you do about that?
Why ask it
Being the only one who knows something feels like job security and is a risk to everyone else. The answer to hope for is a written procedure, a walkthrough or a second person trained, done before a holiday forced it.
Tell me about bringing a new person on your team up to speed.
Why ask it
Onboarding is unglamorous collaboration, and it is seldom anyone's formal job. Ask what the newcomer could do alone by the end of the first fortnight, which shows whether the candidate taught or simply answered questions as they arrived.
Tell me about something you produced together with one other person. How did you split the work?
Why ask it
With only two people there is nowhere for a habit to hide. The details to get are who decided the split, what happened where the two halves met, and whose name went on the finished report, design or plan.
Tell me about a deadline that put your whole team under pressure. What changed in how you worked together?
Why ask it
A tight deadline tempts everyone to put their head down and stop talking. A short daily check-in, one shared list or an explicit split of the work is what a candidate describes when they have seen that happen and done something about it.
Describe a misunderstanding between you and a teammate that cost time. Where did it start?
Why ask it
A thoughtful candidate can trace it to one moment, often an assumption nobody confirmed at the end of a meeting. What they now check before starting is the part to write down, since the lesson is worth more than the story.
Tell me about working with someone whose working style was very different from yours. What did each of you change?
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.
Tell me about working closely with someone you rarely or never met in person. What did you do differently?
Why ask it
Time zones, a second language and separate sites all take away the chance to sort things out in passing. Concrete answers mention agreed overlap hours, decisions written where everyone could find them, and a problem that was settled entirely in messages.
Tell me about a project where you had to collaborate with another department. What did they need that you had not expected?
Why ask it
Work between departments often stalls on priorities before personalities come into it: the other team has its own deadlines and its own measure of success. A candidate who can say what the other side was judged on has done this for real.
Describe a time you needed something from someone who had no obligation to help you.
Why ask it
This is influence without authority, and a role that depends on other teams calls for it most weeks. Good answers describe making the request easy to say yes to; be wary if the only tool was getting a manager to lean on the person.
Disagreement
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
The line being drawn is between disagreement and obstruction. A good answer has them arguing the case, losing, and then backing the decision in front of others; going quiet and doing it their own way is the warning.
When have you given up something you wanted so a team could reach agreement? What did you give up?
Why ask it
A compromise with no cost the candidate can name was probably not one. Notice too whether they tell it as a settled matter or are still arguing the point with you across the table.
Tell me about a colleague you found hard to work with. What did you try?
Why ask it
Pay attention to how the colleague is described. 'She wanted every detail agreed before starting and I wanted to begin' is an observation; 'she was impossible' is a verdict, and candidates who deal in verdicts have often tried one thing and stopped.
Describe a conflict between two other people that affected your work.
Why ask it
The candidate had no authority here and still had work to finish. Staying out of it, taking a side and keeping the work moving around the dispute are three different answers, so ask why they chose theirs.
Tell me about a disagreement at work where you turned out to be wrong.
Why ask it
Candidates tend to rehearse the disagreements they won, so this one often gets a less polished answer. What matters is how they found out, whether they said so to the other person in plain words, and how long that took.
When have you raised a problem in a team meeting that nobody else wanted to mention?
Why ask it
Ask what happened in the minute after they spoke, and whether they would do it again. Someone who was ignored the first time and found another route, such as writing it up with the numbers, is showing persistence without drama.
Tell me about a project you could see going wrong when the decision was not yours. What did you do?
Why ask it
The useful colleague raises it once, clearly, with the person who can act, and then keeps working. Be cautious about a story that ends with the candidate proved right and having said nothing at the time.
How have you handled disagreeing with someone more senior in front of the rest of the team?
Why ask it
There is a choice in every instance: say it in the room, or wait and say it privately. Neither is always right, so what matters is that the candidate can explain why they chose as they did on a real occasion.
Tell me about a disagreement with a teammate that was never settled. How did you keep working together?
Why ask it
Some conflicts do not end, and a candidate who claims all of theirs did is leaving something out. A believable answer describes an arrangement: who decides which things, what gets put in writing, what the two of them stopped arguing about.
Accountability
Describe a time you depended on someone who was not delivering. What did you do?
Why ask it
Two things to hear: whether they spoke to the person before going over their head, and whether they quietly did the work themselves. The second feels heroic and can hide the problem until it is too big to fix.
Tell me about a time you let a teammate down. How did they find out?
Why ask it
The second question is the test. Hearing it from the candidate before the deadline is one kind of colleague; discovering it on the day is another. Early warning is the habit worth hiring for.
Tell me about covering for a colleague who was away or overloaded.
Why ask it
Find out how the cover was arranged and whether it had an end date. Open-ended cover turns into a second job and then into resentment, so a candidate who agreed limits at the start has learned something useful.
Tell me about a week when two teammates both needed you at once. Who waited, and how did they hear about it?
Why ask it
Being wanted by two people at once is ordinary on a busy team, so most candidates have a real week to describe. The answer to hope for has the one who waited being told early and given a date, not left to work it out from silence.
Tell me about a time credit for shared work went to the wrong person.
Why ask it
How they raise something uncomfortable that concerns their own standing is what you are hearing. Saying nothing and making a scene are both common; a private word with the person who took the credit, or with whoever handed it out, is the response a team can live with.
When have you made sure a colleague got the credit for their work?
Why ask it
Generosity is easy to claim, so ask for the mechanism: naming the person in the report, or having them present their own section to the client. 'I always credit my team' with no occasion attached is a slogan.
Tell me about a team result you were not proud of. What would the others say your part in it was?
Why ask it
Asking for the teammates' view makes it harder to tell the story as something that happened to the candidate. One specific thing they would do earlier next time is a full answer; a list of other people's failings is an answer too.
Describe a time a teammate's mistake landed on your desk. What did you say to them?
Why ask it
Order matters here: did the fix come before the conversation about fault, and was that conversation held with the person or about them, to others? The tone of the retelling, years later, is informative as well.
Tell me about a job nobody on the team wanted. Who ended up doing it, and how was that decided?
Why ask it
Every team has one: the minutes, the weekend rota, the shared inbox. A candidate who always took it and one who never did are both telling you something, and the strongest answers describe making it fair, usually by taking turns.
How do you decide when a problem with a teammate needs to go to your manager?
Why ask it
You are listening for a threshold. Reasonable ones include having spoken to the person first, a pattern instead of a single lapse, and an effect on customers or deadlines. Then ask for the last time they crossed it.
Feedback
Tell me about feedback you gave a peer that was difficult to give.
Why ask it
With a peer there is no authority to lean on, so the words have to do all the work. Ask what they said, as near to word for word as they can remember, and how the two of them got on afterwards.
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.
Tell me about a colleague reviewing your work and finding a real problem. How did that conversation go?
Why ask it
Criticism of work is easier to take than criticism of behaviour, so this is the gentler test, and defensiveness still shows in the retelling. 'They were right, and it would have reached the client' is the sound of someone who welcomes a second pair of eyes.
What would your last team say is the most frustrating thing about working with you?
Why ask it
Candidates carry a stock weakness, but putting it in teammates' mouths makes it harder to dress up. Follow with 'what have you done about it?', and note the answer: where your process takes references, it is one a former colleague can confirm.
Tell me about the last time you praised a colleague for a specific piece of work.
Why ask it
Teams run on noticed effort at least as much as on criticism, and interviewers seldom ask about it. Someone who remembers what the work was and why it mattered is someone who watches what the people around them contribute.
When has a teammate's feedback been wrong, in your view? What did you do with it?
Why ask it
Taking every comment on board is no more a skill than rejecting all of them. Look for a candidate who tested the point or checked it with a third person, then went back and explained their decision instead of quietly ignoring it.
How did your last team look back on its own work once a project was over? What did you say the last time it did?
Why ask it
Not every team holds a review, so 'we never did' is a fair answer and you can ask whether they pushed for one. Where there was one, what the candidate said in it shows whether they can criticise shared work with the people who did it sitting there.
Team fit
What do you need from a manager in order to work well with the rest of a team?
Why ask it
The answer describes the conditions the candidate is used to, and you can compare them with what the hiring manager will in fact provide. 'Clear priorities when two people want different things' is a need most managers can meet; daily direction may not be.
How would you want a teammate to tell you they were unhappy with something you had done?
Why ask it
A small, practical question that sets up the first awkward conversation before it happens. People who have thought about it answer at once, with a preference such as privately and within the same week.
What should your new teammates know about how you work before your first week?
Why ask it
Think of it as a spoken user guide. Concrete answers, such as going quiet when concentrating or preferring requests in writing, show self-knowledge and save the team a month of guessing.
What did your last team do that you would want to bring here, and what would you be glad to leave behind?
Why ask it
Both halves describe norms the candidate takes for granted: how meetings ran, who reviewed what, how late in the evening people answered messages. Set them beside how your team really works, including the parts you would rather not admit to.
From what you have heard so far, what would you still want to know about how this team works?
Why ask it
It checks whether the candidate has been listening, and it hands them the floor. Curiosity about who they would sit beside, how work is shared out and how the team argues is a good sign in someone who says teamwork matters to them.
What kind of team do you not do well in?
Why ask it
Candidates seldom expect this, and a specific answer, such as struggling where nobody clearly owns anything, lets you judge fit against the team you really have. "I get on with everyone" tells you only that they would rather not say.
Assessing teamwork and collaboration in an interview
Practical guidance for the conversation itself
Choosing questions for the role
Interview questions to ask about collaboration across teams
For a role that sits between departments, such as a project manager, an analyst or anyone in operations, lean on the four questions that close the Collaboration group: the colleague with a different working style, the teammate rarely met in person, the other department's needs and the person with no obligation to help. Add the Disagreement question about a team decision the candidate lost. Cross-team work is mostly persuading people who have their own priorities, and those five show whether the candidate has done it.
For a first job or a thin work history
Someone straight from school or returning after years away still has team evidence: a group assignment, a sports side, a volunteer rota, a family business. Say at the start that examples from outside paid work are welcome, then ask the same questions. The part that was theirs, the teammate they let down and the job nobody wanted work as well for a student society as for an office.
For a remote or hybrid team
Ask how they keep teammates up to date, how they handed work over, where a misunderstanding started, and about the colleague they rarely met in person. Follow that last one by asking for a problem they sorted out entirely in writing. On a team that seldom shares a room, collaboration is largely the quality of messages and documents, and a candidate who can only describe corridor conversations may find the change hard.
For a role that leads without managing
Senior specialists and team leads without direct reports need the questions about stepping back, raising what nobody wanted to mention, and disagreeing with someone more senior. Add the one about what made a team run better after they left. You are checking that their influence came from being useful to other people and not from their position.
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 to eight, not the whole list
Six to eight questions with real follow-ups tell you more than every question asked once. Take one or two from each group, and weight the choice towards 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.
Keep the stories at work
A teamwork story can wander into a candidate's health, family or life outside the job. Steer it back to what happened on the team and do not note the rest. What an interviewer may ask about or record differs by country and state, so check with whoever handles hiring rules where you are.
Check with a reference
If your process takes references, ask the candidate for a former peer as well as a former manager, and ask that person what the candidate was like to share a deadline with. A manager often cannot answer that. Some employers confirm only dates and job title, and what a referee may be asked differs by country, so find out how it works where you hire before counting on it.