The hiring-manager conversation is where a company decides whether you fit a specific team, and where you decide whether that team deserves the next few years of your career. At Google and Meta it happens after you have passed the loop, as team matching; at Amazon and Microsoft the manager is part of the loop and shares the decision. This chapter covers what each company does, what managers assess, how to evaluate a team with questions that get real answers, what to ask each kind of interviewer, the red flags, how to state preferences, and how the hand-off to the offer works.
Where the manager conversation sits
Companies split into two models. In centralised hiring, you pass a general bar first and find a team afterwards. In team-specific hiring, you apply to one team's opening and its manager is involved from the start. The model changes what the conversation is for.
| Company | Model | What happens |
|---|---|---|
| Centralised | After the hiring committee approves your packet, your recruiter shares it with teams that have headcount at your level. You have calls with interested managers, usually 30 to 60 minutes and conversational; at senior levels you may also meet a director or future teammates. A match needs both sides to opt in. Some roles are tied to one team from the start and skip this step (reported). | |
| Meta | Centralised | Team matching comes after the onsite and before the offer. You talk with hiring managers, and you can ask to talk with engineers on the team; reported numbers range from a handful of teams to more than ten. Both you and the manager must opt in. Calls are reported to be scheduled one at a time. In early 2025 some candidates were reported to be placed straight into an org with open headcount (Monetization) without matching; asking for normal team matching was reported to be possible. |
| Amazon | Team-specific | You interview for a team's opening. For SDE III, Amazon's own guide says the technical phone screen is 60 minutes with a senior leader on the team, half Leadership Principles and half coding and design, followed by five 55-minute interviews. A Bar Raiser from outside the team sits in the loop, and Amazon says the Bar Raiser and the hiring manager make the final decision together. |
| Microsoft | Team-specific | The hiring team runs the loop; candidates commonly report an early round with the hiring manager. The last interview of the day is traditionally the "As Appropriate" (AA) interview with a senior person who reads the earlier feedback. A Microsoft engineer's blog (Raymond Chen, 2023) says the term is no longer official and the role has changed over time, while 2025–26 candidate guides still describe a senior final interviewer whose view carries the decision. Ask your recruiter who your last interviewer is. |
| Atlassian | Team-specific | A manager interview is one of the published loop stages, alongside coding, system design and a values interview. |
| Apple, Uber, LinkedIn | Team-specific | A hiring-manager round is common; Apple candidates report a manager call early in the process. Treat it as part technical, part fit. |
Treating team matching as "not an interview". Recruiters at Google and Meta may say it is just a chat, and technically it is not scored like the loop. But if no manager says yes, you do not get an offer: Google approvals are reported to expire after about a year, and Meta candidacies are reported to lapse if no team takes you. Prepare for it as seriously as a behavioural round.
What the manager is assessing
By the time a manager talks to you, the technical bar is often already settled. The manager's questions are about one team, now: will this person be productive here, stay, and make the team better?
| Signal | What they want to know | How they find out | What to show |
|---|---|---|---|
| Relevance | Does your experience map to our problems? | "Tell me about a recent project." "Have you worked with X?" | Connect your work to their domain out loud: "our reconciliation problem is the same shape as your [problem]." |
| Level | Can you take the scope we have, without hand-holding? | How you describe your past scope and decisions | The decisions you made and their reach, in numbers |
| Motivation | Do you want this team, or any offer? | "Why are you interested in us?" "What are you looking for?" | Specific interest, based on something you learnt about them |
| Ramp-up risk | How long until you are useful? | Questions about new domains you learnt, and how you learn | An example of becoming productive fast in an unfamiliar area |
| Working style | Will you work well with me, my PM and my team? | "How do you like to work?" "Tell me about working with a PM." | Concrete habits: how you write designs, run reviews, handle disagreement |
| Retention | Will you stay long enough to repay the hiring cost? | Career history, "where do you see yourself" | A growth path that this team can plausibly offer |
Questions managers commonly ask
- Walk me through a recent project you led and the hardest part of it.
- What are you looking for in your next role? What kind of work do you want more of, and less of?
- Why this team? What do you know about what we do?
- How do you work with product managers and other teams?
- What are your strengths, and where do you want to grow?
- Tell me about a time you disagreed with a manager. (Some managers use a short behavioural question as a check.)
Prepare the first three from Tell me about yourself (the two-minute version and the "what are you looking for" draft) and the project from The project deep-dive round, cut to five minutes.