Process
I received an email from the recruiter. We set a phone call for a week later. It was a casual talk about my work interests and the interview process. Then, we set a date for a technical interview: a 45-minute phone interview.
On the phone interview, I wrote code on a blank Google Doc shared with the interviewer.
Questions
- Question: Finding the shortest path in a grid with obstacles.
Follow-up question: With a certain number of obstacle eliminations.
https://leetcode.com/problems/shortest-path-in-a-grid-with-obstacles-elimination/
Was this helpful?
Interview Statistics
The following metrics were computed from 31 interview experiences for the Google Software Engineer (Swe II) role in United States.
Success Rate
Google's interview process for their Software Engineer (Swe II) 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 (Swe II) interview process in United States.
Google Work Experiences
- 5.0Good Perks, Lost ImpactSoftware Engineer (Swe II) • Current EmployeeJuly 26, 2024Pros: Generally good perks and work culture.Cons: The company is too large to have an impact.
- 5.0Good company, good work-life balanceSoftware Engineer (Swe II) • Current EmployeeHyderābād, Telangana, IndiaSeptember 3, 2024Pros: Free food and 50% work from home.Cons: Very high competition between people.
- 5.0Great Perks, Bad PoliticsSoftware Engineer (Swe II) • Current EmployeeSan Jose, California, United StatesJanuary 11, 2023Pros: Great benefits, good food, massages.Cons: Too much politics and lots of managers.
Google Interview Questions
