Software Engineer Manager Interview Experience - Warsaw, Masovian Voivodeship
Process
It started with the HR call. HR was very polite and friendly, discussing how much time I needed to prepare for the interview.
After we agreed on the date, there was a first technical interview where I had to show my knowledge in algorithms.
After I passed this interview, HR called me with congratulations and scheduled the next interviews. The second part was much more difficult. It involved interviews with five different people, each lasting 45-60 minutes.
I failed this part. But even after that, HR called me and discussed everything that was wrong and the reasons why I had not passed.
In general, it left a nice impression of the HR team's work.
Questions
There were questions about the managing development team, coding, and algorithms. Two out of five interviews were related to algorithms. The interviewers provided samples from real tasks at Google and asked me to provide my vision on how I would solve them.
One interview was related to coding (graphs).
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Google Software Engineer Manager role in Warsaw, Masovian Voivodeship.
Success Rate
Google's interview process for their Software Engineer Manager roles in Warsaw, Masovian Voivodeship is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having very good feelings for Google's Software Engineer Manager interview process in Warsaw, Masovian Voivodeship.
Google Work Experiences
- 1.0Don't believe the hypeSoftware Engineer Manager • Current EmployeeNovember 2, 2025Pros: Good brand on resume and great benefits for now, although with constant cost-cutting, many perks are disappearing.Cons: This is a very top-down disaster of a company, especially Cloud. There are teams where VPs who came from Oracle are pulling all their past crew and making the culture horrible. This is one of the worst teams I worked for, with unreasonable expectations and pathetic leadership. There are no career opportunities, especially if you're not based in the Bay Area or Seattle. Promos are impossible with ridiculous reasons, and the culture in Cloud is horrible. It's not the same Google once people dreamed to join. It's a disaster.
- 2.0A golden dead endSoftware Engineer Manager • Current EmployeeZürich, SwitzerlandJanuary 17, 2025Pros: Compensation & benefits The Google stamp on your resume Great "rest and vest" opportunities if you know how to be efficient at your job.Cons: Very slow career growth. Close to impossible to innovate and build products iteratively. Performance review frameworks create a culture in which individuals and teams build fences around what they own and promote complex solutions even to trivial problems. There is a big lack of clear leadership who hides behind promoting decisions by consensus and influence. This leads to endless conversations and painfully slow progress from user research to design to implementation. Folks who have been at the company 5y+ (or their whole career) do not know that there is a world outside where better products are built faster and cheaper.
- 5.0Work with the brightest software engineersSoftware Engineer Manager • Current EmployeeKirkland, Washington, United StatesMarch 22, 2024Pros: A very high bar for hiring talent externally means that you get to work with top engineers in the industry.Cons: There are problems, but nothing that can be shared here.
Google Interview Questions
