The Team-Match Call, Scored on Six Weights to Take, Hold Out, or Widen

This scorecard covers the stretch between passing the hiring committee and getting a written offer, when you are on hiring-manager calls with one team after another. It works at any employer that interviews and levels you first, then places you on a team. After each call you score the team on six weighted dimensions, turn the score into one move (take, hold out, or widen), and send the recruiter a scripted reply within 24 hours.

What does a team-match decision actually trade off?

Every team-match decision weighs the seat in front of you against the time, attempts, and outside options you have left to find a better one. Matching usually happens one team at a time, and your packet stops circulating once you match. So saying yes to one team also means saying no to every team you have not met yet.

Team matching is the phase after the general interview loop and committee approval, when hiring managers for specific teams talk to you before any written offer exists. Three mechanics shape every decision in it:

• It is serial. IGotAnOffer describes matching as "typically serialized, meaning you're introduced to teams one at a time." Each call uses up part of a limited window.
• A match stops the search. A Google candidate on Blind reports that once you match, "the recruiter will stop pushing your packet to managers."
• The offer can depend on it. Meta moved team matching ahead of the offer, so "offers are contingent on team matching completely successfully," per interviewing.io. Hello Interview reports seeing prospective offers rescinded when no team match came through.

The written window and the working window

Your approval has a written validity, counted in months. The time a recruiter actually spends pushing your packet is counted in weeks. The gap exists because recruiters are judged on closes. One Blind commenter says what a recruiter is "measured against is the number of offer acceptance."

Every value in that table comes from candidates or coaches. None of these employers publishes its numbers. Reading across the rows, the working window comes out at roughly one-eighth to one-twelfth of the written one (my derivation from the reports above). Plan around the engagement column, not the validity column.

There is no published base rate to lean on either. No dataset gives the share of candidates who never match or the median number of calls. IGotAnOffer notes that "many candidates report passing every interview but never matching." For Meta, interviewing.io puts the number of calls at "a handful, and sometimes it's over 10." Another guide says "three to five hiring-manager conversations of 45 to 60 minutes." The job market moves this a lot. interviewing.io quotes: "When the market is good, you can talk to 20 different teams at the same time."

The six dimensions of the scorecard and their weights

The scorecard has two halves. The Seat score rates the team itself: scope and fit, the manager signal, and level and band consistency. The Runway score rates your position: match window left, attempts left, and outside pipeline. The Seat score tells you whether this team is worth taking. The Runway score tells you whether you can afford to wait for a better one.

Score each dimension from 1 to 5, then weight it within its half:

These weights are my judgement, not a published standard. No published standard exists. Scope carries the most Seat weight because a mismatch is expensive to undo: reported internal transfer waits run about 12 months, so a wrong team is a year-long bet at minimum. Window carries the most Runway weight because it runs out fastest. If your situation calls for different weights, change them, but set them before your first call. Weights adjusted after a call to justify a decision you already wanted are not a scorecard.

Level also works as a gate, on top of its weight. A Level score below 3 blocks a take, however high the Seat score is. A down-level hidden behind a great team is the most expensive mistake in this phase.

How to score each dimension on the call

Score each dimension against fixed anchors at 1, 3, and 5, using evidence from the call or from the recruiter in writing. Use 2 or 4 when the evidence falls between two anchors. Score 1 when you have no evidence, because a question you did not ask is not a good answer.

Team match call questions to ask the hiring manager

Candidates report calls of about 30 to 60 minutes. Spend the last third on these questions. Each one feeds a dimension:

1. What would my first project be, and who owns it today? (Scope)
2. Why is this seat open: a backfill, growth, or a new team? (Manager)
3. When was the last reorg here, and what triggered it? (Manager)
4. Is this headcount approved, or still being decided above you? (Manager)
5. How long have the people on the team been on it? (Manager)
6. What level is this seat budgeted at? (Level. Confirm with the recruiter in writing.)

Scope and fit

• 5: The team's work matches your last two years, and you can name your first project and who you would take it over from.
• 3: Adjacent work. You would pick up one new domain or one new stack, not both.
• 1: A new domain and a new stack, or the manager could not describe a first project.

This score lies when the manager is selling. Enthusiasm on the call tells you how good the pitch was, not how good the job is. If the team has a written role description, run it through Refolk for a fit score built from your own work history. That gives you a second opinion from someone other than the person trying to fill the seat.

Here is what a scope mistake costs, in reported transfer waits:

One Blind poster calls Meta's one-year mark "a guideline, not a hard rule," so treat these numbers as typical, not fixed. Even so, score scope as if you will be on this team for a year.

Manager signal

• 5: A clear reason the seat is open, a last reorg 12 or more months ago, approved headcount, and a mix of tenures that includes some long ones.
• 3: One flag, with a good explanation.
• 1: A reorg in roughly the last three months with no clear trigger, headcount "being debated above the person who is hiring you," or short tenures across the whole team.

These are rules of thumb from practitioners, not research findings. No published study links what you notice on a team-match call to later attrition or transfers. The reorg rule comes from a practitioner write-up: "A reorg twelve months ago is normal. A reorg three months ago is recent and you should ask why." On tenure, the same body of advice says "Very short tenures across the board are a warning sign." This signal lies when "growth headcount" turns out to mean a team created in a reorg within the last six months. Ask for the date and the trigger, not just whether there was a reorg.

Level and band consistency

• 5: The recruiter has confirmed in writing that the seat is at your committee-approved level, and the pay band checks out against public data such as levels.fyi.
• 3: The level has only been confirmed verbally.
• 1: The seat is budgeted lower, or you are being shown at adjacent levels with nothing in writing.

At Google, "the hiring committee will also decide on leveling" before matching starts. But one process guide lists "Compensation and level confirmed" as happening "After a match is agreed." Levels do move. One candidate reports they "interviewed for L5, cleared for L4," and interviewing.io has seen "engineering managers with 10+ YoE accept an L3 (basically a new grad) offer." A 3 here only clears the gate if you get written confirmation before your final yes.

Match window left

• 5: You are in your first two weeks of matching, and your packet went to a manager in the last 7 days.
• 3: You are in weeks three to five, or the last send was 7 to 14 days ago.
• 1: You are past week six, no hiring-manager call is scheduled within 7 business days, or you are in the last month of written validity.

Score from the engagement column of the first table, not the validity column. At Meta, one report says candidates are removed from the matching pool after 60 days, even though the interview results stay valid for a year.

The size of your job market also affects how quickly a declined team gets replaced. A smaller market means fewer hiring managers for each candidate, and so fewer calls.

These figures count people, not open seats. Read them as a measure of market size, not hiring demand. There are three practical readings:

• UK-only searches: score Window one point lower than the calendar suggests, because each decline is harder to replace. That adjustment is my judgement.
• Location: in a 25-person sample, 12 UK engineering managers (48%) were in London, against 4 of 25 (16%) of the US sample in SF or Seattle. That sample is too small to rely on. If you will not work in London, ask your recruiter how much it narrows your options rather than treating the sample as fact.
• Recruiters: with 2.7 engineering managers per technical recruiter in the US, it is the recruiter, not the supply of managers, who decides who sees your packet.

Attempts left

• 5: This is your first or second call, and the recruiter has told you there is no practical limit.
• 3: You have declined two or three teams, and the recruiter is still booking calls.
• 1: The recruiter has named or hinted at a limit you are close to, or calls have slowed since your declines.

This is the softest dimension, because no employer publishes a limit. At Google, the answer to whether declining carries a penalty is "Officially, no." But one coach has "seen candidates get 'quietly deprioritized' after declining a few matches." At Meta, one Blind commenter reports a limit of 5 teams. Ask the recruiter directly how many teams you can decline before you are deprioritized, and score from the answer.

Outside pipeline

• 5: You have a written outside offer you can show, with a known deadline.
• 3: You are in final rounds elsewhere, with dates.
• 1: Nothing is active.

One guide calls a competing offer "the most common way to speed things up, and it is information they need, not a threat." This signal lies when the offer is not real. Google "is known to require evidence of other offers," so a made-up offer does more than fail: it costs you credibility. If this dimension scores 1 and your window is short, the fix is more applications, not a bluff. Refolk tailors your resume to each posting and drafts the cover letter, so you can realistically push a few strong outside applications through during the same weeks as matching.

Turning the score into take, hold out, or widen

Compute Seat = 0.4 × Scope + 0.3 × Manager + 0.3 × Level, and Runway = 0.4 × Window + 0.3 × Attempts + 0.3 × Pipeline. Take if Seat is 3.5 or higher and Level is at least 3. Hold out if Seat is under 3.5 and Runway is 3.0 or higher. Widen if Seat is under 3.5 and Runway is under 3.0.

There is one edge case. If Seat is 3.5 or higher but Level is below 3, do not take yet. Send the take reply as a conditional, asking for the level in writing, and treat the team as a hold until the answer arrives.

Three worked cases

• Take. Scope 4, Manager 3, Level 5 gives a Seat of 1.6 + 0.9 + 1.5 = 4.0, and the level gate passes. Runway does not matter here.
• Hold out. Scope 3, Manager 2, Level 5 gives a Seat of 3.3. Window 4, Attempts 5, Pipeline 3 gives a Runway of 1.6 + 1.5 + 0.9 = 4.0. You can afford to wait.
• Widen. Same Seat of 3.3, but Window 2, Attempts 2, Pipeline 1 gives a Runway of 0.8 + 0.6 + 0.3 = 1.7. Waiting for the same kind of team is unlikely to work, so change what you are being shown.

A strong seat is a take at any runway. Runway only decides what you do with a weak one.

What a take commits you to

A take sets off a chain of commitments. Read it before you send the yes.

Team / manager:
Call date:                Days in matching:
Packet last sent to a manager (date):

SEAT
Scope and fit    x0.4  = ___   Evidence:
Manager signal   x0.3  = ___   Why open / last reorg date and trigger / tenure:
Level and band   x0.3  = ___   Level in writing? Y / N
Seat score       = ___

RUNWAY
Window left      x0.4  = ___   Week of matching / last send:
Attempts left    x0.3  = ___   Declines so far / stated limit:
Outside pipeline x0.3  = ___   Offers I can show / deadlines:
Runway score     = ___

GATE: Level >= 3?  Y / N
MOVE: Take (Seat >= 3.5 and gate passes) / Hold out (Seat < 3.5, Runway >= 3.0) / Widen (Seat < 3.5, Runway < 3.0)
Reply sent at (time):

The team-match procedure, from approval to reply

The procedure runs from the day of your committee approval to the signed offer. The scoring step is the only part no published guide provides. The other six steps come from practitioner playbooks.

Two notes on timing. Ask for the org list in week 2, not week 5. Waiting means, in one playbook's words, "asking a recruiter to do extra work for a candidate they have already deprioritized." The escalation trigger in step 6 comes from PracHub's playbook: act "If no HM chats are scheduled within 7 business days." Hello Interview's target is to "Ask for 2 - 3 HM intros within 7 - 10 days." These are targets, not measured response times. Nobody has published how quickly recruiters actually respond.

Recruiter replies to send within 24 hours

Send the reply that matches your move within 24 hours of the call. A fast, specific reply is the best protection you have against being quietly deprioritized. A decline that says exactly what would fit gives the recruiter something to act on. A vague "not for me" gives them nothing.

To decline without losing your place:

• Be specific. One sentence on why this team does not fit, tied to the work, never to the manager personally.
• Redirect. Name the domain, stack, level, and locations that would fit.
• Ask for the next step. Request the next intro in the same message, with a timeframe.
• Ask about the limit. Find out how many declines you have before you are deprioritized. The answer becomes your Attempts score.

When you widen into an adjacent job family, your packet goes to managers who are reading it for a different kind of role. PracHub suggests asking to "circulate your packet to C1 and adjacent roles (e.g., analytics, experimentation) while preserving your interview validity." Another playbook suggests asking the recruiter to "target a different slice of teams where your experience maps more directly." A resume rewritten for that slice makes the match obvious. Refolk can produce that version from your own history without you rewriting it by hand.

TAKE
Subject: [Team] - I'd like to move forward

Hi [Recruiter],

Thank you for setting up the call with [Manager]. I'd like to move forward with [Team]. Before I confirm, could you send me in writing:
- the level for this seat (my committee approval was at [Level])
- the compensation package, or when I should expect it
- whether any further committee or review step happens after the match

For timing: I have an offer from [Company] with a deadline of [date]. (Delete this line if you have no written offer.)

Thanks,
[Name]

HOLD OUT
Subject: [Team] - passing, and next intro

Hi [Recruiter],

Thanks for the call with [Manager]. I appreciated the time. I'm going to pass on [Team]. The reason is specific: [one sentence, e.g. the work is mostly X and my last two years are Y].

A strong fit would be teams working on [domain / stack], at [Level], in [locations]. Could you line up the next intro this week?

One question so I can plan: how many teams can I pass on before my packet is deprioritized?

Thanks,
[Name]

WIDEN
Subject: Widening my match search

Hi [Recruiter],

Thanks for the intro to [Team]. It isn't the right fit, and I'd rather widen the search than wait. Could you:
- circulate my packet to adjacent orgs and job families such as [family 1] and [family 2], and to [additional locations]
- send me the list of orgs currently hiring at my level
- confirm in writing that my onsite results still apply at [Level] if I am shown at adjacent levels

I'm hoping for 2 to 3 manager intros in the next 7 to 10 days. Is that realistic?

Thanks,
[Name]

If a widen request gets no answer, follow up with a call and a specific date. A Capital One candidate reported that they "opened up my relocation status to all locations. Recruiter doesn't seem to acknowledge or reply to these emails." A widen request with no acknowledgement has not happened yet.

When to negotiate during team matching

Do the groundwork for negotiation during matching, and negotiate the actual numbers once level and compensation are on paper. The sources disagree on timing. The disagreement mostly comes down to how short the offer deadline is at a given employer.

The case for negotiating during matching comes from interviewing.io: "Team matching is actually the part of your Meta journey where you have the most leverage and power." The reason is the deadline that follows. Meta is described as "often giving you a deadline of something like two days." Matching is the only period with no clock running.

The case for waiting comes from Final Round AI, writing about Google: "You negotiate here, not earlier," meaning at the offer. At Google, compensation only arrives after a match, so before that there is no number to negotiate.

My position combines the two. During matching, do the things that cannot be done in two days:

• Declare real outside offers and deadlines in step 2, while they can still speed things up.
• Check the band for your level against public data such as levels.fyi.
• Get the level in writing before your final yes. Negotiating level is far harder after you have accepted a team.
• Ask for the package and its timing in your take reply.

When the offer arrives, the preparation is already done, so even a two-day deadline is enough.

How the team-match scorecard goes wrong

Each dimension has a typical false positive: a score that looks right and isn't. These are the most common ones, with the check that catches each.

1. Trusting the written validity. Candidates treat the 12-month written validity as their real window. The false positive is a "valid" packet that nobody is sending out. Check: ask when your packet was last sent to a manager, and score Window from that date.
2. Assuming a committee pass means you are hired. One Google candidate who "declined a couple of offers" was then rejected by committee after matching. Check: ask whether any committee review happens after the match at your employer. If it does, a take is not the finish line, and declines before it cost more.
3. A strong team hiding a down-level. Great fit can mask a lower level that only shows up when the offer arrives. Check: get the level in writing before you say yes. The level gate exists for this case.
4. Misreading the manager signal. "Growth headcount" can mean a team formed in a reorg within the last six months. Check: ask for the date and trigger of the last reorg, and whether headcount is approved or still being debated.
5. Guessing attempts left. No employer publishes a decline limit, so this score is an estimate. Check: ask the recruiter directly how many declines you can make before you are deprioritized. If they won't say, score 3, not 5.
6. Widening into a lower band. Asking to be shown at adjacent levels can quietly lock you into the lower one. Check: get written confirmation that your onsite results apply at the higher level before your packet goes out. Also confirm the recruiter has acknowledged the request, because widening emails can go unanswered.
7. Overstating your outside pipeline. Mentioning offers you do not have backfires at Google, which requires evidence of other offers. Check: only score and mention offers you can show in writing.
8. Declining after you have matched. Turning down a team you have already matched with is not the same as passing on a call. One Google recruiter told a candidate that declining meant they would "have to match with the declined offer team next time." If your approval expires, "you'll need to reapply and go through the interview process again." At Amazon, one commenter says re-entry within a year works "as long as you didn't renege." Check: make the take decision with the scorecard before matching formally, not after.

Before you send the reply, and keeping the scorecard current

Run the checklist below before every reply, and re-score Window and Attempts after every call. Those two only go down. Scope, Manager, and Level reset with each new team.

Keep every scorecard in one log, so you can compare Seat scores across teams instead of comparing each new team to your memory of the last one. If three teams in a row score under 3 on Scope, the problem is probably which teams you are being shown, not your bar. That pattern is your cue to widen, whatever the calendar says.

Every figure in the first table comes from candidate and coach reports, and those figures shift with the market. Don't rely on them as current. Re-check them for your own case in step 1 by asking your recruiter for the validity period, whether matching is serial, and any limit on declines, all in writing. Your recruiter's written answers outrank anything in this guide.