Principal Software Engineer, AI SIEM

SentinelOne is a company at the intersection of AI and security, pioneering a new operating model for cybersecurity. As a Principal Software Engineer, AI SIEM, you will be responsible for driving architectural decisions across the AI SIEM system, ensuring that data ingestion, analyst workflows, and detection engines are effectively integrated and optimized.

Responsibilities:

• Build a working mental model of the full system, including ingest and storage, query and retrieval, analyst-facing workflows (alerts, findings, assets, incidents), and the detection engines (rule-based and beyond), and use it to identify where architecture is solid, where it's fragile, and where teams are unknowingly duplicating effort or leaving gaps between their boundaries
• Drive cross-team architectural decisions that affect multiple parts of the system at once, for example, how ingest-time enrichment should relate to detection logic, or how detection output should shape what an analyst sees and can act on
• Partner with the engineering leads of each pillar (data platform, analyst experience, detection engines) as a peer thought partner, not a top-down authority, influencing through technical credibility and clear reasoning, not mandate
• Identify and prioritize the highest-leverage architectural investments across the system, and make the case for them to engineering leadership and product
• Get hands-on where it matters: prototype, review, and occasionally build the connective tissue between pillars when no single team naturally owns it
• Establish and champion cross-cutting technical standards, for APIs, data contracts, and service boundaries, that keep independently-developed pillars interoperable as they evolve
• Mentor senior and staff engineers across teams, raising the bar for architectural thinking org-wide, not just within one team
• Represent the technical health of the overall system in planning and leadership conversations, translating "what's exceptional, what's a gap, what's redundant" into a roadmap

Requirements:

• Deep experience (15 or more years) building and operating large-scale distributed backend systems, with direct experience in at least two of: high-throughput data ingest/storage, query engines, or detection/rules systems
• A demonstrated track record of reasoning about systems at the architecture level, not just implementing a spec, but identifying where a system's boundaries are wrong, where responsibilities overlap, and where they leave gaps
• Experience designing APIs and service contracts that need to hold up across teams and years, not just within one codebase
• Comfort operating without a single clear chain of command, influencing peer teams and senior engineers through the strength of your reasoning
• A four-year degree in Computer Science or equivalent practical experience
• Familiarity with security operations concepts (alerts, findings, assets, incidents, detection rules) is preferred; if you don't have direct SIEM/XDR background, you should be someone who can get fluent in a new domain fast
• Experience with modern cloud infrastructure and data-intensive systems (distributed storage, high-cardinality querying, streaming pipelines) is preferred; specific tools matter less than demonstrated judgment about tradeoffs at scale
• Exposure to both rule-based and ML/AI-driven detection approaches is a plus, but the more important trait is being able to reason about when each is the right tool