← Coupang Interview Insights

Coupang·Software Engineer·Onsite - System Design / Architecture·Senior

SeniorPrefer not to say
Jun 2026

Summary

Coupang system design round focused entirely on building an IAM system from scratch. Pretty brutal scope for a single session, they wanted everything from auth flows to multi-tenant isolation to token lifecycle.

Questions Asked (1)

Q1

Design a complete Identity and Access Management system covering authentication, authorization, token issuance, multi-tenant isolation, audit logging, scalability, and high availability.

System DesignTechnical Trade-offsAPI & Integrations
Author's notes

This is one of those questions where the scope alone can sink you if you don't immediately narrow it down.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements and scale, then design a modular architecture with separate authentication, authorization, and token services. Walk through each component, emphasizing multi-tenant isolation, audit logging, and trade-offs for scalability and high availability.

Pro tip: Explicitly discuss how you would handle token revocation and key rotation in a multi-tenant environment, as these are often overlooked but critical for security and compliance.

1. Clarify Requirements and Scale

Ask about expected user volume, tenant count, latency requirements, and compliance needs to tailor the design. Establish functional and non-functional requirements.

2. High-Level Architecture

Outline core services: authentication (login, MFA), authorization (RBAC/ABAC), token service (JWT issuance/validation), and audit logging. Describe how they interact.

3. Multi-Tenant Isolation and Data Model

Explain tenant isolation strategies (e.g., separate databases, shared schema with tenant ID) and how they affect security, scalability, and cost.

4. Scalability and High Availability

Discuss horizontal scaling of stateless services, database sharding/replication, caching, and multi-region deployment for fault tolerance.

5. Security, Audit, and Trade-offs

Cover token security (short-lived tokens, refresh tokens), audit logging (immutable, centralized), and trade-offs between consistency, latency, and complexity.

Key Points to Mention

  • Use of standards like OAuth 2.0 and OpenID Connect for authentication and authorization.
  • Token management: JWT structure, signing algorithms (RS256), expiration, and revocation strategies.
  • Multi-tenant isolation approaches: silo, pool, and bridge models with pros and cons.
  • Audit logging: what to log, how to store securely, and ensure tamper-proofing.
  • Scalability patterns: stateless services, caching (Redis), database sharding, and read replicas.
  • High availability: multi-AZ/multi-region deployment, failover, and disaster recovery.

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