Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 4 mesi. Ho sostenuto un colloquio presso CrowdStrike (Sunnyvale, CA) nel mese di lug 2024
Colloquio
The interview process was relatively straightforward. It comprised of 4 rounds 1) Covering front end basics 2) Chat with hiring manager 3) Front end take home test 4) Discussion on take home test 5) Meeting with Collaboration Panel 6) Chat with hiring manager.
Though the process was not that tough, the communication with the company has by far been the worse I have experienced in my entire career. Engineers are oblivious as to which team they interview the candidate for. The manager certainly did not read the resume well enough mistaking the candidate for a Jr Software Engineer. Also the manager did not seem to have all the details required for a candidate joining the team. Please do not expect any follow ups from this company. You will just end up wasting your time. If this is how they treat candidates during the interview process, I wonder what they do when a person joins their company. The whole process took 4 months to complete. There were a lot broken communication gaps. There is no clear feedback as to where you are in the process. At times you will wonder if the position actually exists or they are just wasting your time. I would definitely not recommend interviewing with them.
Ho presentato la mia candidatura online. Ho sostenuto un colloquio presso CrowdStrike
Colloquio
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.
Ho presentato la mia candidatura tramite un selezionatore. Ho sostenuto un colloquio presso CrowdStrike
Colloquio
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.
