Project Management Interview Questions: 12 Questions with Model STAR Answers
In this guide you'll:
- Answer concept questions with a clear definition and an example
- Structure behavioral answers with STAR, using real project facts
- Practice all 12 questions with flashcards until each answer is ready
Quick answer: what do project management interview questions cover?
Project management interview questions test two things: the basics, such as phases, methods, scope and risk, and your experience, through behavioral questions you answer in STAR form: situation, task, action and result. This Kanbanchi guide gives you 12 questions with model answers and a flashcard deck to practice them.
How to answer: the STAR method
STAR is a way to structure an answer to a behavioral interview question: describe the Situation, the Task you were responsible for, the Action you took and the Result. Interviewers use behavioral questions, which start with "tell me about a time", to hear how you actually work. STAR keeps the answer short and specific.
The STAR structure. Keep the situation short and spend most of the answer on what you did and what changed.
- Situation: one or two sentences of context: the project, the team, the deadline.
- Task: what you were responsible for, in one sentence.
- Action: what you did, step by step. Say "I", not "we", for your own part.
- Result: what changed, with a number if you can: days saved, cost avoided, a launch on time. Then add what you learned.
For concept questions, such as "what is the critical path?", answer with the definition first, then a short example. The model answers below use the same definitions as the Project Management 101 lessons and the project management terms glossary.
Practice with flashcards
Practice deck: 12 project management interview questions
0 of 12 practiced
Read the question and answer it out loud before you reveal the model answer. Then mark it: got it, or practice again. Filter the deck to focus on one kind of question.
Worked example
The first card is shown with its answer open, so you can see how a card works: the question, what the interviewer is checking, and a model answer that starts with the definition and ends with an example from your own work. For the behavioral cards, the model answer is laid out as Situation, Task, Action and Result, with a real case from Kanbanchi's Great Projects and Project Failures pages. Mark the card, then move on.
The practice deck needs JavaScript. All 12 questions and model answers are listed in full below.
Questions on the core concepts
Concept questions check that you know the vocabulary and can apply it. Answer with the definition, then an example.
What makes work a project?
What they are checking: That you know the basic definition and can tell projects from ongoing operations.
A project is a temporary effort with a defined start and end that creates a unique product, service or result. Ongoing work, also called operations, repeats to keep an organization running and has no planned end.
Give an example of each from your own work, such as launching a new website (a project) and answering customer emails every day (ongoing work). The course page opens with a short sorting exercise on exactly this; see the Project Management 101 warm-up.
What are the phases of a project?
What they are checking: That you can describe a structured way to run a project from start to finish.
The project life cycle is the series of five phases a project moves through: initiation, planning, execution, monitoring and controlling, and closing. Name what each phase produces: a charter at initiation, an approved plan at planning, deliverables at execution, status reports during monitoring and controlling, and sign-off at closing. In agile projects, planning, execution, and monitoring and controlling repeat in every short cycle, while initiation and closing still happen once.
Revise the phases in Lesson 1: The project life cycle.
How do you choose between agile and waterfall?
What they are checking: That you choose a method for a reason, not out of habit.
Waterfall is a sequential approach: the team finishes each stage (requirements, design, build, test, release) before starting the next, with scope agreed up front and one delivery at the end. Agile is an iterative approach: the team delivers working pieces in short cycles, gets feedback after each one and adjusts the plan as it goes. Its values come from the 2001 Agile Manifesto.
Say how you decide: if the requirements are clear and unlikely to change, a plan-first approach works; if they will change as users see the product, deliver in short cycles. Mention that many teams combine the two. Practice the decision in Lesson 4.
What is the critical path, and why does it matter?
What they are checking: That you can read a schedule and know where to focus when the deadline is tight.
The critical path method (CPM) is a scheduling technique that finds the longest chain of dependent tasks; that chain sets the shortest possible project duration, and any delay on it delays the whole project. Shortening a task on the critical path shortens the project; shortening any other task does not.
A good example is Hoover Dam. Kanbanchi's Great Projects page explains that river diversion was the first link in the chain: cofferdams, excavation and concrete all depended on it. The river was diverted on Nov 13, 1932, almost eleven months before the contract deadline, and finishing it early moved every later task earlier. The dam was turned over more than two years ahead of schedule.
Facts from Kanbanchi's Hoover Dam: planned vs actual page.
Build a critical path yourself in Lesson 6.
How do you handle scope creep?
What they are checking: That you protect the plan without saying no to everything.
Scope creep is the gradual growth of a project's scope through small additions that nobody formally approved, which add up to delays and extra cost. The answer is change control. A change request is a proposal to change the agreed scope, schedule or budget; it gets a decision against the baseline, and the plan is updated only if it is accepted. A baseline is the approved version of the scope, schedule and budget that actual progress is measured against.
In the interview, describe the routine: every request is written down, its effect on time and cost is estimated, and the sponsor decides. Then give a short example of a trade-off you made. See step 6 in Lesson 2.
How do you find and manage project risks?
What they are checking: That you look for problems early and give each one an owner.
A project risk is an uncertain event or condition that, if it happens, affects at least one project goal, such as scope, time or cost. Describe a method: a pre-mortem at the start, a ranked risk list, and a review at every status meeting. A pre-mortem is a short team exercise held before a project starts: everyone imagines that the project has already failed and writes down why, so the team can act on the biggest risks while there is still time. A project risk matrix is a grid that scores each risk by its likelihood and its impact, so the team can see at a glance which risks to act on first. A risk owner is the one named person responsible for watching a risk and carrying out its prevention step or fallback.
Practice the method in Lesson 8.
Behavioral questions with model STAR answers
Behavioral questions ask for a story. Each model answer below is told in STAR form with facts from a real project on Kanbanchi's Great Projects or Project Failures pages, and ends with what you would do differently.
Tell me about a project that failed. What would you have done differently?
What they are checking: That you learn from failure and can name a specific, practical fix.
Use your own project if you have one. If you do not, or if the interviewer asks about a project you have studied, a well-known case told in STAR form works well. Model answer:
Situation. NASA's Mars Climate Orbiter launched on Dec 11, 1998. Lockheed Martin Astronautics designed and developed the spacecraft, and NASA's Jet Propulsion Laboratory kept overall project management and navigation design. Software called SM_FORCES wrote a data file that the trajectory modelers used, and the interface specification said metric: newton-seconds.
Task. Reach Mars orbit after a nine-month cruise, which depended on accurate data crossing that hand-off between teams.
Action. The data came in pound-force seconds instead of the specified newton-seconds, and the question of whether the file matched the spec belonged to nobody in particular. Concerns about discrepancies between navigation solutions were reported only informally, and the team relied on e-mail rather than the formal anomaly process.
Result. On Sep 23, 1999, the spacecraft began its Mars orbit insertion burn and its signal never came back. Its trajectory was approximately 170 kilometers lower than planned.
What I would do differently, or repeat. Put the interface check on the plan as a task with one named owner, and make every data discrepancy a formal issue with a name next to it. A pre-mortem that asks "why did we lose the spacecraft?" would surface the hand-off as a top risk.
Facts from Kanbanchi's Mars Climate Orbiter failure page.
Tell me about a project that went well. Why did it succeed?
What they are checking: That you can explain success with causes you could repeat, not luck.
Use your own project if you have one. If you do not, or if the interviewer asks about a project you have studied, a well-known case told in STAR form works well. Model answer:
Situation. Empire State Inc. planned an office tower on the old Waldorf-Astoria site in New York. The building had to open on May 1, 1931, and the plans were devised within a budget of $50 million.
Task. Design, demolish and build to a fixed opening date.
Action. The design changed fifteen times, but on paper, before construction. The schedule worked back from the opening date. Demolition overlapped with the next phase, and the contractor, Starrett Brothers and Eken, ran the site like an assembly line, with the frame rising at up to four and a half stories per week.
Result. The steel topped out on Sep 19, 1930, twelve days ahead of schedule, and the structure was finished on Apr 11, 1931, 410 days after construction began. The building opened on May 1, 1931 and cost $40,948,900 including the demolition.
What I would do differently, or repeat. Freeze the scope before work starts and plan back from a fixed date. Also separate luck from skill: part of the underrun came from Depression prices, not management.
Facts from Kanbanchi's Empire State Building: planned vs actual page.
What do you do when experts warn that the plan will not work?
What they are checking: That you treat warnings as risks to act on, not as noise.
Use your own project if you have one. If you do not, or if the interviewer asks about a project you have studied, a well-known case told in STAR form works well. Model answer:
Situation. In 1990, two consultants hired by the City of Denver doubted that an airport-wide automated baggage system could be designed, installed and tested by October 1993. On that advice, the city chose a conventional tug-and-cart system.
Task. Open the new airport on time with a baggage system that worked.
Action. In July 1991 the city reversed course and decided to build the integrated, automated system after all. In November 1991 the airlines' baggage subcommittee wrote that, according to the master project schedule, it would not be finished until mid-1994. The city signed a final contract of $195.6 million in May 1992, and a conventional backup system was contracted only in September 1994.
Result. The opening was delayed four times. The airport opened in February 1995, and the baggage system's cost had risen from about $195 million to more than $290 million.
What I would do differently, or repeat. Record every warning as a risk with an owner and a decision date, and start the fallback early rather than last.
Facts from Kanbanchi's Denver airport baggage system page.
Tell me about a time work started before the plan was ready.
What they are checking: That you understand why planning before execution matters, and what it costs to skip it.
Use your own project if you have one. If you do not, or if the interviewer asks about a project you have studied, a well-known case told in STAR form works well. Model answer:
Situation. In 1957, Jørn Utzon won the design competition for an opera house in Sydney. The estimate was £3.5 million, and the building was to open on Australia Day, Jan 26, 1963.
Task. Premier Joe Cahill, the project's political sponsor, wanted work to start quickly. The sod was turned on Mar 2, 1959, while the roof's weight and anchor points were still unknown.
Action. The podium was built first. About 700 concrete shafts had to be bored into the site, unbudgeted work, and the roof geometry was only solved in January 1962.
Result. The podium was finished in February 1963, two years behind schedule, and still needed substantial modification to suit the final roof. Queen Elizabeth II opened the building on Oct 20, 1973, at A$102 million, 1,357 percent over the original estimate and about ten years late.
What I would do differently, or repeat. Do not let a ceremony set the deadline: build the date from the work. Prove the structure before pouring the base, and baseline every stage, not just the start.
Facts from Kanbanchi's Sydney Opera House: planned vs actual page.
How would you prepare a big launch with a fixed date?
What they are checking: That you plan for testing, load and leadership, not only the build.
Use your own project if you have one. If you do not, or if the interviewer asks about a project you have studied, a well-known case told in STAR form works well. Model answer:
Situation. Open enrollment on the US federal health insurance marketplace was set for Oct 1, 2013. The Centers for Medicare & Medicaid Services issued the task order for the core federal system in September 2011, before key requirements were known.
Task. Launch a national marketplace on a fixed date.
Action. Requirements kept changing, and the HHS Inspector General found that no one held clear leadership of the project. The readiness assessment planned for March 2013 slipped to September 2013, weeks before launch.
Result. The site opened on the scheduled date and users met outages and errors at once: 250,000 people tried to use it at the same time, against 50,000 to 60,000 expected. A tech surge restored high consumer use within about two months.
What I would do differently, or repeat. Name one accountable leader, test at the expected load long before the date, and release in stages so problems surface while they are small. The big-bang risk is covered in Lesson 4.
Facts from Kanbanchi's HealthCare.gov: planned vs actual page.
How do you report whether a project is on budget?
What they are checking: That you report honestly and always say which baseline you mean.
Use your own project if you have one. If you do not, or if the interviewer asks about a project you have studied, a well-known case told in STAR form works well. Model answer:
Situation. London's 2005 bid for the 2012 Olympic and Paralympic Games put the estimated gross cost at just over £4 billion. On Mar 15, 2007, after detailed planning, the government announced a Public Sector Funding Package later restated as £9,298 million.
Task. Say whether the Games came in on budget.
Action. On Dec 5, 2012 the National Audit Office put the anticipated final cost at £8,921 million, about £377 million under the 2007 package. Against the 2005 bid, the same outturn is about 123 percent higher in nominal terms.
Result. Both statements are true and answer different questions. Oxford researchers called the public claim that London came in under budget misleading, because it rested on the revised 2007 baseline.
What I would do differently, or repeat. Name the baseline every time: "under budget against the approved 2007 package, and more than double the 2005 bid." Then explain why the baseline changed.
Facts from Kanbanchi's London 2012 Olympics: planned vs actual page.
How to prepare for a project management interview
- Read the job description twice. Note the method the team uses, such as scrum or waterfall, and the skills it lists. Prepare one story for each skill.
- Write three to five STAR stories from your own work. A project you led, one that went wrong, a conflict you resolved, a change you handled, a risk you caught. One story can answer several questions.
- Revise the core terms. Phases, baseline, critical path, scope creep, risk: the project management terms glossary has every definition used in the answers above.
- Practice out loud. Use the deck above until each answer takes about two minutes and ends with a result.
- Prepare questions for them. Ask how projects are approved, how they handle change requests and how success is measured.
If you are still building the experience behind your stories, start with our guide on how to become a project manager, which ends with a readiness self-check.
Try it on a real board: an interview prep board in Kanbanchi
Keep your stories and your applications in one place. In Kanbanchi, the task and project management app that works inside Google Workspace:
- Create a board with three lists: Stories to write, Ready to tell and Applications.
- Add a card for each STAR story, with the four parts in the description.
- Add a card for each job you apply to, with the interview date as the due date.
- Link the stories you plan to tell to each application card with a checklist.
- After each interview, add a comment on what went well and what to improve.
This step is optional. The guide works without an account.
More from Project Management 101
Build the experience behind your stories, look up any term, or revise the lessons the questions come from.
The course lessons
0 of 8 knowledge checks passed
- Lesson 1: The project life cycleThe five phases of a project and what each one produces · 7 minNot passed yet
- Lesson 2: The project management processFrom idea to closing, step by step · 6 minNot passed yet
- Lesson 3: Project management methodologiesEight methods compared, and how to pick one · 8 minNot passed yet
- Lesson 4: Agile vs waterfallThe real differences, played out on one project · 7 minNot passed yet
- Lesson 5: Scrum vs kanbanSprints or continuous flow · 7 minNot passed yet
- Lesson 6: What is a Gantt chart?Tasks, dependencies and the critical path · 7 minNot passed yet
- Lesson 7: How to prioritize tasksOur step-by-step guide on the Kanbanchi blogGuide, no check
- Lesson 8: Pre-mortem: spot risks earlyFind out why a project could fail, before it does · 6 minNot passed yet
- Lesson 9: Project manager skillsThe hard and soft skills, and how to build them · 6 minNot passed yet
Progress is saved in this browser only, with no sign-up. Pass all 8 knowledge checks to unlock the course badge on the course page.
Project management interview questions: FAQ
What are the most common project management interview questions?
Expect questions on the basics, such as the phases of a project, agile or waterfall, the critical path, scope creep and risk, and behavioral questions such as "tell me about a project that failed" or "how do you handle a difficult stakeholder?". This guide has model answers for 12 of them.
What is the STAR method?
STAR is a way to structure an answer to a behavioral interview question: describe the Situation, the Task you were responsible for, the Action you took and the Result. Keep the situation short and spend most of the time on your actions and the result.
Can I use a famous project as an example in an interview?
Yes, when the question is about a project you have studied, or to show how you think about a problem. For questions about your own experience, use your own project first, and use a famous case to add a lesson you have applied.
Will the Project Management 101 badge help in an interview?
It shows that you completed a free course on the basics. The "Completed Project Management 101 by Kanbanchi" badge is not a certification, and the course is not affiliated with PMI, the Project Management Institute, so present it as learning, alongside the projects you have led.