SDE-2 at Amazon

How it went

What they would tell you

How to prepare

Their background

Round by round

1. 1

   Coding60 min

   • Interviewers: Two SDE-3 (one main, one observing)
   • Started with LPs, then DSA.
   • Subarray Sum Equals K
   • Maximum Subarray Sum After One Operation
2. 2

   LLD60 min

   Same It started with Leadership Principle questions. I was given a Tic-Tac-Toe design problem. The challenge was to think through the entire system, from defining entities to understanding how the game logic would work and end. After discussing, game states like wins, draws, and edge cases. I drew a UML class diagram to explain my design.

3. 3

   HLD60 min

   During my interview, I was tasked with designing an Event Booking System. The system should allow users to book tickets for various events like concerts, sports games, or conferences, while also providing an admin interface to manage these events. The first step was to thoroughly understand the requirements:

   • Core Features:

   • User-side: Browse events, book tickets, cancel bookings, and view booking history.

   • Admin-side: Add, edit, or delete events, view all bookings, and manage event capacity.

   • Non-Functional Requirements: The system should be scalable, secure, and highly available. I divided the system into core functional modules:

   • User-side:

   • View Events: Users can browse available events with details like date, location, and available tickets.

   • Book Tickets: Users select an event, choose their preferred seats, make a payment, and receive a booking confirmation.

   • Cancel Booking: Users can cancel their booking and receive a refund (if within the allowed time).

   • Booking History: Users can see their previous bookings.

   • Admin-side:

   • Event Management: Admins can add, edit, and delete events.

   • Booking Management: Admins can view all bookings for an event and manage capacities. The system needed both frontend and backend components:

   • Frontend: A user-friendly interface where users can view events, make bookings, and interact with the admin panel.

   • Backend:

   • API: A REST API to handle user actions (event browsing, booking, cancellation) and admin actions (event management).

   • Database: A relational database to store users, events, and bookings.

   • Tables: Users (user_id, name, email), Events (event_id, name, description, date, price), Bookings (booking_id, user_id, event_id, seat_number).

4. 4

   Bar Raiser60 min

   Leadership Principles, followed by coding problems The first problem was Paint Fence (a dynamic programming problem) and the second was the Coin Path problem.

   • Paint Fence
   • Coin Path
5. 5

   Outcome10 min

   After completing all the rounds, I was contacted by HR the same day for the final offer discussion. The HR team asked me to confirm my notice period, current CTC, and preferred location. The next day, I received an offer for the SDE-2 role.

What came up