Cloud Engineer applicants have rated the interview process at CrowdStrike with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 83% positive. To compare, the company-average is 42.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Cloud Engineer roles take an average of 41 days to get hired, when considering 6 user submitted interviews for this role. To compare, the hiring process at CrowdStrike overall takes an average of 29 days.
Common stages of the interview process at CrowdStrike as a Cloud Engineer according to 6 Glassdoor interviews include:
One on one interview: 28%
Phone interview: 17%
Skills test: 17%
Background check: 17%
Presentation: 11%
Drug test: 6%
Personality test: 6%
Here are the most commonly searched roles for interview reports -
I applied online. I interviewed at CrowdStrike (Tel Aviv-Yafo) in Jun 2024
Interview
The interview process consists of five stages: an initial meeting with HR, followed by a live coding session, then a system design interview. After that, there is an interview with the hiring manager, and finally a concluding HR review.
The interview process was much longer than ones I had done for other positions at other companies.
That said, it was a good opportunity to meet different members of the team I would be joining and helped make sure they were a good fit for me as much as I a good fit for them.
Interview questions [1]
Question 1
There was a coding style interview question regarding a LRU cache
I applied through an employee referral. I interviewed at CrowdStrike (Bucharest, Bucuresti) in Aug 2021
Interview
The interview process is what you'd expect from other high-bar companies, like Amazon. It is overall lengthy and made of 4 independent interviews. Crowdstrike does not ask behaviour questions. The first interview tested algorithms knowledge and was overall easier than I expected. It was conducted on a shared coding platform, like HackerRank. The second interview tested system design knowledge and started with a problem formulation and continued as a free conversation that aimed at complicating the initial problem as the interviewee came up with solutions. The third interview occupied a large time slot (~6h) and involved coding a working API. I think they dropped this long format interview since, as it was discouraging candidates from continuing the interview process. The last interview was a manager & HR discussion.
Interview questions [3]
Question 1
What is a hashmap and when would one use a hashmap instead of similar data structures like linked lists and arrays?