Went through the CrowdStrike software engineer interview process last spring for a senior IC role on their Falcon sensor team. Going to write up what actually happened because I couldn't find a good recent thread.
Total timeline was about 5.5 weeks from recruiter first contact to verbal offer.
Round 1: Recruiter call (30 min) Standard background check. They wanted to know why CrowdStrike specifically, which is a real question there, not filler. Security domain experience matters to them. She was upfront about comp band: senior in Austin was $155k-$185k base at the time.
Round 2: Hiring manager screen (45 min) Half technical, half 'tell me about yourself.' HM asked about a time I debugged a production incident under pressure. He pushed on specifics. Not behavior-checklist-style, more like a genuine conversation. Asked about my opinion on kernel-level vs. user-space tradeoffs, which gave away the team pretty clearly.
Round 3: Technical phone screen (60 min) Coding in CoderPad. Two problems: one graph traversal, one string parsing that felt like real sensor log work. Not pure algorithmic grind. Medium LC difficulty. They cared about talking through your reasoning more than hitting the optimal solution in the first 5 minutes.
Round 4: Virtual onsite (4 hours) Four back-to-back sessions: System design (60 min): design a distributed alerting pipeline for endpoint telemetry. Real-world problem, not a generic "design Twitter" prompt. Second coding round (60 min): two more problems, one threading/concurrency scenario. Behavioral / values fit (45 min): with a senior engineer, not HR. Details below. Cross-functional (30 min): basically a culture conversation with an eng manager from a different team.
Feedback came back in 6 business days. Got the offer. Total process was more rigorous than some big tech shops I've done, but also felt more purposeful. Problems connected to actual work.