Real, anonymous reports from people who interviewed for Frontend Engineer at CloudKitchens, newest first and distilled into what to expect across the loop.
Get your personalized CloudKitchens Frontend Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
Recruiters were pretty organized about scheduling, but the overall process itself dragged out. I started with a recruiter call where they gave context about the company, then quickly got pulled into the first round. After that, I had another recruiter contact where the full process was laid out and I was asked about my availability for a full day versus splitting it across two days.
What I remember most is how long it took end to end—around fifteen hours total. The structure wasn’t presented as a quick sequence of interviews; it felt like a marathon with enough rounds and pacing that it took over my whole day. Even if the company might be great, the experience left me feeling frustrated because it seemed like the interview process needed tightening and more efficient flow.
> 1 year
Easy Negative Seattle, WA
Recruiter contact kicked things off, and I got scheduled for a technical interview that ran in a CodePad environment. The coordinator caught my attention because the interviewer called at the wrong time while I was busy, and when we finally connected, the interviewer didn’t introduce themself and didn’t ask me any actual questions.
Instead, they pointed me straight to the coding challenge instructions. I was mostly on my own from there, and the overall feel was oddly quiet and unstructured for an interview where you’d expect at least some context or clarifying questions.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
