SDE-2 Backend Interview Experience - Toronto, Ontario
February 1, 2022
Positive ExperienceNo Offer
Process
Overall, the experience was good, but the behavior portion was hard to pass. The questions focused on normal data structures and algorithms. Bug-free code was not required, and it felt like LeetCode style. System design was interesting. The interviewer was good to communicate with.
Questions
LeetCode questions like 225 (Topological Sort).
LeetCode questions like 798, 281.
Was this helpful?
Interview Statistics
The following metrics were computed from 1 interview experience for the Amazon SDE-2 Backend role in Toronto, Ontario.
Success Rate
0%
Pass Rate
Amazon's interview process for their SDE-2 Backend roles in Toronto, Ontario is extremely selective, failing the vast majority of engineers.
Experience Rating
Positive100%
Neutral0%
Negative0%
Candidates reported having very good feelings for Amazon's SDE-2 Backend interview process in Toronto, Ontario.
Amazon Work Experiences
3.0
Good Pay, Bad Management
SDE-2 Backend • Current Employee
Toronto, Ontario, Canada
February 27, 2025
Pros: Well-paid until 5 days RTO.
Cons: No promotion and layoffs.
Bad management.
3.0
Fast-paced, competitive environment
SDE-2 Backend • Former Employee
March 24, 2025
Pros: * E2E dev
* Always features to work on
* Pay is competitive
Cons: * Politics
* No downtime, always heads down working
* Pressure from leadership
1.0
Toxic Managers and a Pathetic Tech Stack
SDE-2 Backend • Current Employee
Bengaluru, Karnataka, India
January 13, 2025
Pros: Ownership
Access to infra
Cons: Toxic managers who won't let the team change by providing false negative feedback to other managers. This feedback is not shared with the SDE.
Promotions to SDE3 are not possible, as there are two-digit SDE2s in one team, and they don't offer projects with good scope to create large impact like SDE3.
No hike for the last two years.
Internal build tools are pathetic and take a lot of time to build. Even a small change takes five to ten minutes to build. Apps don't run on Mac; they need to be run on remote machines, and you cannot debug in an IDE. Development of a simple API takes days. This impacts work-life balance a lot.
Internal common applications have bad documentation and almost no support.
- 3.0Good Pay, Bad ManagementSDE-2 Backend • Current EmployeeToronto, Ontario, CanadaFebruary 27, 2025Pros: Well-paid until 5 days RTO.Cons: No promotion and layoffs. Bad management.
- 3.0Fast-paced, competitive environmentSDE-2 Backend • Former EmployeeMarch 24, 2025Pros: * E2E dev * Always features to work on * Pay is competitiveCons: * Politics * No downtime, always heads down working * Pressure from leadership
- 1.0Toxic Managers and a Pathetic Tech StackSDE-2 Backend • Current EmployeeBengaluru, Karnataka, IndiaJanuary 13, 2025Pros: Ownership Access to infraCons: Toxic managers who won't let the team change by providing false negative feedback to other managers. This feedback is not shared with the SDE. Promotions to SDE3 are not possible, as there are two-digit SDE2s in one team, and they don't offer projects with good scope to create large impact like SDE3. No hike for the last two years. Internal build tools are pathetic and take a lot of time to build. Even a small change takes five to ten minutes to build. Apps don't run on Mac; they need to be run on remote machines, and you cannot debug in an IDE. Development of a simple API takes days. This impacts work-life balance a lot. Internal common applications have bad documentation and almost no support.
Amazon Interview Questions
Explore Interview QuestionsTaro 75Google Interview QuestionsMeta Interview QuestionsAmazon Interview QuestionsApple Interview QuestionsNetflix Interview Questions
Explore Interview ExperiencesOpenAI Interview ExperiencesAnthropic Interview ExperiencesPerplexity Interview ExperiencesWindsurf Interview ExperiencesMistral AI Interview Experiences
