CrowdStrike Cloud Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at CrowdStrike.
CrowdStrike
Cloud Engineer
Mid Difficult Negative experience No offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Technical screen Onsite Take home
Interview formats
Behavioral Technical Coding System Design
The interview process involved 6 steps. First, a phone screen with HR covering previous roles and future aspirations. Then, a call with the engineering director for introductions, a review of accomplishments, and a focus on cultural alignment. This was followed by a technical discussion with an engineer, touching on past challenges and an algorithm problem. Another technical call with an engineer focused on distributed systems, design, handling large data volumes, and the CAP theorem. Next, a conversation with a manager about contributions throughout your career. Finally, a coding assignment with a 4-hour soft deadline, involving a REST API and required check-ins after completing each part of the assignment.
Confirmed questions4 questions
- What is the next smaller element in an array? For elements with no smaller element on the right, return -1.
- If you have a paginated API for UI data, how would you modify the call for a non-UI client needing all petabytes of data at once?
- Design a video sharing application, considering replication, master-slave setups, the CAP theorem, consistency, bandwidth, and availability.
CrowdStrike
Cloud Engineer
Senior Easy Neutral experience Decline offer 5 rounds
Interview process
Recruiter call Phone screen Take home Onsite Offer
Interview formats
Coding System Design Technical Behavioral
Had some chill chats with the hiring manager and others. Went through 2 phone coding challenges, then a take-home design task. After that, I had an onsite interview in Sunnyvale. The whole thing was a bit of a mixed bag. The initial part before the onsite felt really good. The design task was neat, the coding challenges were fair, and talking with the hiring manager and potential colleagues was awesome. The onsite, though, wasn't as great. It consisted of 3 separate 45-minute interviews, each with a single engineer. Only one of them seemed to know my background. None of them seemed prepared with questions tailored for my role; each interview just involved solving a simple whiteboard problem, which felt pointless. The onsite gave me the vibe that these engineers are super swamped. They didn't say it directly, but it's clear they're stretched really thin. It sounded like the job would be pretty demanding. Still, I was keen to move forward with CS because the technical challenge is tough, the engineering team is sharp (even with the odd onsite), and the pay seemed to match the workload. Sadly, the offer was surprisingly low, and the recruiter didn't even try to negotiate. So, it probably worked out for the best.
Confirmed questions1 question
- Could you reverse an array for me?
CrowdStrike
Cloud Engineer
Entry Difficult Positive experience Accept offer 3 rounds
Interview process
Recruiter call Phone screen Take home
Interview formats
Technical Coding System Design
First, there were talks with HR and the hiring manager, then some phone screening interviews. Finally, a task to write a working micro-service within a 5-hour time limit, using either Java, Python, or Go, and including swagger definitions.
Confirmed questions3 questions
- Can you answer a basic computer science question and write the corresponding algorithm?
- Could you write a micro-service that handles file uploads via an HTTP swagger API?
- What are your thoughts on distributed systems, for instance, how would you scale a service using Cassandra and incorporate search functionality?
CrowdStrike Cloud Engineer Interview Questions
Quoted word for word from CrowdStrike interview reports.
“What is the next smaller element in an array? For elements with no smaller element on the right, return -1.”
Read reports →“What's the difference between thread and process context switching?”
Read reports →“Could you tell me the complexity of binary search?”
Read reports →“Can you explain the difference between a heap and a binary search tree?”
Read reports →“If you have a paginated API for UI data, how would you modify the call for a non-UI client needing all petabytes of data at once?”
Read report →“Implement a REST API using Redis for file metadata and dependencies, including CRUD operations and three query calls (one BFS/DFS variation), given that file dependencies form a directed graph.”
Read report →“Could you reverse an array for me?”
Read report →“Could you explain what a hashmap is and in what scenarios it would be preferable to data structures like linked lists and arrays?”
Read report →“Can you explain how to merge intervals?”
Read report →Formats, difficulty and experience
Across all 14 CrowdStrike interview reports.