I gave an interview in Pune.
The recruiter first called and provided brief information about the company.
The interview process heavily focused on algorithms. I had a total of 5 interviews, including a 4-hour coding test.
In the first interview, I was given a live debugging task to fix a binary tree problem. This was conducted by a manager.
Next, I had a 4-hour coding test where I needed to solve 2 out of 3 problems. One was a data structure problem: LRU implementation. The second was a thread implementation. The third was also a data structure: stack implementation.
The coding round was followed by a code review, where the panelists asked about the algorithms used in problem-solving and generic code review questions.
Since I interviewed for a Linux role, the interviewer for the code review didn't ask me much about Linux. Therefore, they scheduled another round specifically for Linux. However, it turned out to be another data structure and algorithms round, with very few Linux-related questions.
The first four rounds were positive, and I felt good about the organization. The last round was scheduled with the director.
That round was not good. He had a very investigative approach during the interview. He was not very professional, and I disliked the way he conducted the interview. General discussion was missing, and I felt like I was being interrogated. I would not have joined if I had been selected based on this round with the director, who recently joined CrowdStrike from Symantec.
However, a plus for the recruiter; he did a good job during the interview process.
Most data structures and algorithms questions.
The following metrics were computed from 1 interview experience for the CrowdStrike Software Engineer role in New York, New York.
CrowdStrike's interview process for their Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for CrowdStrike's Software Engineer interview process in New York, New York.