Technical Program Manager III

About the role
Our Platform Engineering team builds the shared services, tooling, and infrastructure that every product team depends on — and as the Developer Advocate for the platform, you will be the voice of those developers. You'll gather their needs, turn them into a prioritized and transparent roadmap proposal, and run the programs that keep them productive.
This is a hybrid role spanning developer relations, product ownership, and technical program management. It suits someone who is equally comfortable running office hours with engineers and running a disciplined prioritization process — and who believes developer time is the most valuable resource on the platform.
What you'll do
Requirements & insights
- Own the intake process for platform requests, feedback, and escalations — one funnel, complete context, nothing lost in DMs.
- Run office hours, interviews, and surveys with dependent teams; synthesize patterns into regular "voice of the developer" reports.
- Feed prioritized, evidence-backed recommendations into platform leadership and product planning.
Prioritization & planning
- Maintain and publish a transparent prioritization rubric (severity, impact, effort, sequencing) that resolves "everything is urgent."
- Partner with program managers and engineering leads on capacity planning, release sequencing, and trade-off decisions before commitments are made.
- Make every prioritization decision and its rationale visible to the teams affected.
Program management
- Run the platform support program: SLAs, escalation paths, request-quality feedback, and reporting.
- Lead adoption and migration programs for platform tooling and services, from communication plan to completion metrics.
- Maintain the platform ownership registry so teams always know who owns what.
Enablement & communication
- Produce developer-facing content: changelogs, migration guides, onboarding paths, and self-service documentation.
- Build dashboards that make platform health visible — adoption, cycle time, backlog aging, satisfaction.
- Represent the platform in cross-team forums; celebrate wins and communicate changes early.
What success looks like
- Requests are triaged quickly with complete information; SLAs are tracked and published.
- Prioritization is predictable and documented; disputes are resolved with data, not escalation.
- Adoption of platform tooling grows measurably; migrations complete on schedule.
- Developers report — in a quarterly pulse — better responsiveness and predictability from the platform team.
First 90 days: map stakeholders and intake channels; publish the rubric and ownership registry v1; stand up reporting; take over and deliver two in-flight programs.
What you bring
- 5+ years across developer relations, platform product management, technical program management, or developer experience.
- Technical fluency — microservices, Kafka/Postgres, Kubernetes, CI/CD, observability. You can read a repo, a Helm chart, and an epic without hand-holding (no production coding required).
- Hands-on experience with prioritization frameworks (RICE/WSJF) and capacity planning.
- Exceptional written communication; the team runs on Slack, Jira, and Confluence.
- A track record of running cross-team programs with measurable outcomes.
- Comfort operating amidst production escalations and competing stakeholder priorities.
Nice to have
- Built or ran a developer experience / developer relations function for an internal platform.
- Experience with on-call or support operations (severity models, SLAs, rosters).
- Familiarity with AI-assisted developer workflows and tooling.
- Experience in fast-moving, infrastructure-heavy or hardware-adjacent domains