Software Engineer Interview Experience - Mountain View, California
Process
It was a very standard interview, of medium difficulty for Google's standards. All the questions were on expected lines: problem-solving, a lot of coding, and data structure knowledge.
The challenging part was to give more than one solution, pick an efficient one, and then write working code with no logical errors, all within 45 minutes.
Questions
LRU Cache in JavaScript. Queue, Doubly Linked List in JavaScript.
Implement Fibonacci function with caching.
Given a sorted array [2, 4, 4, 4, 8, 9, 9, 11], write a function to give the number of elements in range [3, 10].
Given an n-ary tree containing numbers, find the number of nodes in the longest sequence (do DFS and find the longest sequence not necessarily starting from the root).
Was this helpful?
Interview Statistics
The following metrics were computed from 748 interview experiences for the Google Software Engineer role in Mountain View, California.
Success Rate
Google's interview process for their Software Engineer roles in Mountain View, California is very selective, failing most engineers who go through it.
Experience Rating
Candidates reported having very good feelings for Google's Software Engineer interview process in Mountain View, California.
Google Work Experiences
- 5.0Great Recruiting ProcessSoftware Engineer • Current EmployeeMountain View, California, United StatesDecember 25, 2015Pros: 1. Good procedure 2. Everyone is nice 3. The interviewers are really friendly 4. Flight is very flexibleCons: 1. Not too high salary. 2. Technical interview is very difficult. 3. No LeetCode problems. 4. New problems never seen before.
- 5.0Google SWE 7+ YOESoftware Engineer • Former EmployeeMountain View, California, United StatesJune 6, 2025Pros: Interesting product opportunities on teams. There's a chance for global impact, all the way down to organizational impact, depending on your preference. Free food, great pay, the works. Would recommend.Cons: Competitive promotion culture: You are competing with your peers and sometimes with your TLs, usually over who gets credit for what or who was most to blame if something didn't quite go according to the original plan. Keep an accurate record of the work you've completed and maintain the documentation. It will matter.
- 5.0Had a good timeSoftware Engineer • Former EmployeeMountain View, California, United StatesMarch 22, 2024Pros: Great benefits and work-life balance.Cons: Some of the projects were less than interesting.
Google Interview Questions
