Process
After a recruiter reached out to me about my applications, I had an online coding assessment. There were 2 questions: one easy and one medium, with 90 minutes to finish them both.
After passing that, I had a phone screening interview where the interviewer asked me a medium programming question.
The final stage was the onsite interview, where I had 4 interviews in a single day. The first interview was a regular behavioral interview, followed by 3 technical coding interviews with medium to hard programming questions.
Questions
What would you do if your coworker took all the credit for a team project?
Was this helpful?
Interview Statistics
The following metrics were computed from 3,820 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.0Tiring but worth the pay and lifestyleSoftware Engineer • Current EmployeeSan Francisco, California, United StatesJune 6, 2023Pros: Great office. Great staff. Fun, challenging work.Cons: Long hours, stress, a competitive environment, and a lack of job security, with everyone being fired.
- 4.0Fun, but getting less soSoftware Engineer • Current EmployeeChicago, Illinois, United StatesMarch 2, 2024Pros: Benefits are amazing. Offices and perks are spectacular. Many office cultures encourage play and relaxation when possible.Cons: Company culture is becoming more traditional and profit-motivated. Did unnecessary layoffs.
- 5.0Great Pay, Smart Colleagues, BureaucracySoftware Engineer • Current EmployeeCalifornia City, California, United StatesJuly 22, 2025Pros: 1. Top-tier Compensation and Benefits 2. Smart, Talented Colleagues 3. Scale and ImpactCons: 1. Large Company Bureaucracy 2. Limited Product Ownership
Google Interview Questions
