Technical Program Manager II, Developer Experience & Client Platform

• Long-term incentive plan with a company performance-based cash payout
• Pension plan
• Private medical insurance
• 25 days PTO
• Meal allowance and flexible compensation plan (transport and nursery)
• Gym membership
• €450 to cover the costs associated with the adoption of a pet
• Annual €150 wellness reimbursement
• Flexible work hours, sometimes you’ll need to be in at certain times, but on the whole, we’re pretty flexible when it comes to managing workload and time
• Grab snacks and fresh fruit in our kitchen to keep yourself going
• Regular team activities, events, game nights, and more
• Dog-friendly office
• In the greater Barcelona area the first-year salary range is €51,837 - €62,832. Additionally, Rover offers a long-term incentive plan with a company performance-based cash payout and benefits to full-time employees.
• The cash compensation offered for this role will be dependent on the candidate's experience, qualifications, skills, and abilities as demonstrated in the interview and hiring process.

Every feature Rover ships travels the same path: the environment an engineer builds in, the CI that verifies high quality, the design system it's assembled from, and the release that puts it in front of pet parents and pet service providers. Two teams own that path: Developer Experience and Client Platform. Their vision is to make development faster, more reliable, and less painful for all makers.
As the TPM supporting these teams, your role is to help them deliver that vision. You'll join Rover's Technical Program Management team, a small and growing function that sits at the center of how engineering delivers complex, cross-functional work. TPMs here own how programs get executed, drive alignment across organizational boundaries, and bring structured thinking to the hardest problems on the roadmap.
Your focus is the platforms Rover's engineers build on. On the Developer Experience side, that means the environments, tooling, and pipelines engineers work in every day, including the AI-native tooling that is quickly becoming the center of how work gets done here. On the Client Platform side, it means the shared foundations of our web and mobile apps: the mobile frameworks and release infrastructure, our Next.js web platform, the design system used across every platform, and much of our Cloudflare routing.
What connects the two is that both teams build capabilities for makers. Their customers are internal: engineers today, and increasingly designers, PMs, and analysts who now build with AI too. So the hardest part of this job isn't tracking the work; it's helping make sure it's the right work. You'll aggregate needs across a large, fast-moving engineering organization, separate real friction from loud friction, and, critically, spot duplication. When teams quietly build their own versions of the same capability, you're the person who notices, names it, and works with the teams involved to get to one.
You'll bring the technical fluency to be a real partner to engineering, not just following a plan but pressure-testing it: reading a dependency chain, spotting gaps and risks early, then driving them to resolution. You'll develop the roadmap for your programs in partnership with the engineering managers leading these teams, and lead the highest-impact initiatives across both teams, including the work that falls between them. At Rover, that means working fluidly across Barcelona, Seattle, and the remote engineers in between.
That extends to how you use AI yourself. We're looking for someone who has gone past experimenting and is using these tools to change how their own work actually happens: synthesizing large volumes of stakeholder input, automating the recurring overhead of running a program, building workflows that save their teams time. What matters isn't how many tools you've tried; it's your point of view on where they create real leverage and where they don't.
This is a role for someone who is energized by making other builders faster and measured by whether they actually adopt what you ship, who moves easily between technical detail and organizational alignment, and who brings order to complexity without adding bureaucracy.

• Develop the roadmap for your programs with the engineering managers leading these teams, turning their priorities into a plan with clear objectives, sequencing, and measures of success.
• Drive that plan through to delivery: run the cadence, keep dependencies visible, identify risks early, and drive them to resolution or escalate with clarity and context when you can't.
• Lead the highest-impact initiatives across Developer Experience and Client Platform, including the work that falls between the two teams, coordinating with the teams that depend on them.
• Communicate change across the makers who depend on these platforms, from engineers to PMs, designers, and analysts, covering what is shipping, what is coming, and how teams should plan around it. Drive adoption of what these teams build, not just delivery of it.
• Aggregate what makers actually need. Run the feedback loops with developers and other internal users, turn dense, messy input into a prioritized recommendation, and lead the process that gets the engineering managers to a decision on where to invest.
• Surface duplication and help drive consolidation. As the organization builds quickly, find where the same capability is being built more than once, make the case for a single, better version, and work with the teams to get there.
• Define and report the metrics that tell us whether these platforms are working: adoption, cycle time, release health, developer satisfaction. Do your own data discovery to find the signal rather than waiting for a dashboard to be handed to you.
• Keep programs legible and the teams running well: maintain the project plans, status updates, and documentation others can actually find and use, and propose the process changes that fix inefficiencies you see across your teams and their partners.