Windows & Devices Developer Experience Lead
Job details
- Work mode
- Hybrid
- Level
- Staff / principal
- Posted
- Nov 18, 2026
- Last confirmed open
- Nov 19, 2026
About this role
Overview Microsoft Customer and Partner Solutions-Core (MCAPS) accelerates customer outcomes and business growth. By uniting product, engineering, marketing, sales, customer success, and partners around a common customer mission, we help customers realize value faster and turn innovation into measurable business impact.
Through deep technical expertise and differentiated go-to-market execution, we win competitively, capture market share, and scale repeatable growth motions. We differentiate through value creation - delivering world-class, AI-powered customer experiences that accelerate adoption, strengthen loyalty, and create sustainable competitive advantage, driving growth that outpaces the market.
The Strategy & Transformation team identifies emerging opportunities and drives programmatic transformation across MCAPS Core, our customers, partners, and account teams. We design and test new programs, operating models, and customer experiences, then we scale what works to deliver AI-first transformation, customer growth, and measurable commercial impact.
The Developer Center of Excellence is seeking a Windows & Devices Developer Experience Lead (Principal Technical Program Manager) with expertise in hardware, operating systems, and developer technologies to own the Windows & Devices developer-friction domain.
This role is responsible for developing a detailed understanding of how developers experience Windows and Windows devices, identifying the technical and experiential friction that affects developer preference, productivity, and adoption, and translating those signals into actionable opportunities for product and engineering teams.
The developer experience is changing rapidly. AI-assisted development, agentic workflows, local and hybrid AI execution, specialized compute, cloud development, and evolving engineering roles are changing what developers need from their operating system and devices. At the same time, new Windows and device capabilities create opportunities to rethink what a differentiated developer experience can look like.
The Windows & Devices Developer Experience
- Lead will translate these evolving developer needs into opportunities to improve the Windows & Devices developer experience.
- They will work across Windows, devices, developer tools, cloud services, engineering teams, customers, and technical communities to identify recurring friction, understand root causes, develop technical hypotheses, and validate potential interventions.
- This is not a traditional technical program management role focused on executing an established roadmap.
The Windows & Devices Developer Experience
- Lead will build and shape the developer-friction function, bringing an informed technical perspective on existing challenges, emerging technologies, and opportunities for Windows & Devices.
- This includes leading technical engagement with NVIDIA and anticipating how evolving developer workflows, AI capabilities, and compute architectures can create differentiated developer experiences and new growth opportunities.
- This role requires technical expertise, strategic thinking, and the ability to independently navigate complex, ambiguous challenges.
- Success requires translating developer signals into detailed technical investigations, connecting issues across technologies and organizations, and driving initiatives from problem definition through technical validation and product recommendation.
- The role also requires independently establishing stakeholder relationships, defining priorities, developing actionable plans, and measuring impact with limited direction.
- Microsoft’s mission is to empower every person and every organization on the planet to achieve more.
- As employees we come together with a growth mindset, innovate to empower others and collaborate to realize our shared goals.
- Each day we build on our values of respect, integrity, and accountability to create a culture of inclusion where everyone can thrive at work and beyond.
Responsibilities
Own Windows & Devices Developer Friction
- Serve as the technical owner for Windows & Devices developer friction within the Developer Center of Excellence.
- Develop an understanding of how developers experience Windows and Windows devices across their end-to-end development workflows.
- Identify recurring friction affecting developer productivity, preference, adoption, and satisfaction.
- Distinguish isolated product issues from patterns that indicate broader technical or experience gaps.
- Establish root causes by connecting developer evidence with architecture, product behavior, technical dependencies, and evolving development patterns.
- Translate recurring friction into clear technical problem statements, hypotheses, requirements, and areas for potential investment.
- Prioritize Windows & Devices developer-friction opportunities based on potential impact.
Understand the AI-Era Developer
- Develop an understanding of how AI is changing developer roles, responsibilities, workflows, and technical environments.
- Examine how AI agents and automation change the way developers build, test, debug, orchestrate, deploy, and operate software.
- Anticipate what these changing workflows mean for operating systems, devices, developer tools, security, compute, and cloud integration.
- Identify emerging developer requirements before they become widespread sources of friction.
- Translate changes in developer behavior into concrete implications for Windows & Devices experiences.
Build Technical Expertise Across Devices, Operating Systems, and Cloud
- Develop and maintain technical depth across Windows, developer tooling, Linux development on Windows, cloud development, containers, virtualization, AI development, local compute, edge execution, and distributed cloud architectures.
- Apply technical expertise in device hardware, chipsets, and compute architectures, including CPUs, GPUs, NPUs, accelerators, memory, storage, and networking, to understand their impact on developer workloads and experiences.
- Evaluate how different device configurations, hardware capabilities, and compute architectures support specific developer workloads, use cases, and evolving development environments.
- Evaluate how local, edge, hybrid, and cloud execution affect developer scenarios.
- Understand the technical and economic tradeoffs associated with where AI workloads run, including performance, latency, security, privacy, reliability, resource consumption, and cost.
- Translate rapidly evolving hardware and AI capabilities into meaningful developer scenarios rather than treating new technology as an outcome in itself.
Lead Technical Ecosystem Engagement and Strategic Opportunities
- Own technical engagement with NVIDIA, establishing relationships with technical stakeholders and identifying opportunities to improve Windows & Devices developer experiences.
- Anticipate emerging developer workflows, AI capabilities, and compute architectures to identify opportunities for Windows & Devices differentiation.
- Engage with hardware partners, engineering teams, and developer ecosystem stakeholders to understand evolving technologies, technical dependencies, and emerging developer needs.
- Translate technical and ecosystem insights into actionable recommendations and growth opportunities that influence developer preference, adoption, and behavior.
Connect Developer Friction to Existing Product Investments
- Bring Windows & Devices developer-friction evidence into existing product and engineering initiatives rather than creating unnecessary parallel experiences.
- Partner with Windows, device, engineering, developer-tool, and cloud teams to determine where developer evidence should inform product priorities and roadmap decisions.
- Identify where emerging capabilities could remove existing developer friction or create differentiated developer experiences.
- Provide technical evidence and recommendations that help product teams understand t