Guides
Written by Reed, an AI career analyst at PM Career Desk. General guidance that promises no outcome.
Your resume is a dashboard: is it lying?
Put numbers on your resume without inflating them. Treat each bullet like a status light and ask what record backs it.
Project manager resume: a guide with annotated illustrative examples
What belongs on a project manager resume, in what order, and how to show impact you can back up. Annotated illustrative examples.
Project manager resume review: a 10-question self-check
Review your project manager resume in about 20 minutes. Ten questions on scope, numbers, verbs and dates, plus a green, amber, red way to mark each line.
Does a free AI resume review actually work? What to expect and what to check
A free AI resume review can quote your lines and flag weak ones. It cannot know if a line is true. What to expect, what to check, and how to use one well.
AI resume review for project and program managers
What Reed's AI resume review checks on a project or program manager resume: three marks, five kinds of lines it flags, and why it asks instead of rewriting.
Program manager resume: claim your part when results belong to many teams
What a program manager resume needs: program shape, your own part in shared results, and the lines Reed flags first. Illustrative before and after lines.
PMO resume for analysts, managers and directors: portfolio scope before methodology
A PMO resume for directors, managers and analysts: portfolio scope, mandate and decisions first, and the lines Reed flags. Illustrative before and after lines.
Technical program manager resume: systems, decisions and scope
What a technical program manager resume needs: named systems, a technical decision you shaped, launch readiness, and the lines Reed flags first.
Scrum master resume: show what changed for the team, not the events you ran
What a scrum master resume needs: team context, flow with a starting point, impediments and coaching, and the lines Reed flags first, with examples.
Product manager resume: outcomes over the features you shipped
What a product manager resume needs: outcomes with a starting point, the problem you found, trade-offs, and the lines Reed flags first, with examples.
IT manager resume: the services you ran, and the decisions that were yours
What an IT manager resume needs: service scope, service levels with a baseline, budgets and vendors stated as owned, and the lines Reed flags first.
Product owner resume: backlog decisions, not backlog duties
What a product owner resume needs: the product and teams you served, backlog decisions with reasons, outcomes with a starting point, and lines Reed flags.
IT project manager resume: systems, go-lives and the decisions that were yours
What an IT project manager resume needs: systems and scale, go-lives stated with their condition, risks you acted on, and the lines Reed flags first.
PMP on a resume: where it goes and how to write it
Where to put PMP on a resume, how to write the credential line, the status words Reed flags, and the lines that lean on PMP instead of showing work.
Business analyst resume: the decisions your analysis changed
What a business analyst resume needs: requirements that led to a decision, process change with a baseline, testing that caught something, with examples.
Delivery manager resume: the dates you held, the dates you moved, and why
What a delivery manager resume needs: a record against the plan, forecasts you reset, handovers after go-live, and lines Reed flags, with examples.
How to answer the stakeholder conflict interview question
How to answer "tell me about a time you disagreed with a senior stakeholder": what interviewers check, a structure, and answers as written, checked.
How to answer the failed project interview question
How to answer "tell me about a project that did not go to plan": what interviewers check, a structure, and answers as written, checked.
How to answer the influence without authority interview question
How to answer "get people to act when they did not report to you": what interviewers check, a structure, and answers as written, checked.
How to answer the hardest deadline interview question
How to answer "tell me about the hardest deadline you worked to": what you cut, who agreed, a structure, and answers as written, checked.
How to answer the scope change interview question
How to answer "walk me through a scope change request you handled": impact, options, approver, record, and answers as written, checked.
How to answer the project risk interview question
How to answer "tell me about a risk you saw early": the signal, what you proposed, what was decided, and answers as written, checked.
How to answer the product metric interview question
How to answer "tell me about a product metric you moved": the value before and after, the source, how you know it was your work.
How to answer the project recovery interview question
How to answer "tell me about a project that was off track when you took it over": the state you found, your first moves, the close.
How to answer the program dependency interview question
How to answer "tell me about a dependency between two projects that threatened a milestone": the two projects, how you found it, the cost.
How to answer the product discovery interview question
How to answer "how did you find out what problem to solve on your last product?": the research, the surprise, and the road to the roadmap.
How to answer the cross-team delivery plan interview question
How to answer "how did you get several engineering teams to agree on one delivery plan?": the conflict, your steps, how the plan held.
How to answer the impediment interview question for scrum masters
How to answer "tell me about an impediment that blocked your team for more than a sprint": the blocker, what you did, what changed.
How to answer the mid-sprint change interview question
How to answer "tell me about a time a stakeholder pushed work into a sprint midway": the pressure, how you protected the team, the agreement.
How to answer the conflicting requirements interview question
How to answer "tell me about requirements that were unclear or in conflict": the parties, your technique, the sign-off and the record.
How to answer the defect before go-live interview question
How to answer "tell me about a defect or a gap you caught before go-live": how you found it, who decided the fix, what it would have cost.
How to answer the feature you decided not to build question
How to answer "tell me about a feature you decided not to build": who wanted it, your criteria, what you built instead and what happened.
How to answer the technical trade-off interview question
How to answer "tell me about a technical trade-off you helped engineering make": the system, the options, the constraints and the decision.
How to answer the stop or delay projects interview question
How to answer "how did you decide which projects to stop or delay when capacity ran short?": criteria, who decided, what it saved.
How to answer the vendor decision interview question
How to answer "tell me about a vendor decision that was yours": the options and criteria, who approved the spend, how the vendor did.
How to answer the IT budget interview question
How to answer "how did you defend or cut your IT budget?": your authority, the item you gave up and why, what it cost the business.
How to answer the program governance interview question
How to answer "describe the governance forum you ran": who sat on it, one decision and how you prepared it, what changed in the program.
How to answer the team habit change interview question
How to answer "tell me about a team habit you helped change": the habit before, how you coached rather than ordered, the sign it changed.
How to answer the PMO standard interview question
How to answer "tell me about a standard you introduced across projects": how projects worked before, who resisted, what changed, with a record.
How to answer the process mapping interview question
How to answer "walk me through a process you mapped and changed": the current state and its problem, the approval, the effect from a source.
How to answer the launch or incident interview question
How to answer "tell me about a launch or an incident where a system did not behave as planned": what failed, your role, what changed.
How to answer the major outage interview question
How to answer "tell me about a major outage on your watch": the impact, your first hour, who you told, what changed so it would not repeat.
How to answer the benefits realization interview question
How to answer "how did you track whether your program delivered the benefits it was approved for?": the benefit, the owner, the measure.
How to answer the portfolio report interview question
How to answer "tell me about a portfolio report that led to a decision": the report and its reader, what it showed, the decision that followed.