How does the mix of rounds in an engineering onsite loop change from junior to senior to staff level?
answer
- Round count stable, contents shift
- Coding slots shrink as rung rises
- Design enters the loop at senior
- Staff adds architecture and influence
- Ask recruiter for round list and rung
basics
~20 sJunior loops are mostly coding rounds. Senior loops trade some coding slots for a system-design round and a deeper past-work round. Staff-and-above loops add architecture and cross-team influence rounds, and coding usually shrinks to a single screen.
solid answer
~40 sThe number of rounds barely moves across levels; what moves is the mix. A junior onsite is coding-heavy — often three coding rounds plus one past-work round and a hiring-manager conversation — because the panel is buying raw problem-solving and trainability. At senior, one or two coding slots are replaced by a system-design round and a round that probes ownership of delivered work, so the panel can see scope as well as code. At staff and above, coding often drops to a single screen while architecture, cross-team influence and past-impact rounds take over, and interviewers from outside the hiring team join. Ask the recruiter for the round list and the rung being assessed before you plan preparation: the same six-round day is measuring three different things depending on which rung it is scoped to.
go deeper
Know that your loop is deliberately coding-weighted and that this is normal, not a sign the company undervalues you. Be able to name the rounds you will sit and say which one you expect to carry the most weight.
Explain why the mix moves — which evidence each added round is collecting and why a design round becomes necessary once you are expected to own a system rather than implement one. Be able to sketch a plausible round list for two adjacent rungs.
Show that you check the mix before preparing: get the round list and the rung from the recruiter, then allocate practice in proportion to the slots rather than by habit. Be ready to describe how you would prepare differently for two loops of identical length.
Own the tradeoff in loop design itself: every slot spent on coding is a slot not spent on scope evidence, and a badly balanced loop mis-levels people in both directions. Be ready to argue what you would cut from a six-round day to buy an architecture round.
## The count stays flat, the mix does not Most companies run an onsite of roughly the same size for every engineering level — four to six rounds is the common shape. What changes with the rung is **what those slots are spent on**, because the panel is buying something different at each level. A useful way to hold it: a loop is a set of bets the company is placing on evidence it can gather in a day. At junior, the bet is *can this person write correct code and grow fast*. At senior, it is *can this person own a system and a project end to end*. At staff and above, it is *can this person change what several teams do, and choose the right problem in the first place*. The round list follows the bet. ## An illustrative ladder Take an invented example: the internal platform group of a national freight carrier — a non-tech enterprise whose engineers keep shipment-tracking and dispatch services running. The hiring manager there shares the group's **internal level-ladder document** (some companies call it a job architecture) with candidates who ask for it. That document is the artefact everything below hangs on: it states, rung by rung, what scope of impact the company expects. Their loops come out roughly like this: | Rung | Coding | System design / architecture | Past work, influence, leadership | Hiring manager | |---|---|---|---|---| | Entry / junior | 3 | 0 | 1 | 1 | | Senior | 2 | 1 | 1 | 1 | | Staff (infrastructure) | 1 | 2 | 2 | 1 | Read the shift as ratios rather than as a rule: coding falls from about three-fifths of the junior day to roughly one-sixth of the staff day, while design plus influence rises from one slot in five to four in six. Those exact counts are one invented org's; the *direction* is what generalises. Notice what does **not** happen. Coding does not vanish at staff — most companies keep one screen, partly to confirm the person still reads and writes code, partly because a staff engineer who cannot follow an implementation discussion is a real risk. And the round count does not balloon; a longer loop usually signals a scheduling constraint or an added team-match conversation, not a more senior rung. ## What each added round is actually testing - **The system-design round entering at senior** is testing whether you can hold requirements, constraints, storage, failure and scale in one head and make defensible tradeoffs out loud. It arrives at senior because senior is the first rung on most ladders where you are expected to own a design rather than implement someone else's. - **The past-work round deepening at senior** stops being *tell us about a project* and starts being *what exactly did you decide, what did you trade away, what happened after*. The interviewer is matching your described scope against a rung in the ladder document. - **The architecture and cross-team rounds at staff+** are looking for influence without authority, choosing between competing approaches across teams, and evidence that you changed a direction rather than executed one. Interviewers from partner teams often join here, because the company is checking whether people outside the hiring team would follow you. ## Why this matters before you prepare The most expensive mistake is running identical preparation for every level: the same algorithm drilling, the same rehearsed project summary, no evidence of scope. A candidate who does that arrives at a staff loop having practised the one round that now carries the least weight, and improvises through the four that carry the most. The fix is mechanical — get the round list, get the ladder rung, and allocate practice in proportion to the slots. ## Getting the mix before the loop Recruiters will normally tell you the round list, the rung, and who is interviewing, because a candidate who prepares for the right rounds makes their job easier. Reasonable asks: *what does the loop consist of and which level is it scoped to*, *is there a design round and what shape is it*, and *is there a written ladder or job-architecture document I can read*. Not every company has one, and not every company shares it; where they do, it is the single most useful preparation document you will get, because it names the evidence the panel has been told to look for. One caution: level names are not portable. A rung called senior in one org can sit above or below a rung with the same name elsewhere, and internal ladders differ even between two groups in the same company. Read the *expectations text*, not the label.
- If the round count is roughly the same at every level, what is the panel measuring differently?The evidence being collected, not the volume. A junior loop gathers correctness, speed of learning and coachability; a senior loop gathers design tradeoffs and end-to-end ownership of a delivered system; a staff loop gathers cross-team influence, problem selection and impact that outlived the project. Same day length, different questions behind the questions.
- Does the coding round disappear entirely at staff level?Usually not. Most companies keep one coding or code-reading screen at staff and above, both as a floor check and because an architect who cannot follow an implementation discussion is a genuine risk. What changes is weight: one weak coding round rarely sinks a staff loop on its own, whereas at junior it often does.
- How would you find out the round mix before you start preparing?Ask the recruiter directly for the round list, the rung the loop is scoped to, and the format of any design round. Then ask the hiring manager whether the company has a written level ladder or job-architecture document you can read. Those two asks cost one message each and change where every practice hour goes.
saying these in an interview costs you the question
- Running the same coding-drill preparation for every level
- Assuming a longer loop means a more senior loop
- Treating the design round as optional at senior
- Bringing no evidence of scope beyond code personally written
- Assuming a level name means the same thing at every company