Courses › Behavioral Interviews › Question Themes

Team Matching & Hiring-Manager Calls

How team matching works, what managers assess, and the questions to ask each team.

At many large companies, passing the interview loop doesn't put you on a team. You pass a general hiring bar first, then go through team matching: a series of calls with hiring managers who each have an open role. Google is the best-known example, and other large companies use variations of it. At smaller companies, a hiring-manager call often happens before or during the loop instead.

These calls are less formal than interviews, but they still decide outcomes. A strong candidate can wait months for a match, or lose an offer, by handling them badly.

How team matching usually works

You pass the loop, often reviewed by a hiring committee or a calibration panel.
A recruiter shares your profile with teams that have open roles at your level and location.
Interested managers schedule calls, usually 30–45 minutes each.
You and a manager both say yes, and the offer is finalized for that team.

The details vary: some companies match before the offer and some after; some let you talk to several teams at once. Ask your recruiter how it works, how long it usually takes, and how long your interview results stay valid.

[!NOTE] It's a two-way conversation A team-match call is partly an interview and partly a sales pitch from the manager. Both sides are deciding. Treat it like a conversation between future colleagues, not an exam.

What the manager is assessing

Expect a short version of Tell Me About Yourself, one or two project deep-dive questions, and "Why does this team interest you?"

Preparing for each call

Research the team. Ask the recruiter for the team's area and a short description. Read anything public: blog posts, product pages, papers or talks.
Pick two projects from your past that fit the team's work, and practice a two-minute version of each.
Prepare specific questions (below). They're the main way you show real interest.
Know what you want. Decide in advance what matters most to you: the domain, the tech, the manager's style, growth, on-call, location.

Questions worth asking

"What would my first project be, and what does success look like at six months?"
"What are the team's biggest challenges right now, technical or otherwise?"
"How is work planned and prioritized? Who decides the roadmap?"
"How big is the team, and what's the mix of seniority?"
"What does on-call look like? How often are people paged?"
"How do you support growth? Who has been promoted recently, and what did they do?"
"How do you like to give feedback, and how often do you have 1:1s?"

See Questions to Ask Your Interviewer for more.

Common mistakes

Treating it as a formality. Managers do turn candidates down, usually for low enthusiasm or a poor fit with the work.
Being too eager to say yes. Accepting the first team that wants you can mean a year on work you don't care about. If something worries you, ask about it.
Saying negative things about current or past teams. It gives the manager a reason to worry.
Being vague about what you want. "I'm open to anything" sounds flexible but gives the manager nothing to match to.

When matching takes a long time

Matching can take weeks, sometimes longer, especially for senior roles or in a slow hiring market.

Stay in regular, polite contact with your recruiter, and tell them if your priorities or constraints change.
Ask whether broadening the location, product area or tech stack would help.
If you have another offer with a deadline, say so. It's normal information, not a threat, and it often speeds things up.

Hiring-manager calls at smaller companies

At smaller companies, the hiring manager often talks to you before or during the loop. The same preparation applies, with more focus on motivation ("Why us, why now?") and on your ability to work with less structure. See Motivation Questions.

[!TIP] Practice Tell me about yourself · What kind of team do you want next? · Questions for us · Why this company?