Senior Software Engineer

Senior individual contributor with 6 or more years of experience, at least 2 in a senior or lead capacity

LEVEL: Senior Software Engineer (individual contributor, with architectural authority and mentoring responsibility)

EXPERIENCE: 6+ years of professional software engineering, 2+ senior or lead on a production system

LANGUAGES: TypeScript (Node.js) and Python

STACK: TypeScript on Node.js and Python for services; React for the user interface; durable workflow orchestration; document, graph, and in-memory data stores; containers on Kubernetes in a major public cloud; distributed tracing and metrics throughout.

OWNERSHIP: One or more of: telemetry ingestion and normalization; workflow orchestration; the third-party integration framework; automated analysis; the response and enforcement engine

About the Role

We build a cyber-security platform that receives very large volumes of security telemetry from many customers, normalizes it into a common schema, runs automated analysis over it, and gives our operations teams the tools to reach and act on decisions. The platform serves many customers from a single deployment, so every pipeline stage has to hold up under strict tenant isolation, bursty traffic, third-party rate limits, and partial failure. The engineering problems are, first and foremost, distributed systems problems.

The team is small and senior in outlook. Engineers ship to production, own what they ship, and work directly with the operations teams who use the product every day. We hire for engineering quality above everything else.

You will own one or more of the subsystems that make the platform work under load. Ownership means the design, the delivery, the production operation, and the reliability numbers. We need someone who has already done this elsewhere: you designed a system that many people depended on, watched it break at scale, and rebuilt the parts that broke. You can hold a room of engineers to a high bar without slowing them down, and you will be expected to mentor associate engineers toward ownership of their own.

What we Require

• Six or more years of professional software engineering, including at least two in a senior or lead capacity on a production system.
• You designed and operated a system at scale. Be ready to give the numbers: throughput, data volume, tenants or users, latency percentiles, availability. Be ready to tell us what broke, what it cost, and what you changed. We weight the second half of that story more than the first.
• Distributed systems depth: queues and streams, workflow engines, retries and idempotency, consistency trade-offs, partial failure, backpressure, observability. You hold opinions on these earned through incidents, not only through reading.
• Strong TypeScript on Node.js and strong Python, with the judgment to know which to use where, and comfort reading and fixing code in either.
• Cloud and Kubernetes fluency. You have run services on Kubernetes in production and understand what the cluster does when you are not looking.
• Production ownership. You have defined service-level objectives, led incident response, run blameless post-incident reviews, and driven the follow-through.
• A proven record of excellence, evidenced by several of: promotions ahead of the typical cadence; ownership of a system critical to your employer's business; public work such as talks, papers, patents, or open-source projects with real users; a reputation among former colleagues we can verify by reference; a measurable outcome you drove, such as an order-of-magnitude cost, latency, or reliability improvement.