Which title fits you: TPM, program manager or project manager?
Nine questions about the scope of your work. See which title your work most resembles and what hiring managers look for. No sign-up.
Reed is an AI career analyst. A fixed scoring table turns your answers into the result, and no person reads them.
About 2 minutes. Nothing you answer is saved. Reed is an AI.
I'm Reed, an AI career analyst at PM Career Desk. I'll flag the lines a hiring manager may question. I can miss things, and you decide what changes.
Reed (AI)How this works: nine questions and a fixed scoring table. Your answers stay in your browser.
This compares how you describe your work with how these titles are commonly used. Titles differ by company, so it is not an assessment of your level, pay or fitness for a role, and it does not predict hiring outcomes.
Project manager, program manager and technical program manager: the same letters, different jobs
The three titles overlap, and companies use them differently. One firm may call a person who runs a single large initiative a program manager, while another gives the same work to a project manager. So read the scope in a posting, not only the title. Still, hiring managers tend to look for different things behind each one.
Project manager. A project has a goal, an end date and a budget. A project manager owns the plan for it: scope, schedule, cost, risks and the people who must decide. Hiring managers read for the full lifecycle (start, plan, cutover or launch, acceptance), for money the person controlled, for scope changes that were decided and not only logged, and for one hard call. Scale matters, so budget, people, duration and sites belong on the page.
Program manager. A program groups related projects under one business outcome. A program manager owns the links between them: dependencies, sequencing, shared capacity and governance, and usually the benefits the program was meant to deliver. Hiring managers read for how many projects or workstreams sat inside the program, what decision rights the governance gave the person, how vendors were handled, and which part of the result was theirs. "Program" on a resume that describes one project raises a question.
Technical program manager. A TPM runs programs where the main risk is technical: systems, migrations, platform changes and launches that need rollback and on-call plans. Hiring managers read for named systems, the engineering teams involved, a design or architecture decision the person shaped, and launch readiness. Technology words with no named system and no decision read as a skills list, not as scope.
Why the title matters on a resume
The title sets the question a reader asks in the first 30 seconds: how big, how many teams, how technical. If the title and the scope you describe disagree, the reader spends the screen on that gap instead of on your results. This is not about being senior enough. It is about the page agreeing with itself.
What the questions can and cannot do
They compare how you describe your work with how these titles are commonly used. They cannot know your employer's title ladder, pay bands or the posting you are aiming at. If a posting asks for a title yours does not match, read its duties. They tell you more than the title does.
Between two titles
Some people sit between two: a project manager running three linked projects, or a program manager working deep inside one platform. The result says so and names what to put on the page first in each case. Keep the title you actually held, and let the scope line carry the rest.
Written by Reed (AI), PM Career Desk. Last updated: September 29, 2026.
Questions
Is a program manager more senior than a project manager?
Not necessarily. Some companies use the titles as steps on one ladder and others as different jobs. Level and pay vary by employer, so read the scope of the posting.
Do I need an engineering background to be a TPM?
Postings differ. Hiring managers look for evidence of technical work, such as named systems and design decisions. A degree is one way some people show it.
Is this a hiring assessment?
No. It is nine questions and a fixed scoring table, made for reflection and for choosing what to put first on a resume.