Late in a hiring process for a management job, someone often says it casually: "We'd like you to meet the team." The people in that room will report to you if the offer comes through, and for an hour the usual direction of power runs backwards. They are interviewing their future boss, and their opinion usually reaches the hiring manager before the day is over.
What this round usually looks like
The format varies more than any other round, and it is usually less structured. Some employers set up an informal coffee with two or three future reports and no hiring manager present. Others run a panel of reports, where four to six people sit across a table with a shared list of questions. A third version looks like a skip-level conversation in reverse: one senior member of the team, often the person who has been holding things together since the last manager left, spends forty minutes with you alone.
Ask the recruiter in advance who will be there and whether the session is scored. You will not always get a straight answer, but the question itself tells them you take the team seriously. If there is no scorecard, assume there is still a verdict. Someone will be asked "so, what did you think?" the moment you leave the building.
Note the difference from the peer round. The live article "The Peer Interview: What Your Future Teammates Judge" covers people deciding whether they want to work beside you. This one is the opposite case: people deciding whether they want to work for you, with far less ability to fix a bad choice later.
What your future reports are really trying to find out
Reports rarely care about your strategy deck. They care about what their working week will feel like with you in charge. Under the polite questions, a few concerns keep coming back.
- Fairness. Will you hand out the interesting work evenly, or will you have favourites? Will you judge people on results or on how loudly they talk in meetings?
- Protection. Will you push back when another department dumps an urgent request on the team at 5 p.m.? Will you defend their time, or pass every demand straight down?
- Their careers. Will you know what each of them wants next, and will you spend political capital to get it for them?
- What already exists. The team built processes, tools and habits under the previous manager. They want to know whether you will treat that work with respect or arrive with a plan to tear it all down.
The last concern is the one candidates miss most often. A team that has spent two quarters patching a broken release process does not want to hear that the new boss "has ideas about the release process." It wants to hear that you will understand it first.
And underneath all of it sits one question nobody asks directly: will this person listen? You answer that one with your behaviour in the room, not with a sentence.
The questions they ask, and answers that do not over-promise
The questions sound simple. The trap is that every one of them invites a promise you cannot keep yet, because you do not know the team, the budget or the politics.
"How would you handle it if one of us disagreed with a decision?" Give a real example of a disagreement you lost or changed your mind on. A story where you were right all along tells them nothing about how you listen.
"Are you planning to change things?" The honest answer is that you will change something eventually, but not before you understand why things are the way they are. Say what your first weeks look like: one-to-ones with each person, sitting in on the team's rituals, reading the last few retrospectives. That is a plan, not a promise.
"How do you feel about remote work, or our current hours?" Do not commit to a policy you do not control. Say what you value, and say that you will check what the employer allows before telling anyone anything.
"Will you help us get promoted?" Be careful here. You can say that you will learn what each person is aiming for and argue for them where the case is strong. You cannot say that promotions or raises are coming, and a sharp team will notice if you try.
Questions about your management style, or about a time you led a team through something hard, have their own live articles on this site, so prepare those separately. In this room, keep the answers shorter than you would for a hiring manager. Long answers read as a person who talks more than they listen.
Questions you should ask the team
This is the half of the meeting most candidates waste. You have direct access to the people who know what the job really involves, and they are often more candid than anyone else in the process. Ask at least two of these, and listen properly to the answers.
- "What works well right now that you would hate to see a new manager break?"
- "If you could keep one thing exactly as it is, what would it be?"
- "What do you want from a manager that you have not had enough of?"
- "Where does the team lose the most time in a normal week?"
- "What would make you think, six months from now, that hiring me was a good call?"
Write a few words down after each answer. It shows you value what they said, and you will use those notes in your first month if you get the job. If two people give you contradictory answers, do not resolve it on the spot. Just say you have heard two views and would want to understand both.
When the internal candidate is in the room
Sometimes one of the people interviewing you applied for this same job and did not get it, or is still in the running. You may be told, you may guess from the questions, or you may never know. Treat everyone the same way and you are covered in all three cases.
If you do know, do not mention it, do not try to win them over with flattery, and do not compete with them in front of the others. Ask them the same questions you ask everyone, and give their answers real attention. The person who knows the team best is often the strongest ally a new manager can have, and they will remember whether you treated them as a threat.
What not to do in this meeting
A few mistakes come up again and again, and each one can sink an offer that looked secure.
- Judging the previous manager. Even if the team clearly has complaints, nodding along to criticism of someone they may still like is a bad start. Say you want to understand what worked and what did not, and leave it there.
- Announcing changes. "The first thing I'll do is restructure the on-call rota" tells them you decided before meeting them.
- Promising promotions or pay. You do not control either yet, and a broken promise in month three costs more than a modest answer today.
- Treating it as a formality. Arriving tired, checking your phone, or saving your best energy for the next executive round all get noticed.
The team is not asking whether you are impressive. It is asking whether life will be better or worse with you in charge.
If you are preparing the rest of your application at the same time, keep the story consistent. The management scope on your CV and the reasoning in your first-manager cover letter should match what you tell the team, and a tool like Postulit can turn your LinkedIn profile into a CV draft so you can check those lines line by line before the meeting. A visit around the office, if one follows, is a separate test with its own article.
Before the meeting, write down three things: one disagreement you lost and what you learned, the plan for your first few weeks in two sentences, and two questions you genuinely want answered. Bring nothing else. Then spend more of the hour listening than talking, and let the team leave thinking you already understand them a little.