Google's SWE loop runs in stages: resume screen, sometimes the Google Hiring Assessment (GHA), a technical phone screen (1-2 rounds), and an onsite loop of four to six rounds, followed by hiring-committee review and team matching. End to end it typically takes six to twelve weeks; team matching is the main variable and can stretch it to several months.
The phone screen is a ~45 minute live coding interview, now conducted on Google's internal Virtual Interviewing Platform (VIP, at interview.google.com) with syntax highlighting and auto-indentation, a step up from the plain Google Docs of prior years, though some geographies still use Docs. The onsite is usually two coding rounds, a system design round (from L5 up), and a behavioral / "Googleyness" round (which can be skipped for some candidates). Since mid-2025, Google expects at least one onsite round to be in-person, citing AI-assisted cheating. In May 2026, Google announced a pilot replacing one coding round with a Gemini-assisted "code comprehension" round for select US junior/mid-level teams; standard coding rounds remain AI-prohibited.
Hiring is committee-driven, so the onsite is decoupled from any specific team. You match to a team after passing. Team matching historically followed hiring-committee approval, but the order now varies: some teams (notably EU offices, and roles filled via hiring-manager outreach) match before the HC so a manager can add a statement of support. Coding is weighted more heavily than system design at Google, the only FAANG where that's true.
The interview loop
- Recruiter & resume screen - Recruiter call on background and logistics; resume is screened for the bar.
- Google Hiring Assessment (GHA) - A ~50-question, 30-45 min personality/situational judgment test introduced in 2022. Not every candidate gets it (referral/hiring-manager-outreach candidates sometimes skip). Failing blocks re-entry for 6 months.
- Technical phone screen - ~45 min live coding on Google's VIP platform (or a shared Google Doc in some geographies). Data structures and algorithms. A second phone screen happens only when the first did not produce enough signal.
- Onsite loop - 4-6 rounds of ~45 min each:
- Coding (x2) - Two coding interviews, weighted as the most important rounds at Google. AI is strictly prohibited.
- System design (L5+) - Required from L5 up; absent at L4 and below.
- Behavioral / Googleyness - Can be skipped for some candidates; the lowest-weighted round at Google.
- Hiring committee & team match - A committee of 4-5 engineers/managers who did not interview you reviews packets. Can request 1-2 additional interviews ("more info"). Team matching historically follows HC approval but the order now varies; some teams match before the HC. HC approval is valid ~12 months; if no team selects you in that window, the candidacy expires and you must re-interview.
What they look for
- Data-structures and algorithms fluency with clean, optimal solutions. Coding is the most important round at Google.
- Clear communication of trade-offs and complexity.
- Googleyness: collaboration, humility, and dealing with ambiguity. Scored, but can be skipped.
How to prepare
- Drill medium/hard DS&A and always state time/space complexity and alternatives. Coding is weighted more heavily than system design at Google.
- Practice on Google's VIP platform (interview.google.com) or a plain shared doc. No autocomplete in some configurations, no run button.
- Prepare structured behavioral stories; the Googleyness round is scored, not a formality, though it may be skipped.
- Ask your recruiter whether team matching happens before or after the HC for your loop and geography.
