amazon logo
Amazon· System Development Engineer (SysDE)

Amazon System Development Engineer (SDE) Interview Experience — 2 YOE (Rejected)

Experience
2 years
Posted
8 May 2025
273 reads

Summary

I was rejected for the System Development Engineer role at Amazon after 2 years of experience. Despite a strong performance in the system design round, my inability to complete a coding question (Generate Parentheses) led to the rejection.

How it went

Amazon System Development Engineer (SysDE) Interview Experience

Company: Amazon
Role: System Development Engineer (SysDE)
Experience: 2 Years
Status: Rejected
Timeline: March 2025


📩 How It Started

I was contacted by an Amazon HR on LinkedIn for the System Development Engineer role. With 2 years of experience in full-stack development (React, .NET Core, MySQL, Elasticsearch), I was excited to explore this opportunity.


📍 Timeline Overview

  • Early March: Online Assessment (OA)
  • Mid March (Week 3): Two Technical Rounds (Back-to-back)

🧪 Online Assessment (OA)

Standard OA questions – mainly string-based. Completed in the first week of March.


🧠 Round 1 (Actually happened second) – Coding + LPs

Format: 1-hour virtual interview
Interviewers: Two (one shadowing)

Structure:
- First 10–15 mins: Leadership Principles discussion
- Next: Two coding questions

Questions:

  1. Similar to: Generate Parentheses
    I struggled with recursion and couldn’t complete it.
  2. Add Two Numbers
    Solved this.

🧠 Round 2 (Actually happened first) – System Design + LPs

Format: 1-hour virtual interview
Interviewers: Two (one shadowing)

Topic: High-Level Design (HLD) of an E-commerce System

What I Covered:

  • Explained CDN, ALB, NGINX, API Gateway, Microservices
  • Core Services: Auth, Product, Cart, Payment, Order, Notification
  • Queues: For async communication (e.g., order → notification)
  • Caching: Memcached with consistent hashing
  • DB: SQL with master-master and multiple read replicas
  • Circuit Breaker: Design for fault isolation

Follow-up Questions:

  • SLA and SLO
  • Business and App metrics
  • How to handle large traffic or a single service failure (Circuit Breaker)
  • Caching strategies and eviction policies
  • Horizontal vs Vertical Scaling
  • SQL vs NoSQL (used SQL for orders/payments; NoSQL for product catalog)

Discussion on Leadership Principles (LPs)

Outcome: Went well. I was confident and clear.


❌ Final Verdict: Rejected

Even though the system design round went well, the coding round performance was not up to the mark.

Takeaway for me: Should focus on DSA.

Questions asked (3)

  1. 01

    Generate Parentheses

    Data Structures & Algorithms

    The problem was similar to generating all combinations of well-formed parentheses. I struggled with recursion and couldn’t complete it.

    Open the problem
  2. 02

    Add Two Numbers

    Data Structures & Algorithms

    A coding question to add two numbers, likely represented as linked lists.

    Open the problem
  3. 03

    High-Level Design of an E-commerce System

    System Design

    High-Level Design (HLD) of an E-commerce System, covering components like CDN, ALB, NGINX, API Gateway, Microservices (Auth, Product, Cart, Payment, Order, Notification), Queues for async communication, Caching (Memcached with consistent hashing), DB (SQL with master-master and multiple read replicas), and Circuit Breaker for fault isolation. Follow-up questions included SLA and SLO, business and app metrics, handling large traffic or single service failure, caching strategies and eviction policies, horizontal vs vertical scaling, and the choice between SQL vs NoSQL.

Know someone preparing? Send it to them:WhatsAppLinkedInX

Interviewed at Amazon recently?

Write up your rounds while you still remember the questions. It helps the next person more than you would think.

Share your experience
Discussion 0

Questions for the author, or how your own interview compared.

Join the discussion

Sign in with Google to comment or ask the author a question.

No comments yet

Be the first to share your thoughts and start the discussion!