Overview

We are looking for a principal engineer to build the monitoring, detection, automation, and response capabilities that protect Microsoft AI.

Microsoft AI develops and trains first-party models that Microsoft publishes and uses across products including Foundry, Copilot, Microsoft 365, and MDASH. The work spans model development and serving, large-scale compute, shared infrastructure, engineering systems, identity, data, and productivity services - the whole operational system that makes large-scale training, experimentation, and deployment possible. In the last year, MAI evolved from a research lab to a full production model factory. This role is designed for an engineer who has built or substantially transformed security monitoring and response capabilities and is prepared to do so again. You will set technical direction and build production systems across telemetry collection, security data, SIEM, detection engineering, hunting, SOAR, incident response, and AI-native security operations.

This role exists to build a function, not simply administer an existing SOC stack. You will help define what Microsoft AI must observe, which telemetry is collected and in what order, how detections are created and evaluated, how investigations are assembled, and where automated systems can safely recommend or take action. You will deploy and manage collection agents such as AzSecPack or comparable modern sensors, shape the SIEM and security-data architecture, and replace repeated manual work with reliable automation.

You will also bring patterns emerging in AI safety into security operations: continuously running evaluators or judges, evidence-grounded analysis, automated alerting, and agents that can investigate or respond within explicit authority. These systems must be engineered rather than merely prompted. They need evaluation sets, quality measures, scoped identities and permissions, traceable evidence, deterministic guardrails, human escalation, safe rollback, and clear rules for when automation may act. This entire category is new – we don’t expect you to be an expert on day one – but it’s helpful if you are (or can do some research before we chat).

This is a principal individual-contributor role that leads through architecture, code, technical judgment, prototypes, production ownership, and influence across a growing security-engineering team and partner organizations. MAI Security earns trust by staying close to the systems it protects and remaining accountable for detection and response outcomes, not just for raising risks. We build working systems, make coverage and residual risk explicit, and are honest about what our detections and agents can and cannot yet be trusted to do. The goal is to help Microsoft AI move quickly on frontier work by making security risk visible and manageable, creating safer options rather than new bottlenecks.

What You Will Do

Build the Security Telemetry Foundation

Define a security-observability strategy across identities, endpoints, hosts, workloads, containers, orchestration layers, networks, cloud control planes, developer systems, model infrastructure, data systems, and business applications.
Define telemetry and detection requirements for model and agent access, tool invocation, training and evaluation jobs, model and data artifacts, safety signals relevant to cyber defense, and anomalous use of high-consequence capabilities.
Deploy, integrate, and operate collection agents such as AzSecPack or modern equivalents. Establish rollout, upgrade, health, tamper-resistance, coverage, performance, and incident-use requirements.
Design reliable telemetry pipelines with clear schemas, enrichment, routing, retention, access control, data-quality checks, lineage, cost controls, and resilience to partial failure or adversarial interference.
Identify high-consequence visibility gaps, work with system owners to close them, and make monitoring requirements part of platform and service architecture.
Establish measures for coverage, freshness, completeness, health, query performance, detection dependencies, and operational value.