Real, anonymous reports from people who interviewed for Software Engineer at Cloudflare, newest first and distilled into what to expect across the loop.
I started with a recruiter touchpoint, but the process felt a bit uneven right away—the conversation was rushed, and even though the recruiter explained the path pretty clearly, the overall cadence didn’t feel smooth. After that, I had a hiring-manager style discussion and then a technical round that felt more like a collaborative problem-solving session than something purely “LeetCode.” I was able to talk through my thinking with the interviewer while we worked, and the tone stayed conversational.
My process took long enough that it started to feel like the goalposts were moving. It began with a hiring-manager call, then I went into a live coding round where I built a Battleship-style game. After that, I entered a larger loop: there was an “orange cloud” behavioral interview, a debugging-style discussion, a system design conversation, and a PM-focused interview. I also had another hiring-manager touchpoint that included an AI-assisted coding challenge, where I used prompts to fix bugs in a project/environment I wasn’t fully familiar with.
The interview process can be lengthy and may involve multiple stages, including hiring manager calls, technical rounds, and behavioral interviews, often stretching over several weeks or even months. Candidates noted that the timeline can feel inconsistent, with delays and lack of communication contributing to frustration.
Technical interviews focus on practical problem-solving rather than traditional LeetCode-style questions, emphasizing implementation details and communication during coding tasks. Candidates are often expected to demonstrate their thought process while coding, with some rounds including live coding or AI-assisted challenges.
Behavioral interviews are generally straightforward, focusing on collaboration, fit, and communication style rather than deep technical depth. Candidates reported that these rounds often included discussions about their background and motivations for applying.
Candidates can expect system design interviews that vary in difficulty, often requiring them to discuss trade-offs and design principles. These rounds are designed to assess not only technical skills but also the candidate's reasoning and communication abilities.
The coordination and communication from recruiters can be inconsistent, with reports of scheduling issues, lack of follow-up, and unclear timelines. Candidates expressed frustration over the chaotic nature of the recruitment process, which detracted from their overall experience.
While the technical and behavioral interviews are generally perceived as fair and structured, many candidates did not receive offers, leading to feelings of disappointment. The overall difficulty was described as average, but the lack of closure or feedback after interviews was a common point of frustration.