CloudKitchens software engineer candidates describe a recruiter screen, a technical phone screen, and an onsite built around a 3-hour coding project and project deep dives. Two reports give timelines of about eight weeks and nearly three months.
$212K
Avg. Base Comp
$365K
Avg. Total Comp
4-5 rounds
Typical Rounds
8-12 weeks
Process Length
The most distinctive part of the CloudKitchens loop is not a classic algorithm screen. Two candidates describe a 3-hour take-home-style coding project during the onsite. One built a CLI around courier dispatch and order delivery, with thread-safe concurrency, object-oriented design, testing and documentation expected. The other built an API-backed project involving multithreading, concurrency, test coverage and a Swagger API integration, and said they missed that the data had to be fetched from that API. Read the prompt closely and ask early about requirements.
A review of the work followed in both reports. One candidate was pressed by engineers on design choices and asked to add features on the fly. The other had their implementation picked apart in a review session. A frontend candidate described a project demo as a full round, and another candidate's technical screen opened with a project deep dive on a low-level problem. Prepare a past project you can explain from code details up to architecture, and consider diagrams.
Technical screens varied. One candidate was given code in an invented language and asked to predict its output, then a string parsing problem with unusual edge cases. Another spent about 20 minutes stuck before a hashmap approach worked. A senior candidate reported a UI system design round where the interviewer would not narrow scope, so be ready to set constraints yourself.
All six reports ended without an offer, and one senior candidate was rejected right after a recruiter call. Two candidates described slow or unclear recruiter communication, so confirm each round's format in writing. The sample is small and mixes levels and a frontend role.
Synthesized from 6 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 Cloudkitchens process.
I'd been through CloudKitchens before—three years ago when I was still intermediate level—and made it to an onsite. This time around as a senior, the recruiter actually reached out to me. The phone screen went well; she seemed confident and enthusiastic the whole way through, said my resume was exactly why she contacted me, and told me it was being passed to the hiring manager.
Then I got rejected. No technical interviews, no onsite, just a rejection after that recruiter call. It doesn't add up. The recruiter was engaged and positive, yet somehow my background didn't move forward. I've worked at Amazon and other solid companies, and I'm not sure what changed or what they're actually looking for at this stage. I've heard the recruiter team there is largely outsourced, which might explain some of the inconsistency—there's probably a disconnect between what the recruiting team communicates and what hiring managers actually care about.
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 Cloudkitchens
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Monthly Customer Report | |
| Over-Budget Projects | |
| Hurdles In Data Projects | |
| Bagging vs Boosting | |
| Daily Retention Summary | |
| Delivery Estimate Model | |
| Month Over Month | |
| Google Maps Improvement | |
| Average Order Value | |
| Sum to Zero | |
| Longest Streak Users | |
| Clickstream Data | |
| Valid Anagram | |
| Success Measurement | |
| Target Indices | |
| Portfolio Platform Architecture | |
| Christmas Dinner Ingredient Optimization | |
| How Many Friends | |
| Celebrity Mentions | |
| Count Transactions | |
| Concurrent LLM Serving | |
| Slow SQL Query | |
| Biggest Tip | |
| Data Pipelines and Aggregation | |
| DDoS Attack Response | |
| A/B Testing a Checkout Button Change | |
| Sample Time Series | |
| Finding the Maximum Number in a List | |
| Diagnosing Query Speed Degradation |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter or HR call covering background and logistics. Some say the full loop format was not explained, so ask what each later round involves. One senior candidate was rejected right after this stage despite a positive call.
Reports vary. One candidate described a one-hour screen where a hashmap approach unlocked the problem. Another described three parts: a project deep dive, predicting the output of code in an unfamiliar made-up language, and a string parsing problem with unusual edge cases. Expect to explain your thinking aloud.
Two candidates report a three-hour project in the onsite. One built a courier dispatch CLI, and the other an API project with a Swagger integration. Both mention concurrency, and the reports cite testing, object-oriented design, documentation and test coverage. Confirm requirements early, including where data must come from.
Candidates report engineers reviewing the project, asking about improvements, and sometimes asking for features to be added live. One also describes a past-project walkthrough with an engineering manager, from code details up to architecture. A frontend candidate describes a project demo round.
Senior and frontend reports add other rounds. These include a data modeling and algorithm interview, a UI system design round where the interviewer would not narrow scope, and React plus online coding assessments. Candidates report timelines of roughly eight weeks to nearly three months, and some report slow scheduling.
