How to move from project manager to program manager
The short answer
To move from project manager to program manager, show work across projects, not only within one. Take on the links between projects: dependencies, a shared governance forum, a trade-off put to a sponsor, benefits beyond go-live. Then write that work into your resume and practice the program questions before you apply.
Practice your answers in Claude with Interview Coach, free
What changes in the work
A project manager owns one plan, one team and one delivery date. A program manager owns the space between several projects. The program manager rarely runs a schedule day to day; the project managers do that.
| Area | Project manager | Program manager |
|---|---|---|
| Scope | One project, one plan | Several dependent projects |
| Main record | Project plan and RAID log | Dependency map and decision log |
| Decisions | Within the project | Across projects, with the sponsor |
| Success | On time, on budget, on scope | The benefits the projects add up to |
| Team | Project team and vendors | Project managers, sponsor, steering group |
Moving up means letting go of the detail of one plan and holding the view across all of them.
Program work you can do now
You do not need the title to do some of the work. Look for chances in your current role.
- Own a dependency. If your project waits on another, set up the weekly check with the other project manager and keep the shared view.
- Run a cross-project forum. Offer to run the meeting where several projects review shared risks.
- Bring a trade-off to the sponsor. When two projects compete for a test window or a team, lay out the options instead of waiting.
- Track benefits. Ask the sponsor what the project should deliver after go-live, and report on it.
Each of these leaves a record: a dependency map, minutes, a decision log, a benefits view. Those records become your resume lines and your interview stories.
Show it on your resume
Program hiring managers read your lines for work across projects. A line about one schedule reads as project work, even under a senior title.
| Resume line as written | What the free review finds | Stronger line for a program role |
|---|---|---|
| Responsible for coordination with other project teams on the billing release. | This line names a duty and no result. | Ran a weekly dependency review with 3 project managers, which moved the billing release ahead of the shared test window, per the program minutes. |
| Managed the schedule for the CRM project. | This line names a duty and no result. | Put the shared test window conflict between 2 projects to the sponsor, who chose to move the data project by 3 weeks, per the decision log. |
| Delivered the CRM rollout to 4 regions. | The program is named; the benefit it was meant to produce is not. | Ran the CRM rollout across 4 regions to its goal of one customer record per account, which the sales leads confirmed in the quarterly review. |
Illustrative, not a real client.
The third line names the program but not what it was for. A program manager is judged on the benefit the projects add up to, so name it.
Put program words in your summary and headline only when your lines back them up. The program manager resume guide covers the rest of the resume.
Before you apply, check your resume against a program posting. The free resume to posting match marks each requirement as shown, partly shown or not found. Program postings often ask for governance, dependencies and benefits; see which of those your lines show.
Match your resume to a posting, free
Is it program, project or TPM?
Titles vary between companies. A "senior project manager" posting may describe program work, and a "program manager" posting may describe one large project. Read the duties, not only the title.
The free title fit check asks a few questions about the work you do and want, and tells you which title it matches best. It helps you decide which postings to apply to.
Check which title fits your work
What program interviews ask
Program interviews ask about the links between projects. Expect questions like these:
- Tell me about a time a dependency between two projects put a date at risk.
- How did you set up governance for a program? What decisions went where?
- Tell me about a trade-off you put to a sponsor between two projects.
- How did you show the benefits of a program, not only its go-live dates?
Prepare one story for each, with your own action and a record. The program manager interview questions list more, and the program dependency question guide and the program governance question guide show what a strong answer covers.
A stretch role on your current program
The fastest route is often a stretch role where you are. Ask your manager whether the next program needs someone to hold the links between its projects. Offer to run the program review, own the dependency map and write the steering pack.
Agree on what the stretch role covers and for how long, so the work shows on your record. At the end, ask your manager for a short review of what you did. That review, and the records you kept, make the case for the title.
Inside your company or outside
A move inside your company is often easier. Your manager has seen your work, and you can take on program work before the title changes. Ask for a stretch role: the next program that needs someone across its projects.
A move to a new company asks more of your resume and interviews, because the hiring manager has only your lines and your stories. The records you built in your current role carry the case.
Certifications
Some people pursue a program management certification for the move. Postings vary: some list one, many do not. A certification shows study; your program records show the work. If a posting you want lists a certification as required, take it into account. If not, the work comes first.
Your first 90 days as a program manager
Once you land the role, the first months set the tone. Map the dependencies, set up governance, then bring the first trade-off to the sponsor. The 30-60-90 day plan for a program manager walks through each phase with an example.
Practice with Interview Coach in Claude
Program interviews ask about dependencies and governance. Write your answer the way you would say it and ask Interview Coach for a check.
- Paste your resume and the job posting. Interview Coach returns the lines a hiring manager is likely to ask about, each as a question that quotes your own line, with the points a strong answer covers.
- It matches the requirements of the posting to your resume and turns the gaps into questions to prepare.
- Write one answer at a time and ask for a check. It looks for a situation, your own action, a result and a before and after figure or a named record. It does not judge whether the story is true.
Your answers start from your resume. The free review quotes your own lines and flags the 5 to fix first, so you know which lines an interviewer may question.
Free in Claude, no account. We do not store the text you send through it.
Questions
Is program manager a step up from project manager?
In many companies it is the next level, because the role covers several projects and the links between them. Titles vary, so read the duties of a posting rather than the title alone.
How many years as a project manager do I need before program manager?
There is no fixed number. What matters is whether you have done work across projects, such as dependencies, governance and trade-offs with a sponsor. Postings state their own requirements.
Do I need a certification to become a program manager?
Some postings list one and many do not. Program work you can show on your resume and in interviews usually matters more. Check the postings you want for what they require.
Keep going
- Program, project or TPM: which title fits
- Program manager interview questions
- Program manager resume guide
- 30-60-90 day plan for a program manager
Last updated: October 24, 2026