Applied online, I got HR call and she asked my compensation expectation,My expectation was less than what mentioned in their job description and the recruiter tried to telling a range in the same range I asked for. Anyways, I just did my coding interview pretty well and after 2 weeks I did my second interview with hiring manager. I didn’t hear back from them until two weeks. I decided to follow up. They responded me that based on my first coding interview they believe I am level 3 not senior so the compensation is different for that role. I checked levels.fyi and I told I am fine moving forward with level 3 with x range. Then after waiting for long they rejected me. lots of red flags. First tried to manipulate and lower the band for something they already had mentioned in website. Second slow process and ghosting me for 2 weeks. Third red flag , even though I did well in my coding interview they assumed I am level 3 (how they can judge by one round of coding idk, if they knew in first round they should have told me and not have second round with hiring manager ) and finally they rejected me . Lots of manipulation here. Happy it didn’t work. Company culture and transparency is so important for me. They forget that engineers are smart and these kind of tricks are easily understood by them.
3
Altre recensioni di colloqui per Senior Software Engineer presso CrowdStrike
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.
