Drimva

Microsoft

Senior Software Engineer - HW/SW in Fleet Infrastructure

$120K–$261K

Redmond, WA +2 · On-site · Senior · Full-time · Posted Oct 26, 2026

Location
Redmond, WA
Mountain View, CA
New York, NY
Experience
4+ years of technical engineering experience with coding; equivalent experience accepted. Preferred alternatives: master's degree plus 3+ years, or bachelor's degree plus 5+ years, or equivalent experience.
Education
Bachelor's Degree in Computer Science or related technical field, or equivalent experience.

About the job

Designs and operates distributed systems and lab infrastructure to keep Microsoft 365 fleet operating systems, firmware, and security updates healthy, compliant, and current.

What you'll do

  • Build telemetry, analytics, and automation for fleet health, compliance, vulnerability remediation, and safe updates.
  • Manage and troubleshoot lab servers and networking infrastructure, and validate hardware, firmware, and software changes.
  • Develop AI-assisted incident and investigation experiences; partner across engineering teams and support live-site operations.

What they ask for

  • Bachelor's degree in Computer Science or a related technical field and 4+ years of technical engineering experience coding, or equivalent experience.
  • Ability to meet Microsoft, customer, and/or government security screening requirements, including the Microsoft Cloud Background Check.

Nice to have

  • Master's degree and 3+ years of technical engineering experience, or bachelor's degree and 5+ years, or equivalent experience.
  • Operating system internals and Windows/Linux troubleshooting; large-scale diagnostic data analysis and experience with Kusto/Azure Data Explorer or similar.

Pay

USD $119,800 - $234,700 per year (base salary); USD $160,200 - $261,000 per year (base salary) in the San Francisco Bay area and New York City metropolitan area.

Tools

C, C++, C#, Java, JavaScript, Python, Kusto/Azure Data Explorer, Linux

AI focus

Build AI-assisted experiences to accelerate investigation of patching failures, firmware issues, configuration drift, vulnerability exposure, and live-site incidents.

Model-written summary · the original posting is authoritative

First seen Oct 27, 2026 · Last verified Nov 5, 2026 (UTC)