Principal Software Engineer

Microsoft Microsoft · Big Tech · Redmond, WA +1 · Software Engineering

Principal Software Engineer to drive the architectural transformation of Conditional Access into a universal policy engine for users, workloads, and AI agents. This role will own the technical vision for scaling Conditional Access to meet the next generation of identity, including autonomous agents, continuous authorization, data-plane enforcement, and policy portability. The role involves defining architecture, owning technical strategy for the evaluation engine, designing next-generation policy models, leading CA-for-Agents vision, architecting agent identity evaluation, driving cross-org technical alignment, and influencing roadmaps for agent governance. It also includes setting standards for safe rollout, driving testability, and mentoring engineers.

What you'd actually do

  1. Define the architecture for Conditional Access at identity-platform scale
  2. Own the technical strategy for the CA evaluation engine — today processing millions of policy evaluations per second inside ESTS with sub-millisecond latency budgets
  3. Design the next-generation policy model: portable, data-driven policies that evaluate at token-time and at the data plane (GSA, MISE, resource providers)
  4. Lead the CA-for-Agents technical vision
  5. Architect how CA evaluates agent identities as first-class actors — spanning OBO, S2S, CUA, and agentic chaining scenarios

Skills

Required

  • Bachelor's Degree in Computer Science or related technical field AND 6+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python OR equivalent experience.
  • Ability to meet Microsoft, customer and/or government security screening requirements

Nice to have

  • Deep expertise in distributed systems, high-performance runtime engines, or policy/rules engines operating at extreme scale
  • Strong background in identity, authentication, authorization, or security infrastructure — you understand OAuth2/OIDC, token semantics, and Zero Trust principles
  • Fluency in C# and large-scale .NET service development; experience with ESTS or equivalent identity platforms is a strong plus
  • Architectural leadership
  • Track record of defining and driving multi-year technical strategies that span teams and organizations
  • Ability to make pragmatic tradeoffs between architectural purity and shipping velocity
  • Experience designing systems that evolve incrementally

What the JD emphasized

  • security screening requirements
  • policy evaluations per second
  • agent identities

Other signals

  • AI agents
  • policy engine
  • identity platform
  • distributed systems
  • high-performance