Role Summary:

TPMs partner closely with engineering &  product leadership to deliver initiatives where architecture, integration, reliability,  performance, and technical trade-offs are central to success. 

TPMs are expected to be technically fluent (able to understand system design, APIs, data  flows, reliability constraints), while remaining primarily accountable for program  execution, cross-functional alignment, and outcomes. They will partner closely with  technical leads to drive the technical implementation plans and roadmaps.  

TPMs must be able to work in a complex environment with matrixed teams and  organizations. TPMs must provide project/program visibility to technical and business  stakeholders around key projects, status, risks, and post-launch metrics.  

Key Responsibilities :

Program strategy & planning 

• Define program objectives, success metrics, scope boundaries, and sequencing.

• Build an integrated roadmap across teams; manage critical path and trade-offs.

Technical coordination 

• Translate business goals into technical milestones and engineering deliverables. 

• Drive integration plans across services, APIs, data contracts, and environments. 

• Ensure non-functional requirements are planned: reliability, scalability, security,  privacy, cost, and observability. 

Execution leadership 

• Establish operating cadence across internal & dependent teams (working session, project reviews, milestone reviews, launch readiness, go/no-go). 

• Anticipate bottlenecks; negotiate sequencing and resourcing with engineering leaders. 

• Own RAID management and escalation with options and recommendations. 

Release & operational readiness 

• Drive launch plans, cutovers, feature flags, rollback strategies, and runbooks. 

• Partner with SRE/Infra to ensure monitoring, alerting, SLOs, and on-call readiness. 

Stakeholder management 

• Align engineering, product/business, security/compliance, and operations. 

• Communicate progress and trade-offs clearly to leadership; maintain a decision  log. 

A TPM consistently: 

• Drives cross-team execution without relying on escalation as the primary lever. 

• Makes ambiguity smaller: produces clear charters, milestones, and dependency  maps. 

• Understands enough technical detail to: 

- Ask the right questions 

- Surface integration risks early 

• Identify missing work (e.g., telemetry, data backfills, DR, access controls)

• Anticipates and manages systemic risks (migration complexity, reliability debt, data  quality). 

• Ships with operational excellence: readiness reviews, runbooks, SLOs, post-launch  validation. 

Qualification:

• Strong program management fundamentals (project planning, dependency  mapping, RAID, stakeholder management). 

• Technical fluency: system design concepts, APIs, data flows, environments, CI/CD  concepts. 

• Experience driving cross-team software/platform/infrastructure programs. 

• Comfort with ambiguity and technical trade-offs; can facilitate decisions. 

Preferred Qualification:

• Experience with AI/ML or data platforms. 

• Familiarity with SRE practices (SLO/SLI, incident management, observability). 

• Experience with large migrations, platform modernization, or reliability programs.

Boundaries (What This Role Is Not):

• Not the engineering manager or architect-of-record (but influences and unblocks). 

• Not a “Jira admin” whose primary output is tickets; outcomes and alignment come  first.

What is in it for you:

• Be part of the fastest-growing AI-first digital transformation and engineering company in the world

• Be a leader of an energetic team of highly dynamic and talented individuals

• Exposure to working with fortune 500 companies and innovative market disruptors

• Exposure to the latest technologies related to artificial intelligence and machine learning, data and cloud