
One Shopee Cloud & Platform Engineer candidate describes a first round of resume discussion, quick-fire networking, OS and Kafka fundamentals and a coding question, followed by an in-person round on resume project details.
$123K
Avg. Base Comp
$150K
Avg. Total Comp
This guide rests on a single candidate account, so treat it as one person's experience rather than a fixed format. The candidate did not receive an offer, and they found the process more detail-oriented than they expected for a Cloud & Platform Engineer role.
The first round opened with a short resume deep dive and then moved into a long stretch of CS trivia. Most of it was networking and operating systems, with a little software-defined networking. The candidate remembers Kafka specifics, service discovery between microservices, threads versus processes, and what a file descriptor is. The round finished with a Leetcode-style question. They describe the technical part as quick-fire fundamentals rather than broad system design, and it tested whether you know the infrastructure pieces underneath the cloud tooling.
The second round was in person. The interviewer zoomed in on tiny details of the candidate's personal projects, and past internships never came up, though the candidate had expected them to be the focus. They had not revisited those projects in a while, and it showed.
The practical lesson is to refresh every project on your resume, not just the best-known experience. Be ready to explain what you built, why you made each choice, and how it works underneath. Review core OS and networking concepts, the basics of Kafka and service discovery, and some general coding practice. The account does not report a round count or overall timeline.
Synthesized from 2 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 Shopee process.
The first round was pretty straightforward on paper but ended up being a lot more intense than I expected. It started with a short resume deep dive, then turned into a long stretch of CS trivia, mostly networking and operating systems with a bit of SDN mixed in, and it finished with a Leetcode-style question. The technical questions were not broad system design so much as quick-fire fundamentals, like Apache Kafka specifics, service discovery between microservices, and basic OS concepts such as threads versus processes and what a file descriptor is. I was expecting the usual resume walkthrough and maybe some higher-level cloud questions, but this round was much more about whether you really know the underlying infrastructure pieces.
The second round was in person and honestly felt like a trainwreck. The interviewer zoomed in on tiny details from my resume and kept the discussion hyperspecific, especially around my personal projects. What surprised me was that none of my past internships came up at all, even though I had expected that to be the main focus. Because I had not revisited those projects in a while, I was a bit underprepared for how granular the questioning got, and that definitely showed. Overall the process felt very detail-oriented and less forgiving than I anticipated for a Cloud & Platform Engineer role. I didn’t get an offer, and my main takeaway is to refresh every project on your resume, not just the big-name experience, and be ready for fundamentals-heavy questions rather than only cloud architecture talk.
Prep tip from this candidate
Refresh the exact details of every project on your resume, since the in-person round drilled into small implementation details. Also be ready for fundamentals around Kafka, service discovery, and OS basics like threads vs. processes and file descriptors.
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 Shopee
Redesign batch credit card processing to enable real-time streaming for fraud detection and reporting.
Synthesized from candidate reports. Individual experiences may vary.
The candidate says the first round began with a short walkthrough of their resume before moving into technical questions. Be ready to summarise your projects clearly, because later questions can build on what you say here.
The candidate describes a long stretch of quick-fire computer science questions covering networking, operating systems and some SDN. They recall Kafka specifics, service discovery between microservices, threads versus processes, and file descriptors. The questions were about infrastructure basics rather than broad system design.
According to the candidate, the first round ended with a Leetcode-style question after the fundamentals. The account gives no problem details or difficulty, so general data structures and algorithms practice is a sensible way to prepare.
The candidate describes the second round as in person, with the interviewer focused on small details of their personal projects. Past internships did not come up. They felt underprepared because they had not revisited those projects recently, so refresh every project on your resume.