The ChatGPT prompts that help most in a project manager interview work with your real projects: the scope that changed, the date that slipped, the sponsor who needed bad news. The 14 prompts below turn your project notes into two-minute answers, rehearse the scenarios PM panels use and let you practice the work itself, from an executive status update to a 15-minute planning exercise. They work in ChatGPT, Gemini, Claude and Microsoft Copilot.
The AI plays sponsor, stakeholder and hiring manager. The projects, numbers and decisions have to be your own. For how this fits a full preparation plan, see how to use AI for interview prep.
What to paste in, and what to keep out
PM answers live or die on specifics: the baseline, the variance, the decision and who made it. Gather them before you prompt.
| Project material | Paste it in as | Remove or generalize |
|---|---|---|
| Project summaries | Goal, team size, duration, method, outcome | Client and vendor names ("a logistics client") |
| Schedule and budget | Baseline against actual, in weeks or percentages | Contract values and confidential budgets |
| Risks and issues | The two or three that mattered and what you did | Anything about a named person's performance |
| The job description | In full | Nothing; it is already public |
Percentages and weeks ("6% under budget, two weeks late") are usually enough for an interview and avoid sharing figures your employer would treat as confidential. Our project manager interview questions show what these notes need to answer.
Turn your projects into answers
1. Pick the right project for this job
Here are notes on [3 to 5] projects I managed: goal, size, team, method, duration and outcome: [paste]. Here is the job description: [paste]. For each project, write a one-sentence interview headline (goal, constraint, result). Then rank the projects by how closely they match this job and explain the top choice in two sentences.
Interviewers often ask about "a project like the ones you'd run here". Leading with the closest match puts your best detail where it counts.
2. The two-minute walkthrough
Shape my [project] into a two-minute answer to 'Walk me through a project you managed': the goal, the main constraint, my three key decisions, the result with numbers and one lesson. Use only my facts: [paste]. Where a number is missing, such as the schedule variance or the budget outcome, ask me for it instead of estimating.
Two minutes forces you to choose decisions over chronology, which is what a hiring manager wants to hear.
3. Baseline, change and variance
Act as a delivery director. Ask me about the scope, schedule, budget and quality of [project], one area at a time: what the baseline was, what changed, who approved each change and where we ended up. If I don't know a number, say 'look this up' rather than letting me guess.
Vague answers about budget and schedule make an experienced PM sound junior. This shows which numbers to find before the interview.
4. Agile, predictive or hybrid
The job description says: [paste the lines about delivery method]. Ask me three questions that test whether I choose a delivery approach to fit the work rather than out of habit, including one where a stakeholder wants fixed scope and a fixed date on an agile project. After my answers, tell me if anything sounded dogmatic.
Panels want judgment about method, not loyalty to one. If the role sits close to Scrum, our Scrum Master interview questions cover the overlap.
Rehearse the scenarios PM panels use
5. The late vendor
You are the sponsor of a project I manage. Two weeks before go-live, a vendor tells me a critical component will be three weeks late, and there is no schedule reserve. I'll tell you what I'd do first; react as a sponsor under pressure from your own boss. After four exchanges, step out and tell me whether I assessed the impact and options before promising you anything.
The strongest first step is usually to assess impact and options with the team. Promising a recovery before that is the classic mistake.
6. Two stakeholders, opposite directions
Play two senior stakeholders, [role A] and [role B], who give my team conflicting directions on [deliverable]. Reply as each in turn, and each of you should push me to take your side. My job is to bring you both back to the approved plan and the decision owner. Afterwards, rate whether I stayed neutral, used the plan and got the decision recorded.
Quietly picking a side is the wrong answer; getting the right person to make a recorded decision is the right one.
7. The project you inherit
I'm taking over a project that is about [percentage] over budget and [number] weeks behind. Ask me what I'd do in my first two weeks, one question at a time: how I'd find the cause, who I'd talk to, what I'd re-forecast and what I'd present to the sponsor. Challenge me if I start fixing things before I know why they broke.
Inherited-project questions test diagnosis before action. The challenge line catches the urge to start fixing too early.
8. The sponsor who wants to cut testing
Play a sponsor who asks me to cut the testing phase in half to hit a launch date. Push back twice with business reasons. I need to make the risk visible in plain terms and let you decide with full information. Afterwards, tell me whether I explained the risk in business language rather than project jargon.
The decision belongs to the sponsor; your job is to make the risk impossible to misread. Practice saying it without lecturing.
Practice the work itself: status, risks and a plan
9. A 60-second executive status update
Here is the current state of a project, real or invented for practice: [milestones, budget position, top risks, open decisions]. I'll give a 60-second status update to an executive. Then rate it on four things: a clear overall status with the reason, the decisions I need from them, the next milestone, and no task lists. Quote the sentence I should cut.
Some interviews ask for a status update outright. Executives want the status, the reason and the decision they need to make.
10. Build a risk register out loud
Give me a short brief for a [type] project. I'll list the top five risks, each with an owner, likelihood, impact and response. Challenge two of them: one that is really an issue rather than a risk, and one whose response is too vague to act on. Then ask me how often I'd review the register and with whom.
"What's the difference between a risk and an issue?" is a common question. This drill answers it with your own example.
11. A 15-minute planning exercise
Give me a 10-line brief for a small project, such as moving a 60-person office or launching an internal tool. I'll talk through my plan: work breakdown, estimates, dependencies, critical path, milestones and how I'd communicate. Let me finish, then list what I skipped and which assumption most needs checking.
Planning exercises reward a visible structure more than a perfect plan. Run a phone timer so the 15 minutes are real.
Score, tools and closing questions
12. Score with a PM rubric
Score my answer to '[question]' from 1 to 5 on each of these: ownership, structured thinking, stakeholder handling, use of data, and honesty about what went wrong. Quote my words for each score, then name the one sentence that would most improve the answer. Answer: [paste].
A role-specific rubric gives sharper feedback than a generic "good answer". Keep it the same across sessions so the scores mean something.
13. Tools and certifications, honestly
Ask me which project tools I've used and whether I hold or plan to get a project management certification, as an interviewer would. Check that I name only tools I've actually used and say what I used them for, and that if I'm not certified I say so plainly and describe how I already work. Flag anything that sounds like padding.
Interviewers often ask about certifications such as the PMP. "Not yet, and here is how I run projects today" beats a vague promise. Check current requirements on PMI's own site, not with a chatbot.
14. Questions to ask the hiring manager
Write six questions I could ask the hiring manager for this role: [paste job description]. Cover how projects are prioritized, what the project manager owns compared with the product owner or engineering lead, the state of the first project I'd pick up and how success will be judged after six months. Make each one specific to this job.
Good questions double as evidence: they show you already think about ownership, priorities and outcomes.
Check what the AI gives you
| What to check | Why it matters | What to do |
|---|---|---|
| Invented metrics | PM answers are full of numbers, and models fill gaps with plausible ones | Delete any figure you can't trace to your own records |
| Method claims | Chatbots state framework rules with confidence, sometimes wrongly | Check definitions against the official source, such as the Scrum Guide or PMI's materials |
| Hero stories | Drafts tend to make you rescue everything single-handed | Credit the team; keep your own decisions |
| Length | Project stories sprawl | Two minutes per story, said out loud with a timer |
| Confidential detail | Status reports and risk logs often contain client data | Generalize names and figures before pasting |
Panels now also ask how you would use AI in project work itself; our AI interview questions for project managers cover that. Then rehearse the spoken version: an AI mock interview that reads questions aloud and scores your spoken answers shows whether your two-minute walkthrough really is two minutes.
Where CoPilot Interview fits
CoPilot Interview is an AI interview helper that picks up where these prompts stop. Its mock interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10, so you can rehearse a project walkthrough the way you'll deliver it. The free plan gives 15 minutes a day of live help in sessions of up to 15 minutes, with AI mock interviews included. Paid plans are Standard at $24.99 a month and Pro at $39.99 a month.
It runs as a desktop app for Windows 10 and 11 and macOS 12 or later, a free iPhone and iPad companion on the App Store (iOS 16 or later) and an Android companion in beta. In live interviews, the desktop app shows captions of the interviewer's question and a structured answer in about two seconds. If you use it there, follow your employer's rules; for planning exercises, tests or assessments that ban outside help, prepare beforehand instead.
Disclosure: CoPilot Interview is our product, so weigh what we say about it accordingly.
Frequently asked questions
What are good ChatGPT prompts for a project manager interview?
Prompts that use your real projects: one that turns project notes into a two-minute walkthrough with numbers, role-plays of sponsors and stakeholders in common scenarios, and drills for a status update, a risk register and a short planning exercise.
Can ChatGPT help with situational project manager questions?
Yes. Ask it to play the sponsor or stakeholder in a scenario such as a late vendor or a request to cut testing, and to tell you afterwards whether you assessed impact and options before promising anything.
Should I share real project numbers with ChatGPT?
Share what you'd say in an interview, not confidential data. Weeks late and percentage over or under budget usually tell the story. Leave out client names, contract values and anything your employer treats as confidential.
Do I need the PMP to answer project manager questions well?
Not necessarily. Many postings list it as preferred rather than required. If you don't hold it, say so plainly and describe how you already run projects, with the change log, risk register and sponsor updates you actually use.
Rehearse it out loud before the real one
The AI mock interview builds questions from your resume and the job description, reads them aloud and scores each spoken answer out of 10. Included on the free plan.
Start a mock interview