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 workstreams, 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.

Engagement Execution

• 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, GitHub), 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.

Operational Discipline & Cadence

• 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.

Delivery Quality & Risk

• 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 land back in the team's operating practice, not just a deck nobody reads.

Stakeholder Management & Business Outcomes

• Build and own the stakeholder map for the engagement: who decides, who influences, who must be kept informed, and what each one cares about.
• Operate as a credible counterpart to client business leaders, not just their delivery PM, speak fluently to commitments, tradeoffs, and value, in their language.
• Track committed business outcomes alongside execution metrics; know at any moment whether the engagement is on track to deliver the value the client signed up for.
• Partner with the Agentic Systems Analyst on baseline measurement and benefit realization tracking, execution rigor without value rigor is half the job.
• Run the operational rhythm of client communication that keeps trust intact, proactive, transparent, and framed in business terms, never raw status.
• Surface expansion-relevant signals to the Engagement Lead: client comments, friction points, adjacent processes that came up in discovery and could become the next workflow.

Cross-Functional Coordination

• Coordinate across Forward Deployed Engineers, Agentic Systems Analyst, Technical Architect, and Engagement Lead, you are the connective tissue that holds the workstreams together.
• Manage upstream and downstream dependencies on Platform Engineering, GTM, and other PODs.
• Communicate directly with client-side counterparts, their PM, their tech lead, their delivery owner, you are not a back-office function.
• Run the cadence of communication with offshore delivery teams; ensure follow-the-sun models actually work follow-the-sun, not lose-a-day-per-handoff.
• Support the Engagement Lead in pre-sales and engagement shaping with defensible estimates, plan structures, and delivery risk assessments.

What This Role Is Not (And What It Honestly Is)

• Not a Scrum Master. You make tradeoff decisions, not facilitate them.
• Not a coordinator or scribe. You own execution rigor, not meeting notes.
• Not a status-reporter. The status report is a byproduct of the work, not the work.
• Not the architect. You partner with the Technical Architect, you do not substitute for them.
• Honest reality: in our current operating model, this role carries more stakeholder management and business framing than a textbook TPM. The Engagement Lead owns the relationship and the commercial outcomes, but on the ground you are the operational counterpart the client trusts day-to-day to translate work into business terms. Candidates who want a pure execution role and prefer to stay heads-down on the plan are not the right fit. Candidates who can run a tight plan AND hold their own with a client VP are.

Qualifications

Required

• 8 years in technical program management, engagement management, or delivery leadership in a professional services, consulting, or technology environment.
• Proven track record of owning end-to-end execution for cross-functional delivery teams (engineers, architects, PMs) on technically complex engagements.
• Demonstrated stakeholder management at VP or director level on the client side, you can hold your own with senior business leaders, not just their delivery counterparts.
• Business fluency: comfortable framing engagement progress in commercial and outcome terms, working with ROI models, and translating execution tradeoffs into business consequences.
• Strong technical fluency, you do not need to write code, but you must understand AI/ML, data platforms, and cloud architecture well enough to make tradeoff decisions and communicate credibly with engineers and client executives.
• Demonstrated ability to operate in ambiguous environments, with incomplete information and shifting priorities.
• Excellent written and verbal communication, equally credible in a steering committee and in a backlog grooming session.
• Experience managing engagement economics, scope control, and change management.
• Deep fluency with the systems agentic delivery runs on (Linear, Notion, Slack, GitHub), you do not need to be told how to set up a project plan or a status view.

Strongly Preferred

• Background in AI, data, or technology consulting, you understand the domain as well as the delivery mechanics.
• Experience working in a professional services firm, systems integrator, or technology consultancy.
• Prior experience operating at the engagement-management altitude, where business outcomes and execution rigor are owned together.
• Prior experience managing distributed or offshore delivery teams with follow-the-sun models.
• Familiarity with agentic AI systems, RAG architectures, or LLM orchestration workflows, enough to plan around their failure modes, not necessarily build them.
• Experience contributing to IP capture, accelerator development, or reuse-driven delivery models.
• Experience in regulated industries: financial services, healthcare, or insurance.
• PMP, PgMP, or equivalent program management certification.