Coupang USA Staff Engineer (L6-1) Onsite Interview Experience
Question Details
Role: Staff Engineer (L6-2)
Phone Screen (60 mins) *
Format: Two behavioral questions, one coding problem, and a system design discussion. *
Problem: Standard coding question extended
Full Details
Role: Staff Engineer (L6-2)
Phone Screen (60 mins) *
Format: Two behavioral questions, one coding problem, and a system design discussion. *
Problem: Standard coding question extended into a design discussion regarding distributing the solution across a fleet of servers.
Onsite Interview Rounds *
Bar Raiser *
Focus: In-depth discussion of past experience, design choices in previous projects, and behavioral questions. *
Verdict: Strong Hire. *
Coding Round 1 *
Focus: Two behavioral questions and one coding problem. *
Problem: Sort Colors. *
Constraint: The interviewer required a specific one-pass solution without using a map, prioritizing a specific implementation over general time/space complexity efficiency. *
Verdict: Weak Hire. *
Hiring Manager *
Focus: Behavioral questions (hardest project, role definition, conflict resolution) and experience deep dive. *
Outcome: There was a mismatch between the candidate’s research/MVP background and the interviewer's focus on distributed systems scaling. Despite the short duration of the technical portion, the feedback was positive. *
Verdict: Strong Hire. *
Coding Round 2 *
Focus: Two behavioral questions and two coding problems. *
Problem 1: Given networks of two friends represented by a grid, find the minimum connections required to join them. *
Solution: Solved using Breadth-First Search (BFS). *
Problem 2: Given a binary grid (0s and 1s), identify the number of distinct shapes formed by the 1s. *
Verdict: Strong Hire. *
System Design *
Focus: Two behavioral questions and a design problem. *
Problem: Design a ride-sharing application (e.g., Uber). *
Outcome: The discussion lacked the depth and conviction expected for the L6-2 level. *
Verdict: No / Weak Hire for L6-2.
Follow-Up Round *
Context: Scheduled due to mixed feedback on the previous System Design round and the "Weak Hire" on Coding Round 1. *
Focus: Two behavioral questions and a design problem. *
Problem: Design a blob storage system (e.g., S3). *
Discussion: The round was collaborative, covering topics such as DynamoDB replication, partitioning strategies, and internal mechanics. *
Verdict: Strong Hire for L6-1 (Downleveled).
Final Outcome A verbal offer was extended for the L6-1 level upon agreement to relocate. However, the offer was subsequently paused/rescinded due to company restrictions on H1 visa transfers involving government fees.
About This Question
This is a reported interview question from a coupang interview for a swe role (staff level) during the onsite round reported in 2025.
It covers the following topics: Graph, Sql, System Design, Queue, Behavioral, Matrix .
Topics
About Coupang Interview Reports
This question was reported by a candidate who interviewed at Coupang. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Coupang are the higher-signal extractions to take from this report.
For broader preparation context, the Coupang interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Coupang reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Coupang Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Coupang reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.