← Amplitude Interview Insights

Amplitude·Software Engineer·Onsite - System Design / Architecture·Intermediate

IntermediatePrefer not to say
Mar 2026

Summary

System design round at Amplitude for a software engineering role. The prompt was building a shared to-do list app, which sounds simple enough until you're staring at a blank whiteboard trying to remember how WebSockets work under pressure.

Questions Asked (1)

Q1

Design an online application for sharing to-do lists with others. List the API endpoints and define a database schema that supports real-time updates.

System DesignAPI & IntegrationsData Modeling
Author's notes

I started with the data model and that was probably the right call.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements (e.g., number of users, real-time expectations, sharing permissions) and then outline a high-level architecture. Focus on the API design and database schema, explaining how they support real-time updates via WebSockets or similar technologies. Conclude by discussing trade-offs and scalability considerations.

Pro tip: Emphasize idempotency and conflict resolution in real-time updates, as these are critical for a collaborative to-do list app. Also, mention how you would handle offline support and eventual consistency, showing awareness of real-world challenges.

1. Clarify Requirements

Ask questions to understand scale, real-time needs, sharing permissions, and offline support. This ensures your design meets the actual needs.

2. High-Level Architecture

Sketch the components: clients, API gateway, application servers, database, and real-time service (e.g., WebSocket server). Explain how they interact.

3. API Design

Define RESTful endpoints for CRUD operations on lists and items, plus endpoints for sharing and real-time subscriptions. Consider using WebSockets for real-time updates.

4. Database Schema

Design tables for users, lists, items, and permissions. Include fields for versioning or timestamps to support conflict resolution and real-time sync.

5. Real-Time Mechanism

Explain how updates propagate: e.g., using WebSockets, pub/sub, or change data capture. Discuss how clients receive updates and handle conflicts.

Key Points to Mention

  • RESTful API endpoints for lists and items (GET, POST, PUT, DELETE)
  • WebSocket or Server-Sent Events for real-time updates
  • Database schema with users, lists, items, and permissions tables
  • Use of timestamps or version numbers for conflict resolution
  • Sharing model: owner, collaborators, and access control
  • Scalability considerations: sharding, caching, and message queues

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.