Process
I was asked to complete a survey and a coding sample.
In the survey, there were some behavioral questions, such as what you would do in certain scenarios.
In the coding sample, there were two coding questions.
Questions
Given a string that represents time like "15:31", find the next time formed by the numbers in the string (a number can be used more than once). For "15:31", the answer should be "15:33".
Given an array a[] and an integer k, a[i] means a flower at position a[i] will blossom on day i. Find the first day that there are k slots between two blooming flowers.
Was this helpful?
Interview Statistics
The following metrics were computed from 3,728 interview experiences for the Google Software Engineer role in United States.
Success Rate
Google's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Google's Software Engineer interview process in United States.
Google Work Experiences
- 3.0Used to be great, clearly slippingSoftware Engineer • Current EmployeeNew York, New York, United StatesJanuary 21, 2021Pros: Smart colleagues. Amazing engineering infrastructure in place.Cons: Exponentially increasing bureaucracy to basic tasks, like creating design docs. Re-orgs come without warning and seemingly without reason. Projects are shut down because some exec didn't like what they saw in a slide deck. The company is increasingly corporate, focused on profits today instead of long-term plans.
- 3.0Good Balance, High TurnoverSoftware Engineer • Current EmployeeSan Francisco, California, United StatesDecember 13, 2023Pros: Great work-life balance and food.Cons: Lots of turnover and firing.
- 5.0Fun Workspace, Great PlaceSoftware Engineer • Current EmployeeNew Delhi, Delhi, IndiaJanuary 28, 2023Pros: Great place to work. Best workspace.Cons: None, as such, is a place that is really fun.
Google Interview Questions
