Home · Company guides · Google
Google interview process and questions
Google interviews are structured: each interviewer covers one area and writes up evidence, and a separate group reviews the whole packet before an offer. For engineering roles, coding carries the most weight; for every role, how you think out loud matters as much as the final answer.
How the interview usually runs
- Recruiter call about your background, the role and timing.
- One or two technical or role-specific screens over video, often with a shared document for coding.
- A final round of about four to five interviews: coding or role skills, system design for experienced engineers, and a "Googleyness and leadership" interview.
- A hiring committee reviews the interviewers' notes, then team matching and the offer.
Rounds differ by team, level and country, so ask your recruiter what yours will cover.
What Google looks for
- General cognitive ability. How you break down an open problem and reason through it.
- Role-related knowledge. Depth in the skills the job needs.
- Googleyness. Comfort with ambiguity, collaboration and doing the right thing.
- Leadership. Stepping up and helping others, at any level.
Common Google interview questions, and how to answer them
1. Given an array of integers, find two numbers that add up to a target.
Clarify the input, say the brute force first, then improve it with a hash map. Talk through edge cases and give the time and space cost.
2. Design a service like Google Drive's file sharing.
Scope it, sketch the API and storage, then go deep on one hard part such as permissions or sync, and say what breaks first at scale.
3. Tell me about a time you had to make a decision without all the data.
Use STAR. Show how you limited the risk, what signal you looked for, and what you learned.
4. Tell me about a time you disagreed with a teammate.
Show you listened, used evidence, and kept the relationship. End with the outcome.
5. How would you improve a Google product you use?
Pick one real user problem, size it, propose a small change and how you'd measure it.
6. What's a project you'd do differently now?
Be specific about the mistake and the change in how you work since.
How to prepare
- Practise coding while talking, in a plain document without autocomplete.
- Prepare five stories that show ambiguity, conflict, failure, leadership and impact.
- Ask the recruiter which areas your interviews will cover; they usually tell you.
- Set up a session in Ghostpilot with Google, the role and the job post, then run a mock interview out loud and read the feedback on every answer.
Practise for Google out loud
Mock interviews with a score and feedback on every answer, and company questions that candidates reported. Free: 3 mock interviews a month, no card needed.
Frequently asked questions
How long does the Google interview process take?
Often four to eight weeks from the first call to an offer, longer when team matching takes time. Ask your recruiter for the expected timeline.
Which programming language should I use?
Use the one you know best. Interviewers care about clear reasoning and correct, readable code more than the language.
Based on what Google publishes about its hiring and what candidates commonly report. Processes change and differ by team and country, so check with your recruiter. Google is a trademark of its owner; Ghostpilot is not affiliated with or endorsed by Google.
More company guides
Zoom, Google Meet, Microsoft Teams, Webex, Slack, FaceTime, Chrome and Visual Studio Code are trademarks of their owners. Ghostpilot is not affiliated with or endorsed by them.