Staff Software Engineer, Huntress

• Deep experience designing, building, and operating production distributed systems at scale, primarily in Go, with the range to work across several layers of the stack
• You have replaced or substantially re-architected a live, high-throughput system without breaking its consumers, and you can walk us through how you proved the new path was equivalent, staged the cut-over, and decided it was safe to retire the old one
• Experience with high-volume event or data pipelines, and a good feel for how they behave under load: where things queue, where they fall behind, and what happens to correctness when they do
• Strong operability instincts. You design observability in rather than retrofitting it, and you've built alerting that catches the absence of expected work, not just errors
• Demonstrated technical leadership across team boundaries. You've set a direction that other teams had to build against and raised the engineering bar around you, without needing positional authority
• Judgment about production quality: when a system is good enough to ship, when it needs more evaluation, and when it shouldn't ship at all
• Hands-on experience with AI coding tools, and a point of view on using them well, where correctness is a security outcome
• We don't expect prior experience with all of it, and we're not screening on the list; Go is the one language we'll assess directly in interviews. You should be someone who likes being fluent across a broad stack rather than being specialized in one corner of it

Desirable

• Reports to: Engineering Manager
• Huntress protects the small and mid-sized businesses that attackers assume can't afford a security team. The Detection Platform team builds the engines and pipelines that turn billions of raw telemetry events into the signals our 24/7 SOC acts on. Every detection Huntress ships, across endpoint, identity, SIEM, and third-party EDR, runs through systems this team owns. We measure ourselves on two things: time to detection and detection engine uptime
• We're hiring a Staff Software Engineer to help build and rebuild these systems without disrupting the SOC that depends on them, and to make their behavior predictable under load. This is a hands-on technical leadership role: you'll lead major workstreams, set direction that other engineering teams build against, and write and review production code every week
• Detection engine and pipeline modernization. We're rewriting our detection engine to support the full Sigma v2 specification, including stateful correlation of patterns across many events over time. In parallel, we're reworking several existing detection pipelines and building new ones, moving off the bespoke per-product detectors we've accumulated and onto a common platform. You'll lead major workstreams across both and own the validation approach that proves a reworked pipeline still behaves like the one it replaces, so we can turn old paths off knowing we haven't lost anything
• Reliability and behavior under load. A detection pipeline that quietly stops producing signals is worse than one that crashes loudly, and detection volume spikes for reasons we don't always control. You'll build the guarantees that make quiet failure impossible: end-to-end latency measurement, liveness coverage, and alerting that fires when expected work stops arriving. You'll also build the mechanisms that keep a spike bounded and recoverable
• Event schemas and data contracts. Our schema and transformer layer are what several other engineering teams build their detections against. You'll help drive toward a coherent internal standard and build the validation and drift-detection tooling that catches upstream changes before they break detections
• You'll work primarily in Go across our detection engines, pipelines, and the services around them, with Kafka, Temporal, Redis, ClickHouse, Elasticsearch, and Kubernetes across AWS and Azure. Some of our pipeline and application code is Ruby on Rails. Detection logic is written in Sigma