Technical Program Manager

Convert tribal knowledge into documented, repeatable processes: release runbooks, checklists, onboarding guides.

Define and maintain the release process end-to-end so it is survivable if any individual is unavailable.

Establish templates for cross-team planning: dependency maps, risk registers, status reports.

Identify bottlenecks and gaps; propose and implement improvements using retrospective data.

Design and own the organization-wide status reporting system: template, cadence, format, and a compilation mechanism so the report assembles itself.

Author program-level status reports directly covering cross-team releases, dependency health, risks, and milestones.

Partner with engineering leadership to mature delivery practices and introduce tooling that improves velocity and visibility.

Establish program-level metrics (cycle time, release predictability, dependency-related delays) and use them to drive improvement.

5 to 9 years of experience in technical program management, engineering program management, or a comparable role coordinating across multiple engineering teams.

Demonstrated ability to build and run release coordination at the program level, not just within a single team or project.

Strong technical fluency: you can hold a substantive conversation about architecture, dependencies, and technical risk without needing it simplified for you.

Experience defining and documenting processes from scratch, including runbooks, RACI matrices, and dependency tracking frameworks.

Track record of managing cross-functional stakeholders, including product, QA, marketing, and customer success, through complex releases.

Clear written communication: your status reports give leadership the information they need to make decisions, not a list of what everyone is working on.