Senior Software Engineer

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

Senior Software Engineer role focused on building and operating a high-throughput, low-latency, and highly available API gateway service for Microsoft Graph. The role involves end-to-end design, development, and operation of distributed services, leading design reviews, incident resolution, performance optimization, and strengthening observability. It requires strong coding skills in languages like C++, C#, Java, or Python, and experience with high-scale services.

What you'd actually do

  1. Own end-to-end design, development, and operation of distributed services processing millions of requests per second at 99.999% availability
  2. Lead and participate in design reviews for API gateway features including routing, throttling, caching, and protocol translation
  3. Investigate and resolve production incidents; participate in on-call rotation for mission-critical services
  4. Drive performance analysis and optimization to meet low single-digit millisecond latency targets and minimize added latency
  5. Champion engineering quality through automated testing, ensuring services are clean, well-factored, and well-tested

Skills

Required

  • Bachelor's Degree in Computer Science or related technical field AND 4+ 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

  • Practical experience operating high-scale services in production environments
  • Prior experience with performance analysis and optimization of web services
  • Prior experience building services which run on Microsoft Azure, Amazon Web Services, Google Cloud, or Oracle Cloud Infrastructure
  • Expertise in .NET writing high-performance, thread-safe code for low-latency systems
  • Experience with API development frameworks such as OData, GraphQL, or gRPC
  • Experience with protocols such as TLS and HTTP

What the JD emphasized

  • high-throughput
  • multi-tenant services
  • clean, well-factored, and well-tested code
  • low single-digit millisecond latency targets
  • 99.999% availability