Great work environment, few interesting projects
Great work environment, few interesting projects
- Amazing benefits.
- Highly talented people.
- Friendly work environment, friendly management.
- Company strives to improve itself and acts on internal criticism.
- Accessibility to awesome technologies and insider information.
- Most projects aren't exciting.
- Lots of technical debt and bureaucracy.
- Your performance is largely valued on how well you write about it, not on it actually being great.
- Hard to transfer teams if your performance doesn't exceed expectations.
- Internal work tools are dated, cumbersome, and lacking compared to those in the industry.
- Mixed messages when it comes to work-life balance: management stresses the importance of work-life balance and gives us the freedom to put life first, but in practice, this generally means your performance can worsen compared to your peers, which influences your career path there.
- HR responds slowly for most bureaucratic requests.
- Fix performance.
- Make internal transfers easier for employees (e.g., by not enabling performance to influence the process).
- Simplify communication with HR: make it faster (instead of ~5 days for responses) and enable employees to contact local HR for bureaucratic requests (instead of having to contact EMEA HR, which doesn't understand the employee's local language).
Additional Ratings
Was this helpful?
Google Interview Questions
Google Interview Experiences
Software Engineer II
Phone call with a recruiter followed by coding interviews. I did not make it past that stage. The question I received was quite difficult, and I did come up with a non-optimal algorithm, but that was not enough.
Software Engineer II
I applied online. The technical interview itself went fine. I completed the DSA problem, explained my approach with an example, and provided the solution. However, the interviewer’s behavior was disappointing. They did not respond to my initial gree
Software Engineer II
I applied online. The process took three months. - One preliminary coding interview - Three main loop coding rounds - One behavioural round It contained array, DFS, and light design questions with follow-ups. The behavioural round was almost leanin
Software Engineer II
London, EnglandAugust 1, 2024Phone call with a recruiter followed by coding interviews. I did not make it past that stage. The question I received was quite difficult, and I did come up with a non-optimal algorithm, but that was not enough.
Software Engineer II
October 6, 2026I applied online. The technical interview itself went fine. I completed the DSA problem, explained my approach with an example, and provided the solution. However, the interviewer’s behavior was disappointing. They did not respond to my initial gree
Software Engineer II
Zürich, Zürich, SwitzerlandJanuary 11, 2026I applied online. The process took three months. - One preliminary coding interview - Three main loop coding rounds - One behavioural round It contained array, DFS, and light design questions with follow-ups. The behavioural round was almost leanin
