What end-to-end calendar should you plan for in a big-tech hiring loop?

## Why the calendar matters at all Candidates budget preparation and misbudget patience. The interviews in a full loop total perhaps five or six hours of actual conversation; the loop occupies a month or two of your life. Understanding where the time actually goes prevents the two expensive misreadings: treating silence as rejection, and starting three pipelines on the same day expecting them to finish together. ## Where the weeks go A representative shape, using one invented but internally consistent example — a mid-level backend candidate whose recruiter mailed the stage list on day zero: | Day | Event | Elapsed | |---|---|---| | 0 | Recruiter screen; stage list mailed the same afternoon | — | | 6 | Timed online assessment submitted | 6 days | | 13 | Technical phone screen | 1 week later | | 27 | Five-round onsite day | 2 weeks later | | 34 | Review convened, outcome communicated | 1 week later | | 39 | First team-match conversation | 5 days later | That is 39 calendar days — a little over five and a half weeks, comfortably inside the four-to-eight-week band that is typical for these pipelines. Note the distribution: **two long gaps account for more than half the elapsed time**, and neither is about you. - **Screen to onsite (day 13 to day 27).** Booking four to six interviewers into a single day, around their own on-call, travel and delivery commitments, is the single largest fixed cost in the calendar. Some companies split the day across two half-days to loosen this, which shortens the wait and lengthens the loop. - **Onsite to outcome (day 27 to day 34).** Interviewers write up their rounds within a day or so, but the review that reads them runs on its own cadence. A week here is ordinary; longer is common when the calendar hits a holiday period or a hiring freeze rumour is circulating. The front of the pipeline can also stretch for reasons that have nothing to do with your candidacy — a role being re-approved, a target level being re-confirmed, a recruiter changing hands. ## Reading a quiet stretch correctly Silence in a standardized pipeline is weak evidence. Rejections in these processes are usually communicated, often quickly, because the pipeline is instrumented and closing a candidate out is a routine step. A long gap much more often means a review has not yet been convened, or a recruiter is carrying forty other candidates. The productive response is a single, specific, unemotional check-in against the timeline the recruiter themselves gave you — not three of them, and not a re-application through another channel. ## Planning moves that actually help 1. **Ask for the lags up front, in writing.** At the recruiter screen, ask what the typical gap is between each stage in their process right now. Recruiters answer this readily, and it turns your calendar from a guess into a plan. It also gives you the reference point for a later check-in. 2. **Start the slow pipeline first.** If you are running more than one process, the one with the longest published lag should begin earliest. This is scheduling arithmetic, not leverage-building. 3. **Front-load preparation.** The two weeks before the onsite date are firm; the two weeks before that are not. Do the bulk of the work early, because the schedule can move forward as easily as back — an interviewer freeing up can pull your day earlier by a week. 4. **Re-check the mailed stage list whenever the date changes.** A rescheduled onsite frequently comes back with a different round mix, because the substitute interviewer covers a different area. Discovering that on the morning of the day is the avoidable version of this whole problem: the change was in the mail. 5. **Keep your own dated record.** Which stage happened when, what the recruiter said the next lag would be. When the process runs long, that record is what lets you ask a precise question instead of a plaintive one. ## What varies All of the above is a common industry shape, not a rule. Loops for teams hiring urgently can compress to a couple of weeks; loops interrupted by a re-org, a headcount review or a seasonal slowdown can run well past eight weeks without anything being wrong. Ask, record what you are told, and re-ask when the reality diverges from it.