Design a Secure Event Messaging Platform
A publish-subscribe (pub/sub) platform is the plumbing between services. A producer writes an event to a named topic and moves on. Any number of consumers read that topic on their own schedule, and the producer never needs to know who they are. Kafka, Google Pub/Sub and Amazon Kinesis are the well-known versions. At CrowdStrike this has come up as a Senior take-home. One candidate in January 2026 described getting a set of requirements for an event system, writing the design up, then spending about two hours walking two engineers through it. The loop ended in an offer. A 2026 SWE candidate described a smaller cousin, a vague low-level design exercise for a pub/sub system with concurrency and ordering. This lesson covers both, with the low-level version near the end.
The doc itself has a fairly standard shape. Cover the requirements and assumptions, capacity estimates, the data flow from publish to delivery, the event and subscription data model and the API. Then say how the design meets its security and availability goals. This lesson follows that order, so it doubles as an outline for the doc.
CrowdStrikePremium lesson · System design round
The CrowdStrike design, worked end to end.
- The API and data modelSystem design · Frequently asked
- The design, drawn out1 diagram
- 6 deep divesWith the tradeoffs
$49 a year · all 107 companies · instant access
20,000+ candidate reports · guide updated
CrowdStrike interview guideKnow what CrowdStrike asks before you walk in.
28 coding · 4 system design · 15 behavioral questions
Get their questions first.
InterviewLegend is independent and not affiliated with or endorsed by any company it covers.