How Google interviews
Start with the reported process for your role, then use our practice rounds to rehearse the skills it tests. Follow your recruiter’s instructions for your team and location.
- Software Engineer
- Mid-level · 4 practice rounds · 2 h 55 min of practice
- Product Manager
- Mid-level · 4 practice rounds · 2 h 40 min of practice
- STEP Intern
- Intern (first- and second-year students) · 3 practice rounds · 1 h 45 min of practice
- UX Designer
- Mid-level · 4 practice rounds · 2 h 40 min of practice
What Google says about its interviews
Google's official portfolio guidance asks for three to five case studies showing end-to-end process, role, impact, collaboration, and design rationale. Google UX design portfolio tips
Google's virtual interview guide explicitly anticipates diagramming for some UX interviews. Google virtual interviews candidate guide
Google Software Engineer interview
Google calls the L4 role Software Engineer III. Reports point to a coding phone screen, then about two to four coding rounds at LeetCode-medium level, often graphs and dynamic programming. A Googleyness behavioral round appears in many reports. Some reports add a system design round and others have none, so practice one at moderate depth.
Our 4 practice rounds
Coding phone screen
Check that you can solve one medium data structures and algorithms problem with clear reasoning and correct code.
Practice focus: Graph traversal or shortest-path problem on a grid or network. Dynamic programming problem with a clear state definition. Array or string problem needing a hash map or two pointers.
Illustrative practice follow-ups: “Interviewer changes a constraint and asks how the solution and its complexity change.”
Practice this roundOnsite coding rounds
Check consistent problem solving on medium-to-hard problems. Check that you pick a good algorithm, handle edge cases, and respond to follow-ups.
Practice focus: Graph problem with a twist such as weights, cycles, or multiple sources. Dynamic programming problem needing a state and a transition. Implementation task with a small design discussion about data structures.
Illustrative practice follow-ups: “Interviewer asks for a better complexity or a changed input shape after the first working answer.”
Practice this roundSystem design discussion
Check moderate-depth design skill for L4: clear requirements, a sound data model and API, and tradeoff reasoning. This round may not exist in every loop.
Practice focus: Design a billing or metering service with correctness needs. Design a backend service with an API, storage, and moderate scale. Discuss a design, then implement one key function.
Illustrative practice follow-ups: “Interviewer increases load or asks what breaks first and how you would detect it.”
Practice this roundGoogleyness and leadership interview
Learn how you work with others, handle conflict and failure, and learn from them. Look for specific stories with clear personal actions and results.
Practice focus: Time a colleague's working style blocked your progress. Time you failed or made a mistake and what changed. Time you worked through ambiguity or disagreement on a team.
Illustrative practice follow-ups: “Interviewer asks what you would do differently and how the other person saw it.”
Practice this roundGoogle Software Engineer interview questions
- Design a system that bills cars that use a tolled highway. Candidate report
- Describe a time a colleague's working style blocked your work (STAR style). Candidate report
What candidates and sources report
- Google uses the title Software Engineer III for the role that matches L4. Many postings use this title across Cloud, Workspace, Full Stack, Infrastructure, and Backend teams. Google
- A Software Engineer III Dataform posting asks for a bachelor's degree or equivalent experience, plus 2 years of software development (1 year with an advanced degree). Article
- Google states that using AI during a virtual interview leads to disqualification. Google
- A Googleyness and Leadership round with behavioral questions appears in several reports and guides. Themes are conflict and failure. Article
How to prepare
- Practice medium graph and dynamic programming problems: Solve timed problems in a plain editor. Explain approach, write code, then dry-run by hand. State complexity each time.
- Practice one moderate system design: Pick a billing or backend service. Define requirements, API, data model, and one failure case in 45 minutes.
- Prepare four behavioral stories: Write stories on conflict, failure, ambiguity, and teamwork. Include your actions, a result, and a lesson. Rehearse each in three minutes.
Mistakes to avoid
- Do not start coding before the interviewer agrees with your approach.
- Do not stay silent when stuck. Say what you tried.
- Do not memorize solutions. Interviewers change the problem to test real reasoning.
- Do not ignore a hint. Use it and say how it changes your plan.
- Do not list many technologies without saying why each one fits.
Questions to ask your interviewers
- How many coding rounds does the L4 loop for this team include, and how long is each one?
- Does this loop include a separate system design round for Software Engineer III?
- Will my interviews run virtually, in person, or both?
- When does team matching happen compared with hiring committee review for this role?
- Which programming languages may I use in the coding rounds?
Google Product Manager interview
Prepare for product vision and design, analytical judgment, execution under technical constraints, and Googleyness and leadership. Current firsthand accounts agree on these signal families but do not establish one universal stage order or duration. At the mid-level bar, drive an ambiguous problem from user choice to measurable decision, expose second-order effects, and make engineering and stakeholder trade-offs explicit.
Our 4 practice rounds
Product vision and design
Learn whether the candidate can choose a user, frame an important problem, set a direction, and defend a coherent product concept.
Practice focus: An ambiguous product vision problem spanning immediate value and a multi-year direction.
Illustrative practice follow-ups: “Why that user first, and who does this direction leave out?” “What would you ship in the first year, and how would it tell you the longer-term direction is right?” “What would make you switch to the concept you rejected?”
Practice this roundAnalytical and metrics judgment
Learn whether the candidate can define success, diagnose a metric movement, and choose an evidence-backed action under incomplete information.
Practice focus: A product metric diagnosis with segmentation, hypotheses, and decision thresholds.
Illustrative practice follow-ups: “Before we look for causes: exactly which users, events, and time window does this metric count?” “Which check would you run first, and how would each possible result change your next step?” “The metric recovers but a counter-metric drops. Do you keep the change?”
Practice this roundTechnical product execution
Learn whether the candidate can turn product intent into a shippable plan while reasoning credibly with engineering about constraints, risk, and scope.
Practice focus: A roadmap and launch decision constrained by latency, privacy, reliability, or platform dependencies.
Illustrative practice follow-ups: “Engineering says the latency target can’t be met by launch. What do you cut, and what do you keep?” “What signal would stop the rollout, and who makes that call?” “How would you explain this trade-off to a leader who has two minutes?”
Practice this roundGoogleyness and leadership
Learn how the candidate leads through ambiguity, seeks perspectives, handles disagreement, and updates decisions after learning that an assumption was wrong.
Practice focus: Past examples of influence without authority, ambiguity, feedback, and inclusive decision making.
Illustrative practice follow-ups: “What was the strongest argument against your position, as the other person would put it?” “Which of your assumptions turned out to be wrong, and what did you change afterward?” “How did you move the work forward before anyone gave you the authority to decide?”
Practice this roundGoogle Product Manager interview questions
- Analyze how people use Chrome, why it matters, and how it could be improved. Candidate report
- Design a self-driving electric bus and defend the product choices. Candidate report
What candidates and sources report
- A mid-level Google PM posting, retrieved September 6, 2026 and no longer listed on October 11, 2026, emphasized user journeys, strategy, cross-functional delivery, launches, experiments, and success metrics. Job posting
- A recent former-Google account describes product design, analytical thinking, technical depth, and behavioral or leadership as core PM interview components. Candidate report
How to prepare
- Practice product vision and design: Run one 40-minute rep using an ambiguous product vision problem spanning immediate value and a multi-year direction. Use “Frame the user problem” and “Defend the strategy” as checkpoints; repeat after one changed constraint.
- Practice analytical and metrics judgment: Run one 40-minute rep using a product metric diagnosis with segmentation, hypotheses, and decision thresholds. Use “Define the metric precisely” and “Make a measured decision” as checkpoints; repeat after one changed constraint.
- Practice technical product execution: Run one 40-minute rep using a roadmap and launch decision constrained by latency, privacy, reliability, or platform dependencies. Use “Break down delivery risk” and “Align cross-functional partners” as checkpoints; repeat after one changed constraint.
- Practice googleyness and leadership: Run one 40-minute rep using past examples of influence without authority, ambiguity, feedback, and inclusive decision making. Use “Own an ambiguous outcome” and “Update after learning” as checkpoints; repeat after one changed constraint.
Mistakes to avoid
- Do not substitute a memorized framework for the supplied facts.
- Do not hide personal decisions behind vague team language.
- Do not claim certainty beyond the evidence available.
Questions to ask your interviewers
- Which PM signal is the hiring team most concerned about for this role?
- How does this team divide product strategy and execution ownership between PM, UX, and engineering?
- What distinguishes strong mid-level scope from senior PM scope on this team?
Google STEP Intern interview
Google STEP starts with a 10–15-minute recruiter or human-resources screen, followed by two 45-minute coding interviews. Expect data-structures and algorithms problems coded in a shared document, with your reasoning explained as you go, complexity, edge cases and follow-up changes to the problem.
Our 3 practice rounds
Recruiter or HR Screen
Confirm communication, project ownership, academic context, and foundational programming readiness.
Practice focus: Self-introduction and study path. Project contribution and result. Programming language, skills, and preparation.
Illustrative practice follow-ups: “Which part of that project did you decide or build yourself?”
Practice this roundTechnical Coding Interview 1
Assess foundational data-structures and algorithms reasoning, implementation, and optimization during a 45-minute coding session.
Practice focus: Array, sliding-window, or prefix-sum variants. Hash-map or graph warm-ups. Follow-up optimization or constraint change.
Illustrative practice follow-ups: “Request a lower-complexity approach or a changed input constraint.” “Ask for boundary cases and a manual trace through the code.”
Practice this roundTechnical Coding Interview 2
Assess a second algorithmic approach across reported recursion, graph, binary-search, heap, or abstraction patterns.
Practice focus: Recursive tree or folder traversal. Graph search with memoization. Binary search or heap optimization.
Illustrative practice follow-ups: “Ask how the approach changes with larger input or repeated subproblems.” “Probe unfinished code, base cases, and complexity when time is limited.”
Practice this roundGoogle STEP Intern interview questions
- Solve a graph problem that requires depth-first search with memoization. Candidate report
- Solve a prefix-sum problem. Candidate report
- Solve two data structures and algorithms problems within 45 minutes. Candidate report
- Solve an array-based problem with variations after the base version. Candidate report
- Solve a binary-search problem. Candidate report
What candidates and sources report
- Multiple 2025 STEP candidate reports describe a recruiter or human-resources screen followed by two technical interviews. Candidate report
- Several exact STEP candidates reported two 45-minute technical interviews. Candidate report
- Two exact STEP reports state that both technical interviews were eliminatory. Candidate report
- Exact STEP candidates reported coding in a shared Google Docs-like document during technical interviews. Candidate report
- Exact STEP reports describe data structures and algorithms coding with follow-up changes or optimization requests. Candidate report
How to prepare
- Prepare concise screen stories: Prepare brief examples about study, projects, personal contribution, programming language, academic context, and recent preparation.
Mistakes to avoid
- Do not give a long chronological biography.
- Do not describe group projects without separating personal work.
- Do not claim skills without a specific example.
- Do not code before stating inputs, outputs, and constraints.
- Do not hide complexity or edge cases until prompted.
Questions to ask your interviewers
- Will both technical rounds use a shared Google document or another coding editor?
- Are the two technical rounds each 45 minutes in my location and current cycle?
- Does the current process include a preparation session before technical interviews?
Google UX Designer interview
Prepare a concise portfolio narrative, a live end-to-end design challenge, craft critique, and collaboration examples. Google’s current mid-level interaction-design postings emphasize user-centered methods, flows, prototypes, design systems, experimentation, and cross-functional work. Candidate evidence supports portfolio and challenge formats, but much of the detailed public reporting is internship-level, so confirm the exact mid-level schedule with the recruiter.
Our 4 practice rounds
Portfolio narrative
Learn whether the candidate can explain an end-to-end design decision, their own contribution, collaboration, iteration, and measured outcome.
Practice focus: A verbal portfolio walkthrough of one complex shipped project and one sharply different project.
Practice this roundLive product design challenge
Learn whether the candidate can explore an ambiguous UX problem, map a coherent flow, test assumptions, and iterate under critique.
Practice focus: A whiteboard challenge requiring user choice, journey mapping, key states, and a changed constraint.
Practice this roundInteraction craft and critique
Learn whether the candidate can diagnose an interaction, apply hierarchy and system patterns, and defend detailed choices across states and accessibility needs.
Practice focus: A product-flow critique covering hierarchy, interaction states, accessibility, and design-system consistency.
Practice this roundDesign collaboration and influence
Learn how the candidate uses research, handles disagreement, raises the craft bar, and gets quality work shipped through cross-functional constraints.
Practice focus: Past examples of research-driven change, engineering negotiation, critique, and design-system stewardship.
Practice this roundGoogle UX Designer interview questions
- Present case studies that make the user problem, end-to-end process, personal role, collaboration, solution, and impact clear. Candidate report
- Complete a live design challenge during one of two 45-minute interviews; the candidate did not disclose the scenario. Candidate report
What candidates and sources report
- A current mid-level Interaction Designer posting requires a portfolio and emphasizes user-centered design, cross-functional collaboration, prototypes, and design systems. Job posting
How to prepare
- Practice portfolio narrative: Run one 40-minute rep using a verbal portfolio walkthrough of one complex shipped project and one sharply different project. Use “Frame the design problem” and “Demonstrate design impact” as checkpoints; repeat after one changed constraint.
- Practice live product design challenge: Run one 40-minute rep using a whiteboard challenge requiring user choice, journey mapping, key states, and a changed constraint. Use “Choose the design scope” and “Evolve the flow” as checkpoints; repeat after one changed constraint.
- Practice interaction craft and critique: Run one 40-minute rep using a product-flow critique covering hierarchy, interaction states, accessibility, and design-system consistency. Use “Diagnose the interaction” and “Give actionable critique” as checkpoints; repeat after one changed constraint.
- Practice design collaboration and influence: Run one 40-minute rep using past examples of research-driven change, engineering negotiation, critique, and design-system stewardship. Use “Navigate design disagreement” and “Learn from compromise” as checkpoints; repeat after one changed constraint.
Mistakes to avoid
- Do not substitute a memorized framework for the supplied facts.
- Do not hide personal decisions behind vague team language.
- Do not claim certainty beyond the evidence available.
Questions to ask your interviewers
- Which project should the portfolio walkthrough prioritize for this team?
- Will the loop include live diagramming, critique, or another functional exercise?
- How does this team evaluate mid-level craft versus design leadership?
Sources
Latest catalogue research: . Practice exercises and follow-ups are our own; they are not confidential interview questions.
- Candidate Guide: Guidelines for virtual interviews at Google — Google
- Google Interview E9079 RVW105029996 — Candidate report
- Google SWE III Onsite Experience and Team Matching Timeline — Article
- google software engineer interview 597223 — Candidate report
- Show Googleyness at Google SWE Interviews: Sample Questions & Tips — Independent guide
- Software Engineer III, Google Cloud — Article
- Software Engineer III, Workspace — Article
- Software Engineer III, Full Stack — Article
- Software Engineer III, Google Distributed Cloud — Article
- 72088214524830406 software engineer iii — Google
- 130140910200464070 software engineer iii — Google
- Google Careers: Product Manager, Googler Experience — Job posting (no longer listed on October 11, 2026)
- Google PM interview experience discussion — Candidate report
- Google STEP Internship Interview Experience (India, 2025) — Candidate report
- Looking Back: My Google STEP 2025 Interview Experience 💔➡️🚀 — Candidate report
- Google STEP Intern '25: My Interview Experience and Story — Candidate report
- My Google STEP Internship Interview Experience — Candidate report
- Reflecting on My Google STEP internship interview Journey — Candidate report
- My Google STEP Journey + Tips for First-Timers — Candidate report
- Google UX design portfolio tips — Google
- Google Careers: Interaction Designer, Sales Platform — Job posting
Independent preparation using Google as a practice target. Not affiliated with, endorsed by, or sponsored by Google.