Real, anonymous reports from people who interviewed for Solutions Engineer at Cloudflare, newest first and distilled into what to expect across the loop.
Get your personalized Cloudflare Solutions Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My process started normally enough: I had a hiring-manager interview, and then a live coding round was scheduled next. Technically, the people involved felt cool and friendly, and I didn’t feel as nervous as I expected because the interviewers were engaged and gave context about what they worked on. But the recruiter and coordination side derailed the experience.
In my timeline, there were scheduling issues that turned into real friction. The recruiter side felt slow and inconsistent—at one point there were no interview slots after they said I’d get one, then weeks later a slot appeared. Even when the meeting time finally landed, the hiring manager didn’t show up, and I received an apology later for a scheduling conflict. I also had instances where the coordination was basically silent: I sat waiting in a chat with no sign the interviewer would join, and even after reporting it, the recruitment coordinator didn’t respond.
6 months ago
Difficult Positive United States
My interviews started with an informal conversation with the hiring manager, which set the stage for how I’d be evaluated. Then I spoke with a lead recruiter about the role and what salary expectations looked like, followed by a technical interview. The next segment was more people-heavy: I joined a panel where I demo’d one of their products, which made the process feel less like a pure coding test and more like a chance to see how I think and explain.
After that, I moved into the later-stage conversations with a director and then someone from the C-suite. Separately, I also had rounds that emphasized communication and iterative reasoning: one technical task had me verbally talk through how I’d design something, iterate on my approach, and end with conceptual wrap-up rather than just arriving at a single answer. In another technical round, the challenge was a modified version of an LRU cache problem, followed by team matching.
> 1 year
Difficult Negative Stockholm, Stockholm
My process was the most challenging and disorganized I’d experienced anywhere. It didn’t even start in the usual recruiter-first way—it began with a c…
> 1 year
Average Negative Washington, DC
I went into the process knowing I’d likely be evaluated on how I presented and whether I could handle a hands-on technical sales portion. The tech int…
> 1 year
Easy Negative Thailand
The hiring manager conversation itself went fine, but the way the process was run around it felt disrespectful of my time. A big part of what happened…
Unlock every Solutions Engineer interview experience
