Systems Engineer applicants have rated the interview process at Cloudflare with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 53% positive. To compare, the company-average is 35.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Systems Engineer roles take an average of 49 days to get hired, when considering 17 user submitted interviews for this role. To compare, the hiring process at Cloudflare overall takes an average of 39 days.
Common stages of the interview process at Cloudflare as a Systems Engineer according to 17 Glassdoor interviews include:
Phone interview: 26%
One on one interview: 21%
Group panel interview: 18%
Skills test: 16%
Presentation: 8%
Drug test: 5%
IQ intelligence test: 3%
Personality test: 3%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1+ week. I interviewed at Cloudflare in Nov 2012
Interview
I followed up a job posting for people interested in Golang. I was contacted quickly and had a Skype interview with 2 engineers. This went well, and I was scheduled to talk to 3 more engineers individually for lengthier sessions in succession, and John Graham Cumming.
All the interviews went excellently, with the exception of JGC who was 45 minutes late. Despite my being well aware of his celebrity status in the programming community, he obviously wasn't impressed with my lack of interest in London and the tardiness of his call led to my failure to reflect on his achievements.
That said, their initial response after the interviews was positive, and then complete radio silence.
Interview questions [1]
Question 1
The role that proxying, load-balancing, and other HTTP-level tricks that occurs on the Internet these days is astounding. While being familiar with these things would be nice, it certainly isn't a requirement for effectively tackling these problems.
solid, very nice interviewers, technical s were interesting and collaborative. Overall less leetcody than general and felt more like a conversation/ pair programming. Recruiters were very slow though. Most non coding interviews were very fluffy i.e just talk through your resume/ a project you worked on. There was an emphasis on how you like to work, i.e what youre looking for in both a team and work in general.
Total 7+ rounds. First recruiter round. Rejected after second round(hiring manager).
Recruiter round focussed on Cloudflare, comp details, rounds of interviews and few questions about profile
HM:
Why are you looking for a new role?
Why cloudflare?
Interview questions [1]
Question 1
HM:
Why are you looking for a new role?
Why cloudflare?
I applied through a recruiter. The process took 3 weeks. I interviewed at Cloudflare
Interview
The process included about 8 interviews with different people but mostly with the team member. The technical questions were fair, not very hard. And the also the interviewers were polite and professional.
However, the whole process tool about 10 hours, and it was scheduled in a week or two, so you need to allocate a huge amount of time. This was a big issue specially, if you need to plan it during the working hours.
Once all the interviews finished, there was no update for a week, and then finally a cold email saying No! without any feedback or explanation.
It's totally fine to say "No" in an interview process, but given 8 rounds of interviews and many hours, first the silence period and second, not providing any feedback and explanation was a negative experience.
Interview questions [1]
Question 1
Have you experienced any mistake and how did you handled it?