Job Description

Locations

• Redmond, WA, US
• Charlotte, NC, US

Salary

Skills Required

• engineeringintermediate
• revenue managementintermediate
• financial complianceintermediate

Required Qualifications

• Bachelor's Degree AND 4+ years experience in engineering, product/technical program management, data analysis, or product development, OR equivalent experience. (experience, 4 years)
• 2+ years experience managing cross-functional and/or cross-team projects. (experience, 2 years)
• 2+ years experience managing cross-functional and/or cross-team projects. (experience, 2 years)
• Ability to meet Microsoft, customer and/or government security screening requirements are required for this role. These requirements include but are not limited to the following specialized security screenings: Microsoft Cloud Background Check: This position will be required to pass the Microsoft Cloud background check upon hire/transfer and every two years thereafter. (experience)
• Technical Program Management IC4 - The typical base pay range for this role across the U.S. is USD $119,800 - $234,700 per year. There is a different range applicable to specific work locations, within the San Francisco Bay area and New York City metropolitan area, and the base pay range for this role in those locations is USD $160,200 - $261,000 per year. (experience)
• 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 (experience)
• This position will be open for a minimum of 5 days, with applications accepted on an ongoing basis until the position is filled. (experience)

Preferred Qualifications

• Bachelor's Degree AND 8+ years experience in engineering, product/technical program management, data analysis, or product development, OR equivalent experience. (experience, 8 years)
• Bachelor's Degree AND 8+ years experience in engineering, product/technical program management, data analysis, or product development, OR equivalent experience. (experience, 8 years)
• 6+ years experience managing cross-functional and/or cross-team projects. (experience, 6 years)
• 6+ years experience managing cross-functional and/or cross-team projects. (experience, 6 years)
• 1+ year(s) experience reading and/or writing code (e.g., sample documentation, product demos). (experience, 1 years)
• 1+ year(s) experience reading and/or writing code (e.g., sample documentation, product demos). (experience, 1 years)
• Experience with revenue management, billing, invoicing, tax, or payments platforms operating at global scale. (experience)
• Experience with revenue management, billing, invoicing, tax, or payments platforms operating at global scale. (experience)
• Familiarity with financial compliance and control requirements in a large enterprise engineering environment. (experience)
• Familiarity with financial compliance and control requirements in a large enterprise engineering environment. (experience)
• Strong technical communication and stakeholder management skills, with a track record of influencing across organizational boundaries without direct authority. (experience)
• Strong technical communication and stakeholder management skills, with a track record of influencing across organizational boundaries without direct authority. (experience)

Responsibilities

• You will drive large, cross-group technical programs end to end — from ambiguous problem statement to shipped outcome — spanning multiple engineering teams, finance stakeholders, and partner organizations across Microsoft's commerce ecosystem.
• You will drive large, cross-group technical programs end to end — from ambiguous problem statement to shipped outcome — spanning multiple engineering teams, finance stakeholders, and partner organizations across Microsoft's commerce ecosystem.
• You will own the program rhythm for initiatives that modernize revenue recognition, billing, and financial orchestration at Azure scale, defining milestones, managing dependencies, and making trade-offs visible before they become escalations.
• You will own the program rhythm for initiatives that modernize revenue recognition, billing, and financial orchestration at Azure scale, defining milestones, managing dependencies, and making trade-offs visible before they become escalations.
• Shape solutions alongside engineers and architects from the first whiteboard — stress-testing how designs fit together across teams and surfacing misalignment while it costs a conversation to fix, not a release.
• Shape solutions alongside engineers and architects from the first whiteboard — stress-testing how designs fit together across teams and surfacing misalignment while it costs a conversation to fix, not a release.
• Serve as the primary interface between engineering and business, finance, and compliance stakeholders — turning their requirements into build-ready specifications and system behavior into terms they can trust and sign off on.
• Serve as the primary interface between engineering and business, finance, and compliance stakeholders — turning their requirements into build-ready specifications and system behavior into terms they can trust and sign off on.
• Make the hard trade-offs between speed, cost, and correctness explicit, drive them to a decision, and carry the rationale to leadership in writing that holds up.
• Make the hard trade-offs between speed, cost, and correctness explicit, drive them to a decision, and carry the rationale to leadership in writing that holds up.
• Prototype with AI before committing engineering time — working demos and agents that settle open questions, pressure-test designs, and show stakeholders the answer instead of describing it.
• Prototype with AI before committing engineering time — working demos and agents that settle open questions, pressure-test designs, and show stakeholders the answer instead of describing it.
• Rethink how the work itself gets done: identify where AI and agentic workflows can absorb recurring product, program, and validation work, prove it on your own workload first, and scale what works.
• Rethink how the work itself gets done: identify where AI and agentic workflows can absorb recurring product, program, and validation work, prove it on your own workload first, and scale what works.
• Define what "ready to ship" means for changes where errors are costly, and hold releases to that bar.
• Define what "ready to ship" means for changes where errors are costly, and hold releases to that bar.
• Run disciplined, lightweight execution — dependencies, risks, and decisions visible at all times, with an owner and a date on everything open.
• Run disciplined, lightweight execution — dependencies, risks, and decisions visible at all times, with an owner and a date on everything open.
• Embody Microsoft's culture and values — a growth mindset, customer obsession, diversity and inclusion, One Microsoft collaboration, and making others better through your work.
• Embody Microsoft's culture and values — a growth mindset, customer obsession, diversity and inclusion, One Microsoft collaboration, and making others better through your work.

Benefits

• general: Flexibility: Balance what matters—your work, your life, and your team—through trust, autonomy, and shared accountability
• general: Growth: Stretch your skills, expand your impact, and grow with support that meets you where you are
• general: Wellbeing: Support for your body, mind, and financial future—so you can stay energized and do your best work
• general: Community PCS: Find your people, build your network, and feel supported every step of the way

Travel Requirements

Less than 25%

Tags & Categories