Process
Two 45-minute interviews were conducted. The interviewer was 15 minutes late and asked questions sporadically. Some questions were rephrased multiple times, making it difficult to follow. The algorithmic questions were easy to provide brute-force solutions for, but I was required to offer more than one solution. The challenging aspect was not knowing which direction to pursue for more optimal solutions.
Questions
How do you select words randomly and proportionally from a word list?
Another question was that there was a class defined as "final". What will happen if I instantiate this class?
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.0Great place to workSoftware Engineer • Former EmployeeFebruary 1, 2021Pros: A very flexible and fun place to work.Cons: No real cons, great job.
- 4.0Not as good as it used to be, but still pretty goodSoftware Engineer • Current EmployeeBengaluru, Karnataka, IndiaApril 28, 2024Pros: Good policies. No other company has them.Cons: Very short-term focused now, curtailing open communication.
- 4.0Good Team, Decent ProjectsSoftware Engineer • Current EmployeeOctober 3, 2021Pros: Good people. Good projects. Good salary as an SDE.Cons: Not very intellectual. Managers do micromanagement.
Google Interview Questions
