Principal Software Engineer

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

Principal Software Engineer role focused on the security and privacy backbone of Microsoft's Intelligent Conversation and Communications Cloud (IC3). The role involves setting technical strategy and architecture for AI-driven, agentic security tooling, including vulnerability detection, posture assessment, and remediation. It also requires defining and enforcing quality gates, exercising compliance judgment across various standards (SOC 2, HIPAA, FedRAMP, etc.), and driving partner alignment. The position emphasizes applying AI/ML pragmatically to reduce false positives and improve remediation throughput, establishing evaluation and safety patterns, and leading incident response.

What you'd actually do

  1. Set the technical strategy and architecture for AEGIS — multi-service security platforms, AI agentic systems (agentic vulnerability detection, continuous assessment, triage, automated/recommended remediation), and the developer-facing surfaces hundreds of IC3 engineers depend on. Own the 12–24 month technical roadmap and trade-offs.
  2. Provide architecture depth and review rigor across IC3 security work — lead design reviews, security reviews, and threat-model deep dives; act as the final technical reviewer on the most ambiguous, highest-risk designs; raise the bar without becoming a bottleneck.
  3. Define and enforce quality gates — codify the policies, controls, telemetry, and pipeline checks (SFI waves, secure-by-default patterns, identity / network / data protections, container hardening, key management) that make consistent security execution the default across IC3 services.
  4. Exercise compliance judgment — translate SOC 2, ISO 27001, GDPR, HIPAA, FedRAMP, DoD IL5, and Microsoft internal standards (SFI, S360) into concrete engineering requirements and automation; make the call when policy, business risk, and engineering reality conflict.
  5. Drive partner alignment across IC3 and M365 — with security architects, MSRC, privacy, compliance, and service-owner leadership; resolve cross-team architectural disagreements; ensure SFI and incident-driven work lands as a coherent program, not isolated point fixes.

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
  • Ability to meet Microsoft, customer and/or government security screening requirements

Nice to have

  • Master's Degree in Computer Science or related technical field AND 8+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C#, Java, JavaScript, or Python

What the JD emphasized

  • highly regulated industries
  • zero-click compliance
  • material risk
  • hardest security and compliance calls
  • multi-year technical strategy
  • ambiguous, highest-risk designs
  • compliance judgment
  • policy, business risk, and engineering reality conflict
  • hardest security and compliance calls
  • AI/ML pragmatically and rigorously
  • measurable remediation throughput
  • human-in-the-loop patterns
  • incident leadership
  • security screening requirements

Other signals

  • AI-driven security tooling
  • agentic security tooling
  • zero-click compliance
  • AI/ML pragmatically and rigorously