J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez CrowdStrike (Boston, MA) en mars 2023
Entretien
First round with recruiter Second Round with Engineering director Third round with 2 Senior developers and an observer The first two rounds were good behavioral and some high level design questions, on the technical interview was a bit more technical into coding with a not too hard questions listed above, pretty basic. The part that got me out of context and I found difficult to navigate was the continuous interruption or over talking which sadly I was not able to handle very well so I struggled a bit. I ended up asking to finish the call to not waste their times more. I am not the best person interviewing, especially with these interviews that try to evaluate engineers base on Computer Science college questions (Went to college 20 years ago) so I usually avoid these type of interviews and try to go only with the more realistic ones. I do interview a lot, as a Tech Lead and Principal Engineer so I understand where these are coming from and that efficiently evaluating engineers is really hard.
Questions d'entretien [1]
Question 1
How to implement an Iterator of several sorted iterators?
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.
