I applied online. The process took 3 weeks. I interviewed at CrowdStrike (San Francisco, CA) in Oct 2023
Interview
The interview process at CrowdStrike followed the standard protocol for a software engineering position, which I found to be well-organized and clear. The initial screening was followed by a technical interview where I was asked to solve some basic problems from Leetcode. This approach helped me understand that the company values problem-solving skills and has a keen interest in assessing coding proficiency. The questions were fair, leaning more towards fundamental concepts rather than obscure challenges, which I appreciated.
Interview questions [1]
Question 1
Given an array of integers nums and an integer target, return indices of the two numbers such that they add up to target.
You may assume that each input would have exactly one solution, and you may not use the same element twice.
You can return the answer in any order.
Example 1:
Input: nums = [2,7,11,15], target = 9
Output: [0,1]
Explanation: Because nums[0] + nums[1] == 9, we return [0, 1].
Example 2:
Input: nums = [3,2,4], target = 6
Output: [1,2]
Example 3:
Input: nums = [3,3
I applied through a recruiter. I interviewed at CrowdStrike
Interview
Was interviewed by engineers and managers from 2 different teams. The auth team and cloud engineering team. Had a few rounds with engineers from cloud engineering team and the team was very professional with their approach. The regular workout it LC based questions and queries on handling race conditions. Had another 2 rounds with the auth team one with an engineer and another was the final round with the manager. The one with the engineer was easily the worst interview i had to sit through. The engineer was dealing with some high sev issue and clearly had their hands full and was unable to concentrate on the interview. Despite me offering to reschedule if this was not a good time they went ahead with the interview which was medium level LC question that I am sure i got right. They had no comments on the code and just wanted to get of the call. The other round was with someone at higher levels from the auth team whose primary expectation seemed to be to find someone who would stretch without any questions. Should have the titled the role "Senior Slave Engineer".
On a personal level I would recommend AVOID the auth team at all costs. For the sane folks in that team my heart goes out to you. Culture within that team seems not so great.
Very disorganized. Interviewers were very unprofessional, and hostile. They emailed me saying they are not moving forward with me then emailed me again the next day to schedule another call.
Everything went very smoothly during the interview. After a brief introduction, we moved directly into the coding part, which was handled in a LeetCode-style format. There wasn’t much discussion beforehand, as the focus was primarily on problem-solving and implementation, making the process clear, structured, and efficient.