The process took 2 weeks. I interviewed at CrowdStrike (Bengaluru)
Interview
The interview process is slow and really unsatisfactory. The recruiter called me and told me he will setup a telephonic interview. The interview was with senior manager who was very rude. He kept bragging about his company and wasn't interested much in the answers I was giving. He gave me a standard design question (OOP)which I have solved . I gave a simple answer which he thought very good. Other than that he asked if I work on python or go which I already told recruiter I didn't work. Still he kept on asking and I told him I just used in hackathon. After that almost a week later he called again and gave me a python task in a framework which I said I am not aware of . Then he gave me a C++ task. This was also so simple that I could have done anytime. But he insisted to do it over weekend. After weekend they told me to do code discussion. The discussion was with a person with less experience and less knowledge. Also he was also newly joined. He didn't check if my answer is correct or not just accused me that it matches with one in geeks. The question is nowhere to be mentioned in geeks just a small standard part. But interviewer didn't even understand that other part is much bigger. Also for someone who has hundreds of leetcode and geeks question prep, it's not so difficult to give standard answer. But anyway the process was over. Don't even bother giving interview in this company if you are good in design and ds algo.
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.
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.
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.
