This felt like one question but it was really five.
Choose a project where you owned a clear slice of work within a larger team effort, and narrate it in first person with concrete details about your decisions, trade-offs, and measurable outcomes. Use a chronological arc—goal, your role, division of labor, friction, resolution, result—and explicitly contrast your contributions with teammates' so your impact is unmistakable.
Pro tip: When describing friction, avoid painting anyone as the villain; instead, frame it as a disagreement about priorities or technical approach, then show how you used data, a prototype, or a small experiment to drive alignment rather than escalating or conceding.
Briefly describe the team, the product or system, and the measurable objective (e.g., reduce checkout latency by 30% for Coupang's mobile app). State why it mattered to the business and who the stakeholders were.
Explain exactly what you owned end-to-end versus what teammates handled, and how you split work (e.g., you built the caching layer, a peer handled API contracts, a PM coordinated with logistics). Mention any cross-functional partners like product, design, or operations.
Describe one concrete disagreement or ambiguity—such as conflicting priorities between speed and reliability, or unclear ownership across teams—and walk through the options you weighed and the call you made. Show how you gathered input and kept the team moving.
Justify one or two technical or process choices you personally made (e.g., choosing an eventual-consistency model over strong consistency to hit latency targets). Explain what you gave up and why it was the right call given constraints.
Close with the outcome—metrics, launch, customer impact—and what you learned about working in a team, resolving conflict, or adapting to ambiguity. Tie it back to how you'd operate at Coupang.
AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.