CrowdStrike Frontend Engineer Interview Questions
& Process

So there were two rounds of technical questions first, they read them off a list which I guess is to stop bias. Standard stuff really. Then I had a take-home task. After that, it would have been a presentation, then meeting the team, and finally a chat with HR. The first couple of stages took about two weeks. Then I got a week for the take-home task, which was supposed to be 5 hours but ended up taking me 10 because I wanted to do it properly, making lots of components and setting up a mono-repo with a mini design system. After I sent it in, it took almost 3 weeks to hear back. I felt this was pretty rude, honestly. They give little to no feedback when they reject you, just a flat no. Having hired people myself, I know what good code looks like. I reckon they have an EmberJS bias; they might be the only big company using it for everything, given its low usage. My project was mostly native web components with a bit of EmberJS that I had to learn. The only feedback I got was that EmberJS wasn't my primary framework - which missed the whole point. The app worked and met all the requirements. It was super frustrating! The initial stages were good, but the home task was a letdown. If you're going to ask candidates to spend 5 hours on a detailed task, the least you can do is give 15 minutes of constructive feedback.

It was pretty standard: 1 phone screen, 1 technical, and 1 behavioral interview. The person doing the behavioral interview actually hit me with some technical questions, which was unexpected. Then, about two weeks later, a different team reached out for another behavioral chat. This one was way more relaxed, like a casual conversation, and they gave me an offer the very next day.

I applied at CS via an employee referral. The whole process from application to offer letter took 2 months, but it might be faster for others since there were unique circumstances. Everything was remote over Zoom. First, I interviewed with the manager where we talked about the role and I was asked some technical questions. Then, I interviewed with 2 engineers where we had an in-depth discussion about the role, department, company, values, my experience, and workflow, and they asked really thought-provoking questions. After that, I did a take-home code challenge which was relevant to the job and enjoyable. Next, I had a code review with 2 engineers to discuss my take-home and further development, which was casual and included some pseudo code but no whiteboarding. Finally, I had a final interview with the hiring manager, which was informational and focused on the specifics of the team, my work, training, and the tech stack. The process concluded with a verbal offer, written offer, and a background check. The recruiter was very helpful and communicative throughout, making it a fantastic interview experience.