4 rounds - each with 2-3 LPs
I recently completed a four-round interview loop that tested both my technical skills and alignment with core leadership principles. The process included one round each of system design and low-level design (LLD/API design), along with two LeetCode-style data structure and algorithm rounds.
In the system design round, I was asked to architect a scalable solution for a real-world problem, focusing on components like API gateways, data storage, caching, and event-driven processing. The LLD round focused more on writing clean, extensible class designs using OOP principles.
For the coding rounds, I was given medium-to-hard level problems covering arrays, graphs, recursion, and dynamic programming—emphasis was equally placed on problem-solving and clear communication.
What stood out to me throughout was how consistently leadership principles were evaluated in every round. It wasn’t enough to write correct code or sketch a solid design—they wanted to see if I could think big, dive deep into details, simplify where needed, and deliver results under pressure.
Even in the coding rounds, I was asked about trade-offs, edge cases, and testing strategy. Preparing structured STAR-format stories really helped in weaving leadership principles into technical conversations.
If you're preparing for a similar process, I'd strongly recommend balancing coding prep with clear communication and behavioral readiness.
The following metrics were computed from 10 interview experiences for the Amazon Software Development Engineer (SDE) II role in New York, New York.
Amazon's interview process for their Software Development Engineer (SDE) II roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Amazon's Software Development Engineer (SDE) II interview process in New York, New York.