🎯 Product
Google interview
Test Engineer / SWE in Test
Interview rounds
- 1Recruiter screen
- 2Coding rounds (LeetCode easy–medium, e.g. graph paths)
- 3Test design / automation round
- 4Behavioural (Googleyness)
What they focus on
- Algorithms with complexity
- Test tooling that lets developers test their own code
- Black-box vs white-box testing
- Comparing automation frameworks
💡 Tip: Test Engineers at Google write tools, not manual test cases. Show that you think like a developer who cares about testability.
Practice on a similar app
Apps on this site from the same business domain — write your automation against them before the interview.
Practice questions for Google
Filter by your experience, and pick a language, automation tool or database for theory and coding. Topics reported for Google come first; the “asked in most interviews” lists are general questions worth preparing for any company. Full question bank →
Reported for Google: Framework & CI. Other topics are here too — what you get asked depends on the team, so check the job description.
Theory
20 questions
Asked in most interviews · 27
27 questions
🤖 Emerging — increasingly asked (AI & LLM) · 24
AI-testing topics are showing up in more QA interviews, but weren't specifically reported for Google. Worth preparing if the role mentions AI.
24 questions
Coding
5 questions
Asked in most interviews · 14
14 questions
🤖 Emerging — increasingly asked (AI & LLM) · 9
AI-testing topics are showing up in more QA interviews, but weren't specifically reported for Google. Worth preparing if the role mentions AI.
9 questions
Behavioural & situational
6 questions
Asked in most interviews · 25
25 questions
🤖 Emerging — increasingly asked (AI & LLM) · 7
AI-testing topics are showing up in more QA interviews, but weren't specifically reported for Google. Worth preparing if the role mentions AI.
7 questions
Sources
- Glassdoor — Google Test Engineer
- Blind — Google Test Engineer preparation
- Dataford — Google QA engineer guide (AI evaluation questions)
Summarised in our own words; processes change and vary by team, role and location.
🤝 Interviewed at Google? Share your experience →