J'ai postulé via un recruteur. Le processus a pris 3 mois. J'ai passé un entretien chez CrowdStrike en oct. 2023
Entretien
Recruiter reached out via linkedin. We had an brief initial chat, after which I applied for the position. Next was a 45 minute manager screen with pretty standard questions about past projects I've led.
At this point, CrowdStrike gave me a take home project. The take home project involved distributed computations and took about 10 hours. After I turned it in, I got positive feedback, but was told that due to timing, another candidate had been offered the position and they were closing the position.
I asked if the recruiter had other open roles, since the feedback seemed positive. It seems like there are several in-house recruiters working on different but similar roles and they don't really have much visibility into other roles outside their own purview. Eventually, I was put in touch with another recruiter with a similar role, who gave me a system design take-home problem. I had about a week to put together a design document and then was given an hour to talk through it with a couple of engineers. After this, the recruiter said I would receive feedback. However, after the system design interview, I haven't received any feedback or response to my follow-up emails from the recruiter for the past month.
My impression of CrowdStrike was positive as a company, but their hiring and recruitment process seems to be a disorganized mess.
J'ai postulé en ligne. J'ai passé un entretien chez CrowdStrike
Entretien
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.
J'ai postulé via un recruteur. J'ai passé un entretien chez CrowdStrike
Entretien
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.
