Software Engineer candidates at Coupang describe a hiring manager conversation, coding rounds, a system design round and a bar-raiser, with four or five rounds reported. Questions and format vary by team.
$153K
Avg. Base Comp
$250K
Avg. Total Comp
4-5 rounds
Typical Rounds
Not reported
Process Length
Coupang software engineer interviews differ from team to team, so treat the reports as examples rather than a fixed script. Candidates at the Software Engineer level describe a recruiter or hiring manager conversation, one or more coding rounds, a system design round and a bar-raiser interview. The round counts they give are four or five.
The hiring manager conversations lean on your own work. One candidate talked through past projects and the reasoning behind each decision, including what they would do differently now. Another described a 30 to 45 minute video call about background and fit with the job description.
Coding questions include an LFU cache, a medium dynamic programming problem, and an in-memory file system with create, move, delete and list operations. The candidate who built the file system said the coding and design prompts were intentionally vague, so they had to ask clarifying questions and drive the conversation.
Design prompts include a movie theater ticketing system, where concurrent bookings and consistency versus availability came up, and a catalog and recommendation system. A Staff Software Engineer candidate was asked to design an e-commerce platform.
Two candidates describe the bar-raiser differently. One was told it checks the bar across the org rather than for a single team. Another found it mostly behavioral, with questions about decision-making. A third candidate described behavioral rounds built around Coupang's leadership principles, including a question about a time normal approaches did not work and what they did instead.
Outcomes were mixed among the Software Engineer reports: one candidate accepted an offer, one received an offer, and one had no offer. One candidate also said interviewers gave feedback after each session, so they knew what worked and what didn't as the loop went on.
Synthesized from 10 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Coupang process.
My interview loop with Coupang had five rounds total, though the structure varied from what I initially expected. It started with a quick recruiter call, then a hiring manager call on video that ran about 30 to 45 minutes. Unlike some processes where the hiring manager is just one voice in the panel, mine was separated out—a chance to discuss my background and whether the JD aligned with my experience.
After that came four panel interviews, each about an hour. The first two were focused on coding problems at the medium LeetCode level—nothing exotic, just solid problem-solving. One involved dynamic programming, which tested my ability to think through optimal substructure and state transitions. The third round combined a LeetCode-style problem with a system design component where I had to design a catalog and recommendation system. This required thinking about how to structure data for fast queries and how to scale recommendation logic across millions of products.
The final round was the bar-raiser interview, which felt more behavioral and cultural. They asked about decision-making frameworks I use in the workplace—less about specific technical depth and more about how I operate as an engineer and team member. The whole loop was rigorous and back-to-back, which was exhausting but gave the team a complete view. The dynamic programming focus and the catalog system design were the most technically demanding parts; the bar-raiser was more about soft skills and alignment.
Prep tip from this candidate
Medium-level dynamic programming problems are a real focus here—practice problems with optimal substructure, memoization, and complexity optimization. The system design round tests both data structure thinking and architectural decisions, so be prepared to discuss trade-offs in recommendation systems specifically.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Coupang
Reconstruct the path of a trip so that the trip tickets are in order.
| Question | |
|---|---|
| P-value to a Layman | |
| Nearest Common Ancestor | |
| Scrapers or Users | |
| Minimum Parking Spots | |
| Weighted Average Sales | |
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Subscription Overlap | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Random SQL Sample | |
| Top 3 Users | |
| Customer Orders | |
| Monthly Customer Report | |
| Merge Sorted Lists | |
| Upsell Transactions | |
| Longest Streak Users | |
| Size of Joins | |
| Rolling Bank Transactions | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Last Transaction | |
| Get Top N Frequent Words | |
| Bagging vs Boosting | |
| Flight Records | |
| Retailer Data Warehouse | |
| Raining in Seattle | |
| Paired Products |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe a recruiter or HR chat followed by a conversation with the hiring manager. One was a 30 to 45 minute video call about background and fit with the job description. Another went deep on past projects and the reasoning behind each decision. Be ready to explain your trade-offs and what you would change today.
Reported problems include an LFU cache, a medium dynamic programming problem, and an in-memory file system with create, move, delete and list operations. The candidate who built the file system said the prompt was intentionally vague, so clarifying requirements and edge cases came before writing code.
Software Engineer candidates report designing a movie theater ticketing system, where concurrent bookings and consistency versus availability came up, and a catalog and recommendation system. One said the requirements were deliberately rough and they had to flesh out the details. A Staff Software Engineer candidate was asked to design an e-commerce platform. State assumptions early and defend your trade-offs.
One candidate was told the bar-raiser assesses the bar across the org rather than for a specific team. Another found theirs mostly behavioral, with questions about decision-making frameworks. A different candidate described behavioral questions tied to Coupang's leadership principles, including a time when normal approaches did not work and what they did instead. Prepare specific stories with concrete detail.
Software Engineer reports include an accepted offer, a received offer and a rejection. One candidate said interviewers gave feedback after each session. No candidate gave a start-to-finish timeline, so ask your recruiter about the schedule.
