What to expect in a junior PM interview
Junior project management interviews test knowledge, mindset, and potential in roughly equal measure. At this level, interviewers know you likely haven't managed a multi-million dollar programme — but they want to see that you understand the fundamentals, can think structurally about problems, and have the communication and organisational instincts that make a good PM.
Expect questions across three areas: PM methodology and process, stakeholder and risk management, and behavioural questions that ask for evidence from your experience (university, internships, part-time work, volunteer roles — all valid).
What interviewers are really looking for
More than any other role, PM interviews reward candidates who demonstrate structured thinking and clear communication. You don't need to have managed a project — but you do need to show you know how to think about one.
PM methodology and process
Questions 1–7 · Methodology & Process
Question 01
"What is the difference between Agile and Waterfall project management?"
What they're really asking
The most common opening PM knowledge question. Do you understand the two dominant methodologies?
How to answer it
Waterfall is a sequential, linear methodology — requirements are fully defined upfront, then the project moves through fixed phases (design, build, test, deploy) with limited ability to change direction mid-stream. Best for projects with stable, well-understood requirements. Agile is iterative and flexible — work is delivered in short sprints, requirements can evolve based on feedback, and cross-functional teams collaborate continuously. Best for projects where requirements are likely to change or where early feedback is valuable. Many real-world projects use a hybrid of both.
Question 02
"Can you explain what a project scope is and why scope creep is a problem?"
What they're really asking
One of the most common and costly project failures. Do you understand it?
How to answer it
Project scope defines the boundaries of what is and isn't included in the project — what will be delivered, by when, and at what cost. Scope creep is the gradual, often uncontrolled expansion of scope — small additions that each seem harmless but collectively push the project over budget and past deadline. It's dangerous because it frequently happens without formal approval or a corresponding adjustment to timeline and budget. The fix: a clear scope document, a formal change control process, and the discipline to say "that's a great idea — let's log it for the next phase."
Question 03
"What is a risk register and how would you use one?"
What they're really asking
Risk management is central to PM. Do you have a framework for it?
How to answer it
A risk register is a living document that logs identified risks for a project — capturing the risk description, likelihood, potential impact, mitigation strategy, and owner. You use it by reviewing it regularly (not just creating it once), updating the status of each risk, and escalating anything that has materialised or changed. The key value: it forces the team to think ahead about what could go wrong rather than being surprised, and gives stakeholders visibility over the risk landscape. Even on small projects, maintaining a basic risk register signals professional maturity.
Question 04
"What tools have you used (or are familiar with) for project management?"
What they're really asking
Can you hit the ground running with tools the team likely already uses?
How to answer it
Name what you've actually used — Jira, Trello, Asana, Monday.com, Notion, Microsoft Project, Confluence, or even Excel. Be honest about your level of proficiency. If you haven't used the specific tool they use, say you're comfortable learning new tools quickly and give an example of picking one up before. The tool matters less than your ability to use any tool to track work, manage dependencies, and communicate progress clearly.
Question 05
"How would you create and maintain a project plan?"
What they're really asking
Can you translate a project objective into structured, trackable work?
How to answer it
Walk through the steps: start with the project objective and work backwards to identify all the deliverables needed. Break deliverables into tasks, estimate effort and duration for each, identify dependencies between tasks, assign owners, and build a timeline. Key elements of a good plan: clear milestones, identified critical path, realistic buffers, and named owners for every task. Maintaining it means running weekly reviews, updating status, surfacing blockers early, and communicating changes to stakeholders — not just keeping a tidy Gantt chart that nobody looks at.
Question 06
"What is a stakeholder map and why is it useful?"
What they're really asking
Do you understand that project success depends as much on people management as task management?
How to answer it
A stakeholder map identifies everyone who has an interest in or influence over a project — mapping them by their level of influence and level of interest. It's useful because different stakeholders need different levels of engagement: high-influence, high-interest stakeholders need to be managed closely; high-influence, low-interest stakeholders need to be kept satisfied; low-influence stakeholders may just need regular updates. Failing to manage a powerful stakeholder who feels ignored is one of the most common reasons projects run into trouble despite good execution.
Question 07
"What is a RAID log?"
What they're really asking
Common PM artefact — do you know the terminology?
How to answer it
RAID stands for Risks, Assumptions, Issues, and Dependencies. A RAID log is a single document (or set of documents) that tracks all four categories throughout the project lifecycle. Risks are potential future problems. Assumptions are things the plan relies on being true. Issues are problems that have already occurred and need resolution. Dependencies are tasks or deliverables that must happen before something else can proceed. Maintaining a RAID log is a sign of a well-run project — it forces the team to be explicit about the things that could derail them.
Practise these PM questions out loud
Knowing PM theory and explaining it confidently in an interview are two different skills. InterviewZap helps you practise both — with feedback on your structure, clarity, and confidence.
Start Practising Free →No credit card. Free to start.
Situational and scenario questions
Questions 8–13 · Situational
Question 08
"A project is running behind schedule. What do you do?"
What they're really asking
Can you remain calm and systematic under pressure? Do you communicate proactively?
How to answer it
First, diagnose before acting — understand exactly where the delay is, why it happened, and whether it's on the critical path (if not, it may not affect the end date). Then assess options: can tasks be parallelised, can scope be reduced, can resources be added? Communicate early with stakeholders — the worst thing a PM can do is hide a delay and hope to recover quietly. Present a revised plan with clear options and a recommendation. Own it rather than blame the team.
Question 09
"Two senior stakeholders want conflicting things from the same project. How do you handle it?"
What they're really asking
Stakeholder conflict is one of the most common PM challenges. Do you have a mature approach to navigating it?
How to answer it
Don't try to please both by splitting the difference — that usually produces a worse outcome for everyone. Instead: understand both positions fully before drawing conclusions, identify the underlying needs behind each stated position (they're often not as incompatible as they appear), and bring both stakeholders together to work through the conflict with the project's objectives as the reference point. If the conflict can't be resolved at that level, escalate to a project sponsor or steering group with a clear articulation of the trade-offs. Document whatever is agreed.
Question 10
"How would you onboard yourself to a project that's already in progress?"
What they're really asking
Junior PMs often join mid-project. Can you get up to speed quickly without disrupting momentum?
How to answer it
Listen before you act. Spend the first week reading every piece of project documentation — the plan, RAID log, status reports, stakeholder map. Have one-on-ones with each key team member and stakeholder to understand their perspective. Identify the most pressing issues and immediate risks before proposing any changes. Resist the urge to overhaul everything immediately — earn trust first, then influence. Changes based on misunderstood context cause more harm than the problems they're trying to fix.
Question 11
"How do you keep a project team motivated when things are difficult?"
What they're really asking
PM is a people role as much as a process role. Do you understand team dynamics?
How to answer it
Acknowledge the difficulty honestly rather than papering over it with forced positivity — teams see through that immediately. Focus the team on what they can control. Celebrate small wins and milestones. Shield them from unnecessary pressure or politics where possible, and give them a clear line of sight to why the project matters. One-on-ones with individuals who seem disengaged are often more effective than team-wide pep talks. The most important thing: be someone the team trusts to be straight with them.
Question 12
"A key team member is going to miss their deliverable. How do you handle it?"
What they're really asking
Can you manage performance and accountability without being aggressive or passive?
How to answer it
Start by understanding why — is it a capacity problem, a clarity problem, or something personal? Often blockers can be removed or timelines adjusted if you know about them early enough. Address it directly and privately, not in front of the team. Agree a revised plan with specific checkpoints. If the issue persists, escalate through the right channels — but don't wait until the deliverable is already missed to have the conversation.
Question 13
"How do you decide what to escalate to senior stakeholders versus handle yourself?"
What they're really asking
Junior PMs often escalate too much or too little. Do you have a framework for this?
How to answer it
Escalate when: the issue is outside your authority to resolve, it involves significant scope, cost, or timeline changes, it requires a decision that affects other stakeholders, or it's been unresolved for too long despite your efforts. Handle yourself when: it's within your remit, the impact is contained, and you have a clear path to resolution. The biggest mistake junior PMs make is sitting on issues too long — by the time they escalate, the window to act has often closed. When in doubt, escalate early with context and options, not just problems.
Behavioural questions
Use the STAR method for these.
Questions 14–20 · Behavioural
Question 14
"Tell me about a time you successfully delivered something on time and under pressure."
What they're really asking
Can you produce results when conditions aren't ideal?
How to answer it
Use a specific example — university group project, event you organised, work deliverable. Describe the pressure clearly (tight deadline, reduced team, unclear requirements), what you did specifically to deliver despite it, and the outcome. Emphasise the process — how you organised the work, communicated, and kept things moving — rather than just "worked really hard."
Question 15
"Describe a time a project or plan didn't go as expected. What did you do?"
What they're really asking
Can you adapt when things go wrong? Do you own it or deflect?
How to answer it
Be honest — pick a real example where things genuinely went sideways. Describe what happened, how you responded, and what the outcome was. The reflection is the most important part: what did you learn, and what would you do differently? Interviewers in PM roles weight this question heavily — projects rarely go to plan, and they're assessing your resilience and learning agility, not just your ability to execute when everything is smooth.
Question 16
"Tell me about a time you had to manage competing priorities."
What they're really asking
PMs are always juggling. Can you make clear-headed decisions about what matters most?
How to answer it
Describe the competing demands, how you assessed relative priority (urgency, impact, stakeholder visibility), what you decided, and what happened. Show that your prioritisation was deliberate and explained — not just reactive. Mention any communication you did to manage expectations on the things that had to wait.
Question 17
"Give me an example of a time you influenced someone without having formal authority over them."
What they're really asking
PMs manage through influence, not authority. This is one of the most important skills to demonstrate.
How to answer it
Describe a situation where you needed someone (a peer, a senior colleague, a supplier) to do something and you had no formal power to compel them. Walk through how you understood their perspective, what you appealed to — their interests, shared goals, or the data — and how the outcome played out. The key message: you get things done through relationships and reasoning, not just authority.
Question 18
"Describe a time you had to communicate bad news to a stakeholder."
What they're really asking
Can you deliver difficult messages clearly and constructively?
How to answer it
Describe the situation, what the bad news was, and how you chose to deliver it. Good practice: don't bury the lead — state the issue clearly upfront, provide context, explain what you're doing about it, and present options where possible. Show that you took ownership rather than deflecting. Stakeholders can handle bad news; what they can't handle is being surprised by it when it's too late to act.
Question 19
"What do you think makes a great project manager?"
What they're really asking
Do you have a thoughtful view of the role — and does it align with how this organisation operates?
How to answer it
Be specific and genuine. Core traits worth mentioning: proactive communication (no surprises), structured thinking (ability to turn ambiguity into a plan), emotional intelligence (reading stakeholders, managing conflict), and calm under pressure (decisions don't get worse when things are difficult). Then connect your answer back to yourself — briefly note which of these you believe is your strongest quality and give a sentence of evidence.
Question 20
"Do you have any questions for us?"
What they're really asking
Are you genuinely interested in this role and organisation?
How to answer it
Strong questions for PM roles: "What does the project portfolio look like for someone in this role in the first six months?" / "What methodology does the team primarily use and how strictly is it followed?" / "What are the biggest project challenges the team is currently navigating?" / "How does the PM function interact with the technical and product teams here?"
One more thing
If you don't have formal PM experience, draw on everything you've organised — events, group projects, sports teams, fundraisers. The skills are identical. What interviewers are assessing is whether you think like a PM, not whether your job title already says you are one.