Process
I was connected to a recruiter through a friend.
The process included a phone interview followed by a technical phone screen.
The position I applied for was a front-end role, so I should have anticipated questions about DOM manipulation using vanilla JavaScript.
I received a rejection call a few days later.
Oh well, overall it was a great and streamlined experience.
Questions
In-depth DOM manipulation using vanilla JS
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.0Smart People, No ConsSoftware Engineer • Current EmployeeJune 3, 2018Pros: Work with great, smart people.Cons: No cons that I can think of.
- 1.0A terrible company to work forSoftware Engineer • Current EmployeeMountain View, California, United StatesDecember 12, 2023Pros: It can be hard for people to tell if you are working, because the codebase is so bad that it can take ages to do the most basic things. On the other hand, a lot of people work overtime to try and make up for how slow things go.Cons: Filled with corporate politics, promotions are stalled by default. All the tools you use are in-house and ancient, so the experience you gain is mostly worthless. HR is nonexistent and will never do anything, even in serious situations.
- 4.0Very good peopleSoftware Engineer • Current EmployeeNew York, New York, United StatesOctober 14, 2023Pros: Very good and fast in communication.Cons: This is nothing bad.
Google Interview Questions
