10+ years in technical program management, with at least 3 years managing programs that span 5+ engineering teams with competing priorities and hard dependencies .
Deep technical fluency in infrastructure and platform engineering domains . You don't need to write Terraform or tune database queries, but you must be able to follow and contribute to conversations about SLO error budgets, CI/CD pipeline design, database migration risks, security scanning trade-offs, and incident response — well enough to identify dependencies, ask the right questions, and recognize when something is off track .
Demonstrated ability to influence without authority . You will have no direct reports among the domain leads . Your effectiveness comes from relationship skills, clarity of communication, and earned credibility .
Strong stakeholder management skills — comfortable operating at the Director/VP level for leadership communication and at the senior engineer level for technical coordination (p. 3).
Experience with metrics, dashboards, and data-driven decision support . You will own a cross-domain dashboard and need to synthesize complex data into clear narratives .
Excellent facilitation skills — running focused, decision-oriented meetings with senior technical leaders . You know how to draw out the right information, drive to decisions, and end on time .
Experience with organizational change — guiding teams through operating model transformations, not just feature delivery .
Strongly Preferred
Background in SRE, platform engineering, DevOps, or infrastructure organizations . A TPM who has worked in reliability or platform contexts will ramp faster and earn credibility with our technical leads more quickly than someone from a pure product TPM background .
Experience with incident management processes and post-incident reviews . Understanding cross-domain response under pressure helps you design governance that works in practice, not just in planning sessions .
Familiarity with SRE methodologies (SLOs/SLIs/error budgets), DORA metrics, chaos engineering, and platform-as-a-product principles .
Experience working across both proactive engineering functions (platform, reliability, security, quality) and reactive operational functions (support, defect resolution) — or similar environments with mixed proactive/reactive team dynamics .
Track record of simplifying processes, not adding them . We value lightweight governance and you should too