Front-end Software Engineer Interview Experience - Mountain View, California
Process
The interview process begins with a recruiter phone call for screening.
This is followed by at least one technical phone call with a Google engineer to solve coding questions.
Lastly, there is an on-site technical interview. This involves solving coding problems on a whiteboard while you explain your solution. Your work should be as close to compilable code as possible, as they take pictures of it.
Questions
I cannot disclose specific questions, but they are your basic technical coding questions. Some are more applicable to the position than others, but all are relevant to software engineering.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Google Front-end Software Engineer role in Mountain View, California.
Success Rate
Google's interview process for their Front-end Software Engineer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Google's Front-end Software Engineer interview process in Mountain View, California.
Google Work Experiences
- 3.0Smart Team, Terrible ManagersSoftware Engineer, Tools and Infrastructure • Former EmployeeMountain View, California, United StatesApril 8, 2023Pros: Smart people, great benefits. You can make a niche for yourself with the right moves.Cons: Terrible managers scattered throughout. No vision. Doesn't know what it wants to be. Ad revenue covers for slackness in the rest of the company.
- 5.0The best company to work forSoftware Engineer • Current EmployeeMountain View, California, United StatesJune 14, 2008Pros: Chance to work with smart people. Perks and benefits.Cons: Long working hours. Rapid growth.
- 5.0Lots of interesting problems and chances to grow if you work at itSite Reliability Engineer • Current EmployeeMountain View, California, United StatesJune 17, 2008Pros: You get to work on some of the biggest clusters in the world on some very hard and interesting problems. The people are generally above average, and you always have to work to make sure you're doing better. For the most part, it's a very strong meritocracy.Cons: You might not get assigned to the groups doing the really cool things. It must be very frustrating to want to do, e.g., large-scale graph algorithms (think maps) and be stuck doing HR programming or JavaScript. Though, after 18 months, you can move to any team you want if they need engineers (and you're performing). The infrastructure is getting complex enough that there is a huge ramp-up time. While that means that it takes a while to launch a project for the first time, if you know what you're doing, you can launch a very scalable project quickly.
Google Interview Questions
