Process
The process began with an initial phone screen with the recruiter, followed by a typical LeetCode DSA problem of medium difficulty.
The interviewer had difficulty explaining the problem and offered to postpone the interview, which I accepted.
I was not allowed to pick my language of choice, so I went with their recommendation of Python.
Questions
DSA - Catch a Pokémon in a box?
Was this helpful?
Interview Statistics
The following metrics were computed from 32 interview experiences for the Google Software Engineer III role in United States.
Success Rate
Google's interview process for their Software Engineer III roles in the United States is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Google's Software Engineer III interview process in United States.
Google Work Experiences
- 5.0Amazing Tech, Great TeamSoftware Engineer III • Former EmployeeZürich, Zürich, SwitzerlandApril 24, 2017Pros: * Amazing technology * Working atmosphere * Colleagues * CompensationCons: It is really hard to find any.
- 5.0Great fun, good learning experienceSoftware Engineer III • Current EmployeeDublin, Dublin, IrelandApril 25, 2014Pros: Perks and friends. You learn all the time.Cons: Bureaucratic, at times not transparent enough.
- 4.0Great place to workSoftware Engineer III • Former EmployeeMountain View, California, United StatesNovember 7, 2016Pros: Most people I worked with were very intelligent, friendly, and respectful. Engineers are well-respected, and the tools and processes are world-class. My programming skill has improved very significantly in the year and a half that I was here.Cons: Although it does a good job of cutting down on bureaucracy, Google is not completely free from some problems that affect large companies. Because there are so many brilliant people fighting for projects, being politically savvy becomes an important skill. Additionally, occasional shake-ups do mean that some projects get canceled.
Google Interview Questions
