In early 2025, Google quietly changed how it communicates offer timelines to candidates. Several engineering candidates on Blind and Levels.fyi noticed that the standard “4-6 week” timeline language from recruiters had shifted to “6-10 weeks” for most roles above L4. That shift wasn’t announced anywhere officially. It just started showing up consistently in recruiter calls.
Google’s hiring process has a well-documented skeleton that doesn’t change much year to year. The 2026 version of that process still has the same stages: recruiter screen, technical phone screen, onsite loop, hiring committee review, team matching, offer. What has changed is the texture within those stages, and some of that matters for how you prepare.
The current stage-by-stage breakdown
The recruiter screen remains a 30-45 minute non-technical call. The main thing it determines is your leveling band. Google interviews at specific levels (L3 through L7 and above), and the difficulty of your technical rounds is calibrated to that level. If you’re experienced and the recruiter levels you too low, it’s worth pushing back gently on that conversation. Being leveled at L4 when you’re targeting L5 affects both your compensation negotiations and the rigor of your onsite.
The technical phone screen is one coding problem, 45 minutes, typically LeetCode medium difficulty. As of 2025-2026, the screen is conducted via Google Meet with a shared Google Doc (not a specialized coding environment). This is an important logistical detail. Working without autocomplete or syntax highlighting is harder than it sounds.
The onsite loop is 4-5 interviews on the same day or across two consecutive days for some roles. It includes 2-3 coding rounds, a system design round (for L5 and above), and at least one behavioral round. Google calls the behavioral component a “Googleyness” assessment in its official documentation, though interviewers don’t typically label it that in the room.
What the hiring committee stage actually involves
Most candidates understand the committee exists. Fewer understand what it reviews. The committee sees a written packet: the feedback from every interviewer, the recruiter’s notes on leveling, any prior Google interview history on your account, and the hiring manager’s input if a team has already expressed interest in you.
The committee does not see your resume in isolation. They’re evaluating written assessments of your performance. One strong round doesn’t automatically outweigh a weaker one. A strong “recommended hire” from a senior Googler does carry weight, but the process is designed to prevent a single interviewer from making a binary decision.
In 2025 and into 2026, there are reports from candidates on Levels.fyi that committee review timelines extended significantly for roles in AI/ML infrastructure and some SRE tracks. One candidate reported a 7-week wait between onsite and offer in a Vertex AI infrastructure role. That could be an outlier. But the 6-10 week expectation that recruiters now set seems to reflect genuine process load, not just hedging.
Team matching is separate from getting an offer
This confuses a lot of candidates. Passing the hiring committee review means you’re “HC approved,” which is a status on your file. It doesn’t mean you have a job. You still need to match with a specific team that has headcount, wants your skills, and operates at your approved level.
Team matching can take 2-4 weeks on top of the committee timeline. Candidates sometimes lose their offer window if they don’t engage actively with the teams they’re matched to. Google gives you a list of teams interested in your profile. Responding quickly, doing brief team calls, and expressing a clear preference speeds this up considerably. Passive candidates who wait for teams to make the first move after receiving the list sometimes let the window close.
What’s different in 2026 for senior roles
For L6 and above, the onsite loop now commonly includes a second behavioral round rather than an additional coding round. Google appears to be weighting leadership signals more heavily for staff-level hiring following their 2024-2025 workforce changes. This is consistent with what AWS CEO Matt Garman told Fortune in October 2024 about the broader industry shift toward expecting senior engineers to demonstrate decision influence, not just technical depth.
I don’t have clean data on L3-L4 roles specifically, so that qualifier matters: most of what’s different in 2026 affects mid-to-senior level hiring.
Preparation that accounts for the current process
The coding prep hasn’t changed much. Dynamic programming, graphs, and binary search still cover the majority of problems that candidates report encountering. The 2024 Stack Overflow Developer Survey showed algorithm fluency as the top technical hiring signal at large tech companies, and that’s consistent with what Google assesses.
What has shifted is the weight on behavioral and design rounds. Preparing 8-10 structured stories for behavioral questions, with at least two covering technical disagreements you navigated, is more important in 2026 than it was in 2022 when coding performance dominated the committee discussion.
If you want to practice articulating trade-offs out loud under interview conditions, Craqly‘s mock interview sessions simulate a real-time interview environment where you can get feedback on explanation quality, not just answer correctness. Given the increased weight on behavioral and design assessment at Google right now, that kind of practice is more directly useful than it was a few years ago.
The process is documented enough that surprises mostly come from logistics, not content. The candidates who get stuck tend to be surprised by the committee timeline or by the team matching step. Neither needs to catch you off guard.
Check Levels.fyi’s interview experience reports in the weeks before your onsite. Recent firsthand accounts from candidates who interviewed at your target level are more current than any static guide, including this one.