Skip to content
(Role / 05)MBA tech role · Track 05← All roles

Program Management

Program managers drive complex cross-team initiatives end-to-end. They scope, sequence, unblock, and ship on time across many stakeholders, often where no single team owns the outcome.

(02)The work

What you do.

  1. (01)

    Define program scope, milestones, and success criteria with execs.

  2. (02)

    Coordinate engineering, design, marketing, legal, and ops to hit dates.

  3. (03)

    Identify risks and dependencies early; drive mitigation.

  4. (04)

    Run rhythms: kickoff, status, escalations, retros.

  5. (05)

    Communicate up, down, and sideways — keep everyone honest.

(03)Skills

Key skills.

Project planningRisk managementStakeholder communicationOperational rigorComfort with ambiguityInfluence without authority

What they look for.

  • (01)

    Examples of leading complex projects across many stakeholders.

  • (02)

    Operational maturity — checklists, status reports, clear escalations.

  • (03)

    Comfort being the most-organized person in the room.

  • (04)

    Technical literacy (esp. for TPM roles).

(04)Know the difference

Distinctions.

The same title can mean different things depending on the product, the company, and the stage. Here’s how to pick it apart.

Vs / 01

TPM (Technical Program Manager)

Engineering-adjacent. Plans and runs complex technical programs (platforms, infra, ML). Strong CS / systems background usually expected.
Vs / 02

Non-technical PgM

Runs cross-functional business programs — launches, compliance, integrations, expansion. MBAs land here often.
Vs / 03

PgM vs. PM

PMs own the what/why of a product. PgMs own the how-and-when across many products or teams.
(05)Ecosystem

Often confused with.

Roles that sit close to this one — useful to know whether you want the title or the adjacent version.

Product Management BizOps Engineering ManagementOperationsChief of Staff
(06)Further reading

Resources.

(07)The dossier

Open the full file.

File / Program · 3 chapters. Long-form chapters sourced from HTC's internal guides — the kind of reading that pays off on callbacks.