What stages does a standardized big-tech engineering hiring loop run, in order?
answer
- It starts long before any code
- Cheap filters first, expensive ones last
- Count the rounds on the schedule
- A review sits after the onsite
- Placement with a team comes last
basics
~10 sA standardized big-tech loop runs a recruiter screen, often a timed online assessment, one or two technical phone screens, a four-to-six-round onsite, a committee-style review, then team match before an offer conversation.
solid answer
~40 sThe loop is a fixed pipeline, and the recruiter normally mails the stage list up front. It opens with a recruiter screen covering role, target level and timeline. Many pipelines then add a timed online assessment, followed by one or two technical phone screens of about 45 minutes each. Clearing those earns the onsite: four to six rounds, most of them 45 minutes, mixing coding, system design and a values or leadership round. The written evidence then goes to a committee-style review that no single interviewer controls, and only after that come team match and the offer conversation. Each stage is a separate filter with its own bar, so the mailed stage list tells you exactly which filter you are standing in front of next.
go deeper
Be able to name the stages in order without hesitating, and know which one you are booked into next. Open the schedule the recruiter mails you before every call rather than after it.
Explain what each stage filters for and roughly how long it runs, so you can budget preparation across coding, design and behavioural rounds instead of pouring it all into the one you enjoy most.
Show that you manage the whole pipeline: you confirm the stage list in writing, notice when a round is added, dropped or re-staffed, and adapt preparation instead of discovering the change on the day.
Own the tradeoff in how much of a fixed pipeline you try to reshape. Asking for a round to be re-scoped or resequenced can buy a fairer read of your strengths, but it spends recruiter goodwill and calendar time you may need elsewhere.
## What a loop is A *loop* is the whole ordered sequence of conversations a company runs before deciding to hire someone. The distinguishing property of the large-tech model is that the sequence is **fixed in advance, published to the candidate, and broadly the same for everyone applying at a given target level**. It is a pipeline, not a conversation. That is why interviewers assume you already know the format: it was mailed to you. ## The stages, in order | Stage | Typical shape | What it filters for | |---|---|---| | Recruiter screen | one short call | role, target level, location, timeline, interest | | Online assessment | timed, done alone | coarse coding filter at high volume | | Technical phone screen | one or two rounds, about 45 minutes each | first substantive technical signal | | Onsite / full loop | four to six rounds, most about 45 minutes | the evidence the decision is built on | | Committee-style review | no candidate present | consistency of the bar across teams | | Team match | one or more short manager calls | placement, not approval | | Offer conversation | recruiter-led | terms, start date, paperwork | Several of those stages are skippable and the map tells you which were skipped. An online assessment is commonly waived for referred or experienced candidates; a second phone screen is often dropped when the first one is unambiguous; some pipelines hire straight to a named team and have no separate team-match step at all. The pattern above is a *common* industry shape, not a rule every company follows, and details vary by company and by year. ## The stage list is a document, and you should treat it as one The most useful artefact in the whole process is the written loop map the recruiter sends before the onsite: a table of rounds with times, durations and, usually, a one-word label for each. It is the schedule the interviewers are working from. Read it as a specification of what you will be asked to produce. **Worked example.** A mid-level backend candidate is booked for a five-round day. The mailed map reads: 09:15 coding, 10:15 coding, 11:15 system design, 13:00 values and collaboration, 14:00 hiring-manager conversation. Four of those five rounds run 45 minutes; the manager block runs 30. The candidate spends the two preceding weeks entirely on coding practice, walks into the 11:15 block, and hears an open-ended design prompt about a service under sustained write load. The round is not a surprise to anyone but the candidate. It was on the schedule for eighteen days. That is the characteristic failure on this leaf: **being surprised by a stage that was on the published schedule all along.** It costs you a round you could have prepared for, and it is visible to the panel, because a candidate who has not read their own schedule looks like a candidate who does not prepare. ## Why the order is stable Each stage is cheaper than the one after it. The screen costs one recruiter twenty minutes; the onsite costs five engineers most of a day plus the write-up time afterwards. Ordering the filters from cheap to expensive is the whole economic logic of the pipeline, and it explains two things candidates often misread: - **The early stages are genuine filters, not formalities.** More candidates are removed at the phone-screen boundary than anywhere else, precisely because that is the last cheap place to remove them. - **The late stages are not interviews in the same sense.** The committee-style review reads what interviewers wrote; team match is a placement conversation. Preparing for them the way you prepare for a coding round is a category error. ## The calendar shape End to end, a full loop commonly runs four to eight weeks, and most of that is waiting rather than interviewing. The two long gaps are scheduling the multi-round onsite across several interviewers' calendars and waiting for the review to be convened. Knowing that the calendar is mostly queueing keeps you from reading silence as rejection. ## What to do with the map Three concrete moves, all of them cheap: 1. **Confirm the stage list in writing** before you start preparing, and ask what any unlabelled block covers. A nameless 45-minute round is usually behavioural or a manager conversation, but guessing is unnecessary when the recruiter owns the schedule and will simply tell you. 2. **Budget preparation per stage**, weighted by how many rounds test each thing. Two coding rounds and one design round is not a signal to spend all your time on coding; it is a signal that one third of your evidence comes from a skill you may be practising least. 3. **Re-read the map the morning of the day.** Rounds get swapped, an interviewer calls in sick and a stand-in changes the topic, and the updated schedule is usually mailed rather than announced.
- Which stage of this pipeline is skipped most often, and for whom?The timed online assessment. It is a high-volume coarse filter, so it is commonly waived for referred candidates, for experienced hires, and for anyone whose phone screen is already scheduled. A second phone screen is the next most commonly dropped stage, usually when the first one produced an unambiguous result. The mailed stage list reflects whatever was skipped, which is why it is worth reading rather than assuming a standard shape.
- The schedule you were mailed lists a 45-minute block with no title beside it. What do you do?Ask the recruiter in writing what that block covers. They own the schedule and answering is routine. An unlabelled block at that length is most often a values or collaboration round, sometimes a hiring-manager conversation, but guessing costs you a prepared round for no reason. Asking also gives you a written record if the schedule changes later.
- Why do interviewers assume a candidate already knows the stage sequence?Because it is published, mailed ahead, and identical for everyone at that target level. The format is not confidential and not improvised. When a candidate is visibly surprised by a round that was on their own schedule, the panel reads it as a preparation problem rather than a communication failure, and that impression carries into the write-up.
saying these in an interview costs you the question
- Walking into a scheduled design round having prepared only coding
- Never opening the stage list the recruiter mailed
- Treating a phone screen as a formality before the real interview
- Assuming one outstanding round can carry a weak loop
- Believing a single friendly interviewer decides the outcome