For a side-by-side role comparison with tables and FAQs, see TPM vs project manager.
People use the two titles like they mean the same thing. They don't. The gap shows up the first time something breaks across a team boundary.
A project manager owns a plan: scope, schedule, the status of known tasks. That work matters. But it assumes the work is already defined and lives mostly in one place. A technical program manager owns an outcome that no single team controls. The plan is an input, not the job.
Here's the test I use. If the hardest part of the work is keeping a known set of tasks on track, that's project management. If the hardest part is getting three teams with different roadmaps, different incentives, and different definitions of "done" to converge on one result, that's a program. The second one is where I spend my time.
The technical part isn't optional either. You can't sequence work you don't understand. When the data pipeline team says a change takes two sprints, I need to know whether that's real or padding, and the only way to know is to understand the system. A TPM who can't read the architecture is just relaying messages.
So when a recruiter asks what I do, the short version is this: I'm the person accountable for the outcome when no one team can deliver it alone. The plan is the easy part.