Senior Technical Program Manager

We are looking for a Senior Technical Program Manager (TPM) who can be the execution spine of a client engagement, and who carries the stakeholder management and business fluency to operate as a credible counterpart to client business leaders, not just a delivery coordinator. You own the project plan, the cadence, the status, and the blockers. You also own the stakeholder map, the business outcomes the engagement is held to, and the running narrative of value delivered.

This is not a coordination or status-reporting role. You are not a scribe and you are not a Scrum Master. You are accountable for the rigor that turns a POD's intent into shipped outcomes, week over week, sprint over sprint. You make hard tradeoffs in real time when scope, time, and quality come into tension. You catch the blocker before it surfaces in a steering committee.

You ensure that the IP capture commitments the Engagement Lead and Technical Architect made on day one actually get done by close. And you carry the business framing of the work into every conversation: the value the client signed up for, what has been delivered against it, and what the next decision unlocks.

You operate inside the POD alongside the Engagement Lead, the Technical Architect, the Agentic Systems Analyst, and a set of Forward Deployed Engineers. You may run a single complex engagement or coordinate across two engagements depending on scope, concurrency, and account maturity. As an account grows from a single fixed-fee build, to multiple parallel work streams, to a portfolio of agentic capabilities running on a shared platform, your work scales with it.

Through all of it, you are the operational counterpart the client trusts to translate progress into business terms and tradeoffs into business consequences.

• Own the engagement plan end-to-end: scope decomposition, sprint structure, milestones, dependencies, decisions, and the critical path.
• Maintain a single source of truth for status, risks, and decisions in the systems the POD already runs on (Linear, Notion, Slack, Git Hub), kept current, not reconstructed retrospectively.
• Run the daily and weekly POD cadence (standups, planning, retros) without letting them become theater.
• Catch and clear blockers before they surface in client conversations or executive reviews.
• Translate ambiguous client requirements into actionable execution plans the Forward Deployed Engineers can pick up and ship against.
• Manage scope, change requests, and acceptance criteria with the Engagement Lead, every change carries a documented impact on plan, budget, and timeline.

• Enforce the operating cadence: daily POD standup, daily Engagement Lead and Technical Architect evening sync when the engagement requires it, weekly value review with the client, monthly account review against committed metrics.
• Protect calendar time for the things that get crowded out, IP capture review with the Technical Architect, architecture decisions, retrospectives, these are not optional.
• Own the offshore handoff discipline: documentation standards, overlap windows, definition-of-done criteria, and the asynchronous summaries that keep the next shift from losing time.
• Ensure every workstream has clear entry and exit criteria; nothing moves to done without meeting them.
• Maintain rigor on tracked changes, ADRs, runbooks, and handoff notes, you do not produce them yourself, but you ensure they exist when they should.

• Identify delivery risks early (scope, technical, resourcing, dependency) and surface them with options, not just flags.
• Ensure IP capture obligations are scheduled and tracked: every engagement produces Factory backlog items, and you are the one making sure that work is on the plan, not assumed to happen on its own.
• Partner with the Technical Architect to ensure architectural decisions are reflected in sprint goals and acceptance criteria.
• Monitor engagement-level metrics: velocity, burn-down, cycle time, exception rate, agent health where relevant, and feed that signal into the Engagement Lead's account health view.
• Drive post-engagement retrospectives; ensure lessons learned…