Sr Technical Product Manager

Salary

Core Qualifications

Preferred Qualifications

Key Responsibilities

• •Define the long-term vision, strategy, objectives, and roadmap for Booking.com's next generation of engineering environments.
• •Develop a deep understanding of engineers' workflows, pain points, and unmet needs across development, testing, debugging, and service integration.
• •Define the target developer experience and the platform capabilities required to deliver it.
• •Establish clear product principles and investment priorities across areas such as environment fidelity, isolation, reproducibility, availability, speed, security, scalability, and cost.
• •Contribute to the broader Engineering Ecosystem strategy and align senior stakeholders around the transformation's direction, sequencing, and measures of success.
• •Translate an ambiguous, company-wide engineering problem into clearly defined product opportunities, strategic choices, and phased outcomes.
• •Partner with engineering leadership to shape the target platform architecture and make informed trade-offs between developer experience, technical feasibility, operational complexity, and cost.
• •Manage a long-term roadmap with dependencies across infrastructure, compute, networking, data, CI/CD, developer tooling, observability, security, and service ownership.
• •Define the transition from existing environments to the new platform, balancing long-term architectural goals with incremental value delivery.
• •Identify technical, organizational, and adoption risks early and establish mitigation plans with the relevant teams.
• •Treat engineers as customers and build a detailed understanding of their end-to-end workflows.
• •Enable engineers to create, configure, access, troubleshoot, and retire environments with minimal friction and cognitive overhead.
• •Ensure the product integrates effectively with IDEs, source control, CI/CD systems, internal developer platforms, observability tools, and relevant AI-assisted engineering workflows.
• •Support different engineering use cases while avoiding unnecessary fragmentation, bespoke solutions, and duplicated platform investments.
• •Partner with design and research specialists to make complex platform capabilities understandable and accessible.
• •Define the product's go-to-market, adoption, and migration strategy in partnership with platform teams and engineering communities.
• •Identify high-value early adopters and use their experience to validate assumptions, refine the platform, and demonstrate value.
• •Establish clear migration paths and incentives that enable teams to move away from legacy solutions safely.
• •Lead the change-management effort required to establish new engineering practices and platform standards.
• •Influence teams outside your direct area to adopt shared capabilities and contribute to a coherent engineering-environments ecosystem.
• •Define product and non-functional requirements for availability, performance, provisioning time, environment fidelity, scalability, security, privacy, observability, and cost efficiency.
• •Partner with engineering to establish appropriate service levels, operational ownership, support models, and platform-health measures.
• •Ensure the platform supports secure handling of code, credentials, test data, dependencies, and network access.
• •Balance engineer autonomy with organizational requirements for governance, standardization, and efficient infrastructure usage.
• •Make evidence-based decisions about when to build, buy, integrate, standardize, or retire capabilities.
• •Define primary, supporting, and counter-metrics for the platform.
• •Measure outcomes such as environment provisioning time, successful setup rate, developer wait time, workflow completion time, reliability, adoption, developer satisfaction, support burden, and infrastructure cost.
• •Combine telemetry, developer research, experiments, and operational data to identify friction and prioritize improvements.
• •Evaluate whether improvements translate into faster feedback loops, higher engineering quality, and reduced developer toil.
• •Communicate progress, evidence, risks, and investment recommendations clearly to engineering and product leadership.