CrowdStrike · Primly Community

CrowdStrike onsite / final round, how it really goes: timeline, format, what tanked people

mobile_mara · 5 replies

Did CrowdStrike's virtual onsite last quarter for a senior SWE role on their threat intelligence platform team. It's technically virtual but they call it an onsite internally. Here's the actual breakdown.

Format: four sessions over one day, back to back with 5-min breaks. Total block was 4.5 hours on my calendar.

Session 1 - Coding (60 min). Two problems. First was medium-tier, graph BFS variant. Second was a medium-hard simulation. Both in CoderPad. Had to run code against test cases they provided. The second problem has a trick: read the problem statement twice. Mine had a constraint buried in the second paragraph that changed the time complexity target.

Session 2 - System design (60 min). Domain-specific prompt (threat detection pipeline, real-time event processing). This went long. We spent the last 15 minutes on reliability and failure modes. Know how your design degrades gracefully under load.

Session 3 - Behavioral (45 min). With a senior engineer, not a people-ops person. That matters. They're probing your actual experience, not checking boxes. See the other thread on values for the question patterns.

Session 4 - Cross-functional / culture (30 min). Eng manager from a separate org. Very conversational. They wanted to understand how I collaborate cross-functionally. I asked about team structure and how decisions get made. That worked well.

Debrief timeline: 7 business days. Recruiter called with verbal offer, then formal offer packet came 2 days later. Total loop including debrief: about 40 days.

Things that I've heard tank people at the onsite: Failing to ask clarifying questions at the start of system design. Jumping in without scoping the problem reads as weak. Not having metrics in behavioral answers. "We improved performance" is incomplete. "We reduced detection latency from 4 seconds to 800ms" is what they want. Talking too fast in the behavioral round when nervous. They will interrupt to dig deeper so leave room.

Overall: rigorous but fair. The problems felt like they were actually connected to the work.

5 replies

corp_refugee

The buried constraint on the second coding problem is real. I had the same experience. If you're flying through it too fast you'll miss it and your solution will be wrong for 30% of inputs.

staff_steph

40 days total is actually pretty fast for a company that size. My FAANG loops were 60-90 days before ghosting became more normalized. CrowdStrike was similar, they moved quickly once I got to the offer stage.

visa_vik

Did they ask anything about right to work during the onsite itself or was that only at the recruiter stage?

ml_mike

Only at the recruiter call. Not mentioned again until the offer letter which had the standard verification language. Nothing awkward about it.

de_derek

Appreciate the detail on session 4. That round is the one that trips up ICs who've never had to explain how they work with non-engineers. Worth actually thinking about a concrete story for cross-functional collaboration before you go in.