Process
Initial phone screen went well, followed by a technical phone screen. The technical phone screen involved discussion of past work/research experience, followed by a coding portion. Discussions went well. The coding problem was actually quite easy, but time got the best of me, and I ended up giving a working but less than elegant solution. I received feedback in days, saying there were many positives, but they ended up passing on me.
Questions
Simple algorithm design
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
- 4.0Good Growth, But OverworkedSoftware Engineer • Current EmployeeWarsaw, Masovian Voivodeship, PolandSeptember 25, 2023Pros: Benefits, growth, easy teams changing.Cons: Overusing people, chasing the carrot.
- 5.0Good Company, Slow PaceSoftware Engineer • Current EmployeeBengaluru, Karnataka, IndiaNovember 27, 2021Pros: This is a good company to work for.Cons: There are no cons, just that things move slowly.
- 5.0Advanced Tools, Corporate VibeSoftware Engineer • Current EmployeeZürich, SwitzerlandFebruary 20, 2023Pros: Tools and products are very advanced. Work-life balance and benefits are also important considerations.Cons: Very corporate, no startup vibe in most of the teams. Internal stack of tools and services. Some knowledge hard to apply later.
Google Interview Questions
