Process
I had an initial screening with a recruiter, all done via email.
Had two weeks to prepare for the developer technical interview. I was given one question in JS about traversing objects. I had spent time preparing for a lot of algorithms and data structures and was a little caught off guard with the simplicity of the question.
Questions
Given an object, how would you traverse the object to find a specific property that is nested 4-5 layers deep within the object?
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
- 5.0Everything Is Too GoodSoftware Engineer • Current EmployeeBangiriposi, Odisha, IndiaSeptember 23, 2023Pros: The pro is that everything about it is too good.Cons: There are no cons as such.
- 5.0Great Company, Slow PromosSoftware Engineer • Current EmployeeNew York, New York, United StatesAugust 29, 2020Pros: Great company to work at.Cons: Slow promo cycle in career.
- 4.0Great opportunity, but be wary of the hypeSoftware Engineer • Current EmployeeMarch 13, 2023Pros: Top-notch engineering. Just being around other skilled engineers and seeing how things are done causes you to become more skilled. Friendly people. Lots of small perks.Cons: Inconsistent product direction. There's a lot of internal joking about the short time between teams being shuffled, and this means it's difficult to see projects through to completion. Senior leadership seems more focused on cost-cutting than effective long-term vision. There's lots of talk about respecting each other, but when the chips are down, leadership does not follow through on that.
Google Interview Questions
