How Google interviews
Draft, not yet verifiedFramework not yet verified. Community estimate — check before you rely on it.
Official sources: Google Careers - Our hiring process, Google Careers - Interviewing at Google: best practices, advice, and tips, Google re:Work - A guide to structured interviewing for better hiring practices (updated March 2026), Google Careers - Interview (archived copy from 16 Nov 2019, lists Googleyness), Google Careers - Decide (archived copy from 11 Dec 2019, hiring committees and review), Google Careers - Students (internships and early-career roles), Google Careers - job search (titles in use, from Software Engineer II to Director, Engineering).
Before you rely on this
- Draft, not yet verified. Written on 2026-11-21 from Google's public careers and re:Work pages and the sources listed below. Nobody has checked it against a Google recruiter's packet; check with your recruiter before relying on it.
- Google's 2026 pages do not use the word 'Googleyness'. Its 2019 careers page listed four attributes (general cognitive ability, leadership, role-related knowledge and Googleyness); its 2026 structured-interviewing guide names role-related knowledge, problem solving and leadership. The round is still widely called Googleyness and Leadership. The five competencies here come from both, and each one's history says where.
- Only the Googleyness and Leadership interview is covered. General cognitive ability (problem solving), role-related knowledge, coding and system design are out of scope, as is the Google Hiring Assessment some candidates take before interviews.
- The hiring-committee details come from Google's archived 2019 'Decide' page; Google's current page says only that it brings everything together and takes a number of perspectives into account. The committee needing consensus, the seven-point recommendation scale and team matching are reported by interviewing.io, a coaching source, not by Google.
- Level codes (L3 to L9 for engineers, L5 to L9 for managers) are from levels.fyi. Which title goes with which code (Staff as L6, Principal and Director as L8, and so on) is widely reported but not published by Google, and was not confirmed for this draft. Manager ranks are aligned with L6 to L8 as an approximation.
- Question and follow-up counts are an estimate: Google's published example questions each come with three follow-ups. Role focus competencies are our reading, not Google's.
- Answer format
- STAR, with X-Y-Z results
- Google's interview tips suggest STAR and spell the A as Activity: the specific steps you took and the roles you played. For the Result they suggest 'Accomplished [X], as measured by [Y], by doing [Z]'. Keep it concise, since Google notes interview time is limited, and give one specific time rather than what you usually do.
- The loop
- Recruiter conversation (30 min) → Googleyness and Leadership interview (45 min).
- How the decision is made
- Interviewers write structured feedback and scores against rubrics, and people who did not interview you review the whole packet. Google's 2019 careers page described independent hiring committees reading your interview feedback and scores, resume, references and work samples, followed by a senior leader's review and an executive review. Its current page says only that it brings everything together and takes a number of perspectives into account. interviewing.io reports that the committee needs consensus to recommend a hire, that each interviewer also gives an overall recommendation on a seven-point scale from Strong No-Hire to Strong Hire, and that you and a team must both opt in during team matching.
The 5 competencies
In Google’s own framing, where published.
Growing outside your comfort zone
RenamedTaking on work you were not yet good at, seeking feedback, and changing how you work as a result. Google asks how you push yourself to grow outside your comfort zone.
Working with people and teams
RenamedHow you collaborate, help others and handle conflict. Google describes a collaborative culture and asks how you work with peers and cross-functional teams, address conflict and influence teammates.
Emergent leadership
RenamedLeading without the title: taking initiative, mobilising others through communication and decisions, and helping a team succeed when you were not officially the leader. Google's guidance for individual contributors is to look for emergent leadership.
Leading a team
RenamedFor people managers: empowering a team and shaping a long-term vision or strategy. Google's structured-interviewing guide names these as what to look for in managers.
Inside the app, each competency comes with what Google interviewers listen for, the follow-ups they use and their questions, and every story you write is read against them.
The loop, round by round
What actually happens, in order — including rounds this app cannot rehearse.
01
Recruiter conversation
30 min · voiceYou can drill thisAssesses Working with people and teams and Navigating ambiguity.
02
Problem-solving, role-related and coding interviews
45 min · liveNot rehearsable here03
Googleyness and Leadership interview
45 min · voiceYou can drill thisAssesses Navigating ambiguity, Growing outside your comfort zone, Working with people and teams, Emergent leadership and Leading a team.
Levels
Working model, not published by the company. Treat it as a preparation aid, not a promise.
Individual contributor
Intern - student internship (estimated) · L3 - new grad / entry level (estimated) · L4 - early career (estimated) · L5 - senior (estimated) · L6 - staff (estimated) · L7 - senior staff (estimated) · L8 - principal (estimated)
Management
Manager - leads a team (estimated) · Senior Manager - leads managers (estimated) · Director - leads an organisation (estimated)
Inside the app, each level's bar (its scope, ambiguity, influence and impact) sets how your stories and drills are judged.
Roles we prepare you for
Any competency can come up in any loop. Inside the app, your role decides which ones are probed first.
Software Engineer
Software Engineer II, Software Engineer III, Senior Software Engineer, Staff Software Engineer, Senior Staff Software Engineer, Principal Engineer
Engineering Manager
Software Engineering Manager, Senior Software Engineering Manager, Director, Engineering
Product Manager
Associate Product Manager, Product Manager, Senior Product Manager, Group Product Manager
Program Manager
Program Manager, Technical Program Manager
Sales / Account Management
Account Manager, Technical Account Manager, Customer Engineer
Marketing
Product Marketing Manager, Marketing Manager
Practise the Google interview
Google's interview tips call a broad library of examples key, and its 2019 interview page advised writing three different answers for every likely question so the next interviewer hears a different story. Two distinct stories per competency is the floor; many will cover more than one competency.