Software Engineer Interview Experience - Toronto, Ontario
Process
The interview included two simple LeetCode problems, one hard LeetCode problem, some object-oriented programming questions, and two behavioral questions.
For the behavioral part, they asked me to share my top three outcomes or achievements. They also asked me to talk in detail about my most recent project, including challenges I faced, how I approached them, and what the final results were.
Questions
For the behavioral part, they asked me to share my top three outcomes or achievements.
Was this helpful?
Interview Statistics
The following metrics were computed from 26 interview experiences for the Google Software Engineer role in Toronto, Ontario.
Success Rate
Google's interview process for their Software Engineer roles in Toronto, Ontario 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 Toronto, Ontario.
Google Work Experiences
- 3.0Good People, Politics Hamper ProgressSoftware Engineer • Former EmployeeToronto, Ontario, CanadaSeptember 20, 2025Pros: - Great people - Good money - Good infraCons: - Corp politics - Overachieving, over-engineering cool things
- 4.0Good Pay, Growth, Slow PromotionSoftware Engineer • Current EmployeeToronto, Ontario, CanadaAugust 21, 2025Pros: High pay, good culture, continue to grow.Cons: Slow for promotion, many untransferable skills.
- 4.0Great place to learn and grow, but sometimes feels too big to move fastSoftware Engineer • Former EmployeeToronto, Ontario, CanadaAugust 20, 2025Pros: Brilliant and collaborative coworkers – you’re constantly learning from top talent. Access to cutting-edge technology and infrastructure that few other companies can match. Strong focus on work-life balance with generous benefits, wellness programs, and flexible work arrangements. Open culture that encourages idea-sharing and innovation. Career mobility – lots of opportunities to switch teams and explore different domains.Cons: Decision-making can be slow due to the size and multiple layers of approval. Some projects get canceled suddenly, which can be discouraging after months of work. Internal competition for promotions is tough, and the process feels bureaucratic at times. Not all teams enjoy the same level of support and resources – your experience depends heavily on your manager and org.
Google Interview Questions
