Microsoft's Commerce + Ecosystems (C+E) division is looking to modernize its Billing system (Billing vNext) to handle billions in transactions with a new, highly scalable, cloud-native architecture. This involves a shift from a legacy .NET codebase to an event-driven microservices system, focusing on Transaction Orchestration and Domain-Driven Design to improve reliability and efficiency.
Requirements
- 5+ years technical engineering experience with coding in languages including, but not limited to, C, C++, C-Sharp, Java, JavaScript, or Python OR equivalent experience building backend services.
- 5+ years of experience building software on Cloud Platforms (Azure, AWS, or GCP)
- 2+ years of experience with event messaging or streaming architectures and technologies (Azure EventHub, Kafka, etc.)
- 2+ years of experience with big-data and analytics technologies: Azure Data Explorer, Apache Spark, etc.)
- Working experience in an agile development environment with a DevOps model
- Working experience and understanding of CI/CD pipelines.
- coding in languages including, but not limited to, C, C++, C-Sharp, Java, JavaScript, or Python
Responsibilities
- Design and develop large scale distributed software services and solutions.
- Drive engineering excellence by applying and modeling best practices in software design, code quality, reliability, performance, and security.
- Leads discussions for and owns the architecture of a products/solutions and creates proposals for architecture by testing design hypotheses and develop complex design specifications.
- Implement modern architecture – Help refactor a legacy .NET codebase into a config-driven, event‑driven microservices system. You’ll write services that publish and subscribe to event signals, enabling decoupled integration between billing and partner teams (Tax, Payments, Invoicing, etc.)
- Collaborate on building the orchestration engine that drives billing workflows as declarative configs rather than hard-coded logic. You’ll learn to manage distributed transactions (defining steps, handling failures with compensation) – a state-of-the-art approach for reliability.
- Evangelize Domain-Driven Design – Apply DDD principles by helping define clear domain boundaries and interfaces for each billing component.
- Develop telemetry into every feature you build. Help build the Insights component and similar tools to log events with rich metadata (correlation IDs, timestamps, etc.) to provide end-to-end insights into how financial scenarios are flowing throughout the stack.
Other
- Demonstrate technical leadership building mission-critical, high-scale services.
- Shape the next decade of Microsoft’s Billing system architecture.
- Innovate using modern engineering practices and AI-driven agentic workflows.
- Drive cross-team impact through deep technical collaboration.
- Deliver exceptional service quality through live-site excellence.
