Team Interview Questions to Ask
Questions to ask when you are interviewed by the team you would be joining rather than by a manager or recruiter. Peers will tell you things no one else in the process will, if you ask them for examples instead of policies.
The questions
Open any question for the note
What are you each working on at the moment?
Why ask it
An easy opener that gets everyone talking, and the detail tells you whether the team's work matches the job advert. Answers pitched entirely at strategy level from people who should be hands on usually mean the real work is elsewhere.
What does a normal week look like for you?
Why ask it
Ask for the shape of it: meetings, focused blocks, interruptions. A week nobody can describe because every week is different is a signal about planning, not about variety.
How did you each end up on this team?
Why ask it
Internal moves suggest the company is somewhere people want to stay. If everyone joined in the last six months, ask what happened before that, since you are likely joining a rebuild.
Who would I be working with most closely day to day?
Why ask it
Job descriptions describe a role, not a working relationship. If the answer is a person or team not in the room, ask whether you can speak to them before you decide.
How does work actually get assigned here?
Why ask it
Listen for whether people pick up work or are handed it, and who decides priority when two things collide. Vagueness here tends to mean whoever shouts loudest sets the queue.
What is the last thing the team delivered that you were pleased with?
Why ask it
A concrete recent example is the strongest evidence you can get that the team ships. Long pauses, or an example from two years ago, are worth following up on gently.
What have you tried that did not work?
Why ask it
Teams that can name a failed experiment and what they learned tend to be safe places to be wrong. A team that cannot think of anything is either new or not telling you.
How much of your week goes on meetings?
Why ask it
Ask for a number, then check it against the calendars you can see. A wide spread between team members usually means seniority determines who gets to concentrate.
Who do you go to when you are stuck?
Why ask it
If every answer names the same one person, that person is a bottleneck and probably tired. If nobody can name anyone, you would be joining a team that works alone in parallel.
What do new people find hardest in the first month?
Why ask it
Better than asking about onboarding, because it produces the specific obstacle rather than the documented plan. Answers about access, permissions, and undocumented systems are common and honest.
How does feedback happen here outside formal reviews?
Why ask it
Look for a routine occasion rather than good intentions. If the only mechanism is the annual review, expect to find out about problems long after they were fixable.
What happened the last time two of you disagreed about a decision?
Why ask it
Asking about a specific instance gets past "we talk it through". If nobody can recall a disagreement, either the team avoids conflict or decisions are made above them, and both matter to you.
What is your manager like to work for?
Why ask it
Ask when the manager is not in the room, and pay attention to how carefully people phrase it. Praise limited to competence with nothing said about how they treat people is its own answer.
When was the last really busy stretch, and what happened to your hours?
Why ask it
Every team has crunch. What matters is how often it comes, whether it was planned, and whether anything changed afterwards. Answers that treat late nights as a badge tell you what is expected.
What does the team disagree with the wider company about?
Why ask it
Reveals where the friction sits: budget, priorities, a process imposed from elsewhere. A team that claims total alignment is either very lucky or being careful in front of a candidate.
Has anyone left the team recently, and do you know why?
Why ask it
Direct but fair, and the reaction is informative. Regular departures with cheerful explanations are worth probing, especially if the role you are applying for is a backfill.
What kind of person struggles on this team?
Why ask it
Easier to answer honestly than "what kind of person succeeds", and more useful to you. Answers about needing structure, or needing autonomy, tell you plainly whether you fit.
What would you change about how the team works if it were up to you?
Why ask it
Gives everyone permission to be candid about one thing. If two people name the same problem, treat it as real and ask what has been tried.
What is expected of someone in this role in the first six months?
Why ask it
Peers often describe this differently from the hiring manager, and the gap is the thing to notice. Where expectations conflict, ask both sides in front of each other before you accept.
What has kept you here?
Why ask it
A closing question that lets people end on something genuine, and the answers are revealing. Money and inertia are honest answers, but a team that can only cite the people and not the work is telling you about the work.
Getting straight answers out of a team interview
Practical guidance for the conversation itself
Preparing
Find out who is in the room
Ask the recruiter for names and roles beforehand. Peers, a skip-level manager, and a stakeholder from another department each need different questions, and a question aimed at the wrong person wastes a slot.
Bring six questions, expect to ask three
Team panels run over. Rank your questions so the two you most need answered come first, and drop the pleasant ones if time goes.
Prefer examples to policies
"How do you handle disagreement" invites the official answer. "What happened the last time you disagreed" makes people recall an actual event, which is much harder to polish.
In the room
Ask the same question twice
Put one question to two different people in separate sessions and compare. Differences about priorities, workload, or the manager are usually more informative than either answer alone.
Watch the group, not just the answers
Notice who speaks first, who gets interrupted, whether anyone corrects a colleague, and whether the quiet people are junior or simply unheard. Interview behaviour is a reasonable preview of meeting behaviour.
Direct your questions
Address a question to a named person rather than the room, then let others add to it. Open questions to a panel tend to be answered by whoever is most senior, which is the answer you can get anywhere.
What to be careful about
Do not interrogate your future peers
These are people who will vote on hiring you and then sit next to you. Ask hard questions once, accept a partial answer gracefully, and move on rather than pressing three times.
Do not read a rehearsed answer as a bad sign
People who have interviewed candidates for months have set answers. Follow up with "can you give me an example from this year" instead of concluding they are hiding something.
Treat the family comparison as information
Teams that describe themselves as a family often mean long hours and blurred boundaries are normal. Ask what happens when someone needs to leave at five, and listen to the pause.
Afterwards
Write down what you were not told
Within an hour, note which questions got a real answer and which got deflected. Gaps are easy to forget once an offer arrives, and they are the questions to put to the hiring manager.
Ask for one more conversation if you need it
If a key person was missing or a question went unanswered, ask for fifteen minutes with them before you decide. Employers rarely refuse, and a refusal is itself an answer.