There was one phone round followed by four onsite rounds.
The interview with the head of engineering was mostly behavioral. They grilled me about previous contributions, various projects, company culture, and went over the company/org goals. This person was very detail-oriented.
Next, an interview with the engineering manager was a coding interview. Another interview with a director involved designing a data structure for a specific use case and coding it. They also went over one of my previous projects in detail, spending 25 minutes on one project and asking a number of follow-up questions.
An interview with a principal engineer focused more on the architecture of another project of mine. Again, there were a lot of follow-up questions and scenario-based design questions.
The interviews were well organized compared to my company. Each interviewer had a specific goal and they stuck to it. It seemed they spoke with one another between interviews, which usually leads to preconceived notions. Of course, I don't care as I made it through.
Another thing that stood out was that the engineering manager could get into the code. I was amazed when they were able to figure out an issue with my code.
All in all, a positive experience.
One DP question and one array-related problem of medium difficulty. Be prepared for a deep dive into your projects and many follow-up questions.
The following metrics were computed from 1 interview experience for the Coupang Principal Engineer role in Mountain View, California.
Coupang's interview process for their Principal Engineer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Coupang's Principal Engineer interview process in Mountain View, California.