Senior Technical Program Manager II
Posted 3
views
Summary
Fetch is hiring a Senior TPM to help build a new Data Product Partner operating model: an internal coordination role connecting client-facing teams (Sales/GTM, TAM, SE) with data product and delivery infrastructure teams, handling escalations, cross-team prioritization, incident response, and roadmap routing, while leveraging AI tools like Copilot, ChatGPT, and Notion AI.
Overview
Fetch is establishing a new Data Product Partner operating model to serve the partners who rely on our data products. In this model, client-facing roles sit on the business side: Sales/GTM owns the commercial path, the Technical Account Manager (TAM) orchestrates the ongoing account relationship, and Solutions Engineering (SE) owns the partner-facing technical path from discovery through configuration, launch, and first-line triage. Behind them sit the teams that own the shared systems: the Data Product teams own the data assets, models, definitions, and product behavior, and AMPS owns the shared export and delivery infrastructure.
The Data Product Technical Program Manager is the internal coordination pivot that connects those client-facing roles to the teams that own the shared data products and delivery infrastructure. This is an escalation and coordination role, not a checkpoint for standard work. Standard qualification, configuration, and triage flow through Sales/GTM, TAM, and SE without TPM involvement. The TPM enters when the standard path breaks, when work crosses teams, when one partner's request would change a shared product, when prioritization is required, or when there is material delivery risk.
Because this team and operating model are new, the TPM will help shape how the model works in practice: sharpening the boundaries between roles, building the cadences and artifacts that keep cross-team work visible, and steadily routing recurring partner needs into the roadmap. This is a high-leverage role for someone who is energized by ambiguity, disciplined about when to engage, and effective at driving outcomes across teams they do not own.
Responsibilities
- Act as the internal cross-team coordination pivot connecting client-facing partner roles (Sales/GTM, TAM, SE) with the internal teams that own shared data products (Data Product teams) and export and delivery infrastructure (AMPS).
- Lead cross-team planning when work spans multiple Data Product teams, AMPS, or feature/capture teams.
- Own prioritization and dependency management for shared-product changes, balancing partner needs against roadmap and engineering capacity.
- Coordinate engineering estimates and secure internal approval before nonstandard or unsupported commitments are made to partners.
- Lead the internal response for major, recurring, or multi-partner incidents, coordinating diagnosis across SE, Data Product teams, and AMPS and driving prioritization to resolution.
- Clarify and resolve ownership when an issue crosses organizational boundaries or has no clear owner.
- Own the internal launch-exception process and coordinate launch risk when standard delivery paths break, or a committed launch is threatened.
- Own internal mitigation for escalated timeline and delivery risk while TAM maintains partner-facing communication.
- Route validated, recurring partner needs and operational gaps into the product roadmap process, and own the process for prioritizing shared improvements.
- Exercise disciplined judgment about when to engage: step in only when work crosses teams, changes a shared product, requires prioritization, or creates material delivery risk, and stay out of standard delivery work.
- Build the communication cadences, documentation, and artifacts (dependency maps, risk logs, status updates, decision records) that keep cross-team programs transparent and accountable.
- Leverage AI-powered tools (e.g., Copilot, ChatGPT, Notion AI) to accelerate documentation, planning, prioritization artifacts, status updates, and stakeholder summaries.
- Apply AI-based data exploration tools to quickly surface insights from program metrics, incident logs, and dashboards, and proactively automate repetitive coordination workflows.
- Stay current with evolving AI tools and best practices, and advocate for their integration into cross-functional workflows.
Minimum Requirements
- 7+ years of experience in a Technical Program Manager or equivalent role, including demonstrated ownership of cross-team delivery coordination.
- Proven success leading large, cross-functional programs, especially those involving data platforms, data products, pipelines, or delivery infrastructure.
- Strong technical fluency: able to engage credibly in architectural discussions around data models, pipelines, export and delivery mechanisms, connectors, and APIs.
- Demonstrated ability to drive prioritization and manage dependencies across multiple engineering teams, and to resolve ownership when issues cross organizational boundaries.
- Excellent communicator with a track record of influencing without authority and managing stakeholders across commercial (Sales/GTM), account (TAM), and technical (SE and engineering) functions.
- Experience leading incident response and coordinating cross-team resolution for major, recurring, or multi-partner issues.
- Familiarity with tools like Jira, Confluence, Asana, Notion, or similar platforms.
Preferred Requirements
- Experience in a high-growth or startup environment where adaptability and ownership are critical, and scope evolves quickly.
- Experience coordinating partner- or customer-facing delivery programs, particularly data delivery, exports, or integrations.
- Background bridging client-facing teams (sales, account management, solutions engineering) with internal engineering and platform teams.
- Track record of routing recurring needs into a product roadmap process and driving prioritization of shared improvements against competing engineering work.
- Familiarity with data quality, telemetry, anomaly detection, or data-dictionary and definition governance.
- Comfort operating as an escalation and coordination role rather than a checkpoint, with the discipline to know when to engage and when to let the standard path run.
- Ability to thrive where program scope evolves rapidly and the definition of success may shift as the team, operating model, and org structure mature.