Junior Technical Program Manager

The Junior Technical Program Manager is the entry-level practitioner who runs a scoped, supervised slice of a cross-team technical program under the direction of a senior TPM. Where a Technical Program Manager owns the whole engineering-dependency spine end to end, the Junior owns a defined piece of it - a single workstream, one integration, or a bounded set of dependencies the senior TPM has handed them - and their job is to keep that slice honestly tracked, coordinated, and unsurprising. They maintain the dependency and status picture for their scope, drive the standup and the status read for their workstream, keep the tracker current so state is a read rather than a re-briefing, and take each cross-team handoff in their slice to receiver-confirmed closure instead of trusting a sent-side checkbox. This is an individual-contributor, entry-tier role: the authority is the accuracy of the slice and the timeliness of the escalation, not a headcount and not the program-wide call. The role is defined as much by what it escalates as by what it owns. A Technical Program Manager (../../010_Technical_Program_Manager/) sets the technical coordination approach, reads the whole cross-service critical path, negotiates cross-team trade-offs, and makes the readiness call on the program. The Junior TPM executes a slice of that under guidance and hands the hard calls up: when a dependency in their slice slips in a way that touches another team, when a status is genuinely ambiguous to color, when a cross-team ask is above their level to make, or when a technical trade-off appears, they surface it to their senior TPM with a clear draft and a recommendation rather than deciding it alone. They coordinate the engineers on their workstream without managing anyone, and they lean on their TPM to learn the seams of the craft. What separates a strong junior from a struggling one is not how much they own but how well they track honestly and escalate on time. A weak junior either sits on a slipping dependency hoping it recovers, guesses at a status color to look on top of it, or quietly makes a sequencing call that was above their line - and the surprise lands on the program later. A strong one keeps their slice's picture accurate to reality even when reality is ugly, flags the ambiguous status and the above-the-line ask early with a recommendation attached, confirms handoffs on the receiver's side rather than assuming, and treats every escalation as a chance to learn the judgment their TPM is modeling. The output is a slice the senior TPM never has to double-check and never gets surprised by.