Principal Software Engineer

MicrosoftRedmond, WA

About The Position

The Policy & Configuration team is seeking a Principal Software Engineer to work on the deployment control plane for Microsoft Threat Protection. This team is responsible for how security services are deployed across various regions and sovereign clouds. The role involves replacing a legacy configuration system with .NET Aspire, integrating deployment rules, data-residency constraints, and compliance policies into the toolchain using Roslyn analyzers, CI gates, and typed annotations. This approach aims to catch deployment issues at compile time rather than deploy time. The position involves significant architectural work and cross-organizational advocacy with partner platform teams, with all tool developments being pushed upstream into Azure and .NET. It is a small team with high leverage.

Requirements

  • 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.

Responsibilities

  • Design the migration path from a legacy deployment SDK to .NET Aspire. Define the publishing hooks, plan the incremental cutover, and solve the coexistence problems that come from running old and new systems side by side in production.
  • Drive adoption across organizational boundaries. Work directly with Azure platform and .NET partner teams to push deployment capabilities upstream. The goal is getting the right primitives into the infrastructure so the team stops maintaining what should be a platform feature.
  • Encode compliance and deployment standards into the toolchain. Data-residency rules, security policies, and configuration constraints that replace tribal knowledge with .NET analyzers, CI gates, and typed annotations. What was once a wiki becomes a compiler check.
  • Own architecture decisions for the deployment configuration domain. Evaluate build-vs-contribute upstream tradeoffs, lead design reviews, and set the technical direction.
  • Shape the developer experience so service teams deploy through standard .NET code. No specialized SDKs. No deployment-specific tooling to learn. The ordinary path is the correct path.
  • Build machine-readable interfaces - MCP servers, structured APIs - so AI agents and human engineers work against the same deployment control plane

Benefits

  • Certain roles may be eligible for benefits and other compensation. Find additional benefits and pay information here: https://careers.microsoft.com/us/en/us-corporate-pay
© 2024 Teal Labs, Inc
Privacy PolicyTerms of Service