CrowdStrike Interview Questions
& Process

I went through several rounds with engineers and managers from two distinct teams: the auth team and the cloud engineering team. My initial rounds were with the cloud engineering team, who were very professional. They asked standard LeetCode-style questions and queries about handling race conditions. Following that, I had two more rounds with the auth team. The first was with an engineer, which was quite a poor experience. They seemed overwhelmed with a high-severity issue and couldn't focus, yet proceeded with the interview despite my offer to reschedule. It involved a medium-level LeetCode problem, which I'm confident I solved correctly. They provided no feedback on the code and seemed eager to end the call. The final round was with a manager from the auth team, whose main goal appeared to be finding someone willing to work without questioning. The entire experience with the auth team suggested a poor team culture, and I'd advise avoiding them. My sympathy goes out to any good people still on that team.

So I had an HR interview first, then a technical interview. Honestly, it felt pretty tough and not really like a professional setup. The technical part was all over the place, and the questions were way harder than expected and didn't really seem to fit what the job is about. Some felt more like a university test than an interview for a senior role. Plus, they didn't give much feedback after, making it hard to know what I could do better. Overall, I think the process needs more openness and a bit more respect for the candidates.

I had a really good time with the folks at CrowdStrike. It started with a chat to see if it was a fit, then moved into several rounds of interviews with senior people and different team members. I talked with product people about how I handle product and project management. I also had chats with engineers about my leadership, how I grow people and teams, deal with conflict, and build team balance. There was also a system design interview which was challenging and interesting. They gave me the exercise beforehand so I could really think about it and get ready. The recruiter was fast with communication and always kept me in the loop. Everyone I met was genuine, curious, kind, and great to talk to. Unfortunately, the role got cut in my area, so I didn't get an offer, but overall, it was a great experience.

So the interview process started with a recruiter screen, then I had a HM interview that was mostly behavioral questions. After that, I had a manager interview with two managers. Then, there was a technical interview with two engineers, which was pretty much all FE fundamentals. They also gave me a take-home exercise where I had to code a table with some rows of downloadable files and their details from a screenshot. Finally, I had a follow-up interview with two engineers where they asked me what I'd change about my design and how I'd implement filtering and sorting. The last interview was a culture interview with someone not in engineering.