Location, tools accessible to SDE's, and pay.
Not much opportunity to be creative.
I had two interviews: 1. An OOP interview 2. An algorithmic interview I did not have to run any code. At the OOP interview, I had to respond to some questions about a design. At the algorithmic interview, every problem was from "Cracking the Coding
One round of timed, easy-level LeetCode problems. One round of interactive "Day in the Life of an Engineer" scenarios with approximately 20 situations and an 8-question Java debugging exercise. The final round featured two separate whiteboard inter
They asked two behavioral questions based on Amazon LP's and one LeetCode medium-hard question. It was very straightforward. They also asked my motivation behind choosing a SWE career and the goals I would want out of it.
I had two interviews: 1. An OOP interview 2. An algorithmic interview I did not have to run any code. At the OOP interview, I had to respond to some questions about a design. At the algorithmic interview, every problem was from "Cracking the Coding
One round of timed, easy-level LeetCode problems. One round of interactive "Day in the Life of an Engineer" scenarios with approximately 20 situations and an 8-question Java debugging exercise. The final round featured two separate whiteboard inter
They asked two behavioral questions based on Amazon LP's and one LeetCode medium-hard question. It was very straightforward. They also asked my motivation behind choosing a SWE career and the goals I would want out of it.