Own the internal DevEx platform roadmap backlog, translating organizational strategy and R&D needs into prioritized initiatives that deliver measurable value across the R&D organization. Work closely with internal customers within R&D, aligning tightly with the External developer PM
Key Responsibilities
Requirement Definition (the core of the role): Create and own the requirements for the platform solutions we build for our developers. You continuously synthesize and prioritize four inputs into a clear, coherent product direction:
Strategic priorities – the direction set with the Chief Architect on where platform investment should go.
Organizational needs – the recurring challenges and demands surfaced by R&D divisions and their leadership.
User feedback – direct input from the internal developers who use the platform day to day.
Architectural guidance – professional input from Architects, both within the Chief Architect Office and across the product-specific architecture teams.
Platform Product Ownership: Serve as the product lead for the internal platforms and tools our engineering teams build for our developers – for example, our agentic developer platform, among a growing set of developer-experience capabilities. Define what each should do and the outcomes it should deliver, and keep the portfolio aligned to a shared vision.
Prioritization & Roadmap: Maintain a clear, well-reasoned view of what matters most and why, so platform teams always know what to build next and the organization understands the rationale.
Cross-Functional Alignment: Drive the work processes that turn inputs into shipped platform capabilities, partnering across engineering managers, directors, and architects. Set direction, align stakeholders, and keep initiatives moving forward.
Feedback & Impact: Establish durable channels to collect and synthesize developer feedback and adoption signals, feed them back into the requirements, and demonstrate the platform's impact on developer productivity.
Key Responsibilities
Requirement Definition (the core of the role): Create and own the requirements for the platform solutions we build for our developers. You continuously synthesize and prioritize four inputs into a clear, coherent product direction:
Strategic priorities – the direction set with the Chief Architect on where platform investment should go.
Organizational needs – the recurring challenges and demands surfaced by R&D divisions and their leadership.
User feedback – direct input from the internal developers who use the platform day to day.
Architectural guidance – professional input from Architects, both within the Chief Architect Office and across the product-specific architecture teams.
Platform Product Ownership: Serve as the product lead for the internal platforms and tools our engineering teams build for our developers – for example, our agentic developer platform, among a growing set of developer-experience capabilities. Define what each should do and the outcomes it should deliver, and keep the portfolio aligned to a shared vision.
Prioritization & Roadmap: Maintain a clear, well-reasoned view of what matters most and why, so platform teams always know what to build next and the organization understands the rationale.
Cross-Functional Alignment: Drive the work processes that turn inputs into shipped platform capabilities, partnering across engineering managers, directors, and architects. Set direction, align stakeholders, and keep initiatives moving forward.
Feedback & Impact: Establish durable channels to collect and synthesize developer feedback and adoption signals, feed them back into the requirements, and demonstrate the platform's impact on developer productivity.
Requirements:
AI-first mindset: You reach for AI as the default way to work and to solve problems, stay current as the tools evolve, and think about how AI reshapes what our platforms should do for developers. As with every role in our engineering organization, this is a baseline expectation, not a bonus.
Development expertise: Deep understanding of software development and development processes, grounded in hands-on experience – most likely as an engineer, engineering leader, or architect, though what matters is genuine fluency in how developers work and what they need.
Passion for building products: A real drive to build products – to focus on impact and the broad scheme of things, define the what and the why, and leave the implementation details to the teams that own them. This is what sets the role apart, and it is what we are explicitly selecting for.
Platform experience: Experience building or shaping internal platforms and developer tools – whether as a developer, an engineering manager, or a product lead. The perspective matters more than the prior title.
Seniority & independence: Proven ability to set an agenda, operate autonomously, and manage work processes that span multiple functions – engineering managers, directors, and architects – with minimal supervision.
Agile mindset: Comfort with iteration, continuous learning, and adjusting direction as you gather evidence; you make progress amid ambiguity rather than waiting for perfect information.
Passion & curiosity: A genuine curiosity that drives continuous learning – about developers, technologies, and how to make an organization more effective.
Cross-functional influence: Able to influence without authority and to align senior stakeholders around shared priorities.
Communication: Excellent communication, presentation, and prioritization skills, with fluent English.
AI-first mindset: You reach for AI as the default way to work and to solve problems, stay current as the tools evolve, and think about how AI reshapes what our platforms should do for developers. As with every role in our engineering organization, this is a baseline expectation, not a bonus.
Development expertise: Deep understanding of software development and development processes, grounded in hands-on experience – most likely as an engineer, engineering leader, or architect, though what matters is genuine fluency in how developers work and what they need.
Passion for building products: A real drive to build products – to focus on impact and the broad scheme of things, define the what and the why, and leave the implementation details to the teams that own them. This is what sets the role apart, and it is what we are explicitly selecting for.
Platform experience: Experience building or shaping internal platforms and developer tools – whether as a developer, an engineering manager, or a product lead. The perspective matters more than the prior title.
Seniority & independence: Proven ability to set an agenda, operate autonomously, and manage work processes that span multiple functions – engineering managers, directors, and architects – with minimal supervision.
Agile mindset: Comfort with iteration, continuous learning, and adjusting direction as you gather evidence; you make progress amid ambiguity rather than waiting for perfect information.
Passion & curiosity: A genuine curiosity that drives continuous learning – about developers, technologies, and how to make an organization more effective.
Cross-functional influence: Able to influence without authority and to align senior stakeholders around shared priorities.
Communication: Excellent communication, presentation, and prioritization skills, with fluent English.
This position is open to all candidates.
