← Coupang Interview Insights

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

SeniorPrefer not to say
Apr 2026

Summary

Coupang system design round focused entirely on PKI infrastructure. Pretty deep cut for a single session, they wanted the full stack from root CA down to client trust validation.

Questions Asked (1)

Q1

Design a PKI system end-to-end, including the certificate authority hierarchy, how certificates get issued and signed, revocation mechanisms, key storage, lifecycle management, and how clients validate the trust chain.

System DesignTechnical Trade-offsAPI & Integrations
Author's notes

This was basically the whole interview in one question.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by clarifying requirements (scale, security level, use cases) and then walk through the PKI design in layers: hierarchy, issuance, revocation, key storage, lifecycle, and validation. Emphasize trade-offs and how each component integrates with the others, and conclude with how you would monitor and operate the system.

Pro tip: Show awareness of real-world constraints like certificate expiration and revocation propagation delays, and propose mitigations such as short-lived certificates and OCSP stapling. Mention automation and infrastructure-as-code for managing PKI at scale, which is critical for a company like Coupang.

1. Clarify Requirements and Constraints

Ask about scale (number of certificates, issuance rate), security requirements (key sizes, algorithms), compliance (e.g., PCI DSS), and existing infrastructure. This ensures your design is tailored and demonstrates you think before designing.

2. Design CA Hierarchy

Propose a root CA (offline, highly secured) and intermediate CAs for different purposes (e.g., internal services, external-facing). Explain the rationale for separation to limit blast radius and enable flexible policy enforcement.

3. Define Certificate Issuance and Signing

Describe the enrollment process (e.g., CSR generation, identity validation), the signing workflow (possibly automated via API), and how to handle certificate templates and profiles. Mention protocols like ACME for automation.

4. Implement Revocation and Lifecycle Management

Compare CRL vs OCSP, discuss trade-offs (latency, scalability), and propose a hybrid approach with OCSP stapling. Outline certificate lifecycle: issuance, renewal, revocation, and expiration, with automation for renewal and monitoring for expirations.

5. Ensure Secure Key Storage and Validation

Explain key storage options (HSM, TPM, secure enclaves) for CAs and clients, and how clients validate the trust chain (certificate path validation, checking revocation, hostname verification). Mention pinning and trust stores.

Key Points to Mention

  • CA hierarchy: root CA offline, intermediate CAs for issuance, cross-signing for trust
  • Certificate issuance: CSR, identity validation, automated enrollment (ACME, SCEP)
  • Revocation: CRL vs OCSP, OCSP stapling, short-lived certificates to reduce revocation need
  • Key storage: HSMs for CA private keys, secure storage for client keys (TPM, keychain)
  • Lifecycle management: automated renewal, monitoring, and revocation processes
  • Client validation: trust store, path validation, revocation checking, hostname verification

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