# Project Manager interview questions and answers Source: https://digitalcvmaker.com/interview-questions/project-managers Last updated: 2026-10-01 Project manager interviews test whether you can deliver work on time, within budget and to the agreed scope while keeping stakeholders aligned. Expect questions on scheduling, critical path, change control, risk, earned value, agile and hybrid delivery, vendor contracts and status reporting, plus stories about conflict and slipping deadlines. Practise the 20 questions below out loud, compare with the sample answers and prepare for the follow-ups. Project manager hiring usually runs as an HR screen, one or two rounds with a delivery head or programme manager that include a case on a delayed or troubled project, sometimes a client or stakeholder round, and a final HR discussion. ## Role and technical questions ### 1. What is the difference between a project, a programme and a portfolio? Round: Role · Level: Fresher **What they’re checking:** Whether you know the basic vocabulary of project management and understand how individual projects connect to business goals above them. **Sample answer:** > A project is a temporary effort with a defined scope, start and end, such as rolling out a new billing system to one region. A programme is a group of related projects managed together because their benefits depend on each other, for example billing, CRM and customer portal projects that together form a digital transformation. A portfolio is the full set of projects and programmes an organisation runs, chosen and prioritised against strategy and budget. So a project manager focuses on delivering outputs, a programme manager on combined benefits, and portfolio management on choosing the right work in the first place. **Likely follow-ups:** - Who decides which projects enter the portfolio? - What is a PMO and what does it do? ### 2. How do you find the critical path of a project, and what does float tell you? Round: Role · Level: Fresher **What they’re checking:** Whether you can actually schedule a project using a network diagram, not just name the term, and understand which tasks can slip. **Sample answer:** > I list activities with durations and dependencies, then draw the network. In a forward pass I calculate the earliest start and earliest finish of each activity. In a backward pass from the project end date I calculate the latest start and latest finish. Total float is latest start minus earliest start. Activities with zero float form the critical path, the longest path through the network, and any delay on them delays the whole project. Float tells me how much a non-critical task can slip without moving the end date, so I can shift resources from those tasks to protect the critical ones. **Likely follow-ups:** - What is the difference between total float and free float? - Can a project have two critical paths? ### 3. A client keeps asking for small additions to the scope. How do you handle scope creep? Round: Role · Level: All levels **What they’re checking:** Whether you protect scope through a clear change process while staying helpful to the client, rather than saying yes to everything or refusing everything. **Sample answer:** > First I make sure the baseline scope is written down clearly, with a signed statement of work and acceptance criteria. When a new request comes, I log it in the change register, even if it sounds small. I then assess the impact on effort, schedule, cost and risk with the team, and present options to the client: add it with revised timeline and cost, swap it for something of similar size, or move it to a later phase. Nothing gets built until the change is approved by the right person. On a CRM rollout, this process turned fourteen informal asks into three approved changes and a phase-two list. **Likely follow-ups:** - What if the client says it is a defect, not a change? - Who sits on a change control board? ### 4. How do you build a work breakdown structure and estimate effort for a new project? Round: Role · Level: All levels **What they’re checking:** Whether you plan from deliverables down to work packages and use more than one estimation technique, involving the people who will do the work. **Sample answer:** > I start from the deliverables in the scope statement, not from activities. Each deliverable is broken into smaller components until I reach work packages that one team can own and that take roughly one to two weeks. Then I estimate with the people doing the work. For familiar work I use analogous estimates from past projects. For uncertain work I use three-point estimates, optimistic, most likely and pessimistic, and take the weighted average. I add contingency based on the risk register rather than padding every task. Finally I check the bottom-up total against a top-down sanity estimate. **Likely follow-ups:** - What is the 8/80 rule? - How do you estimate when the team has never done similar work? ### 5. Your project has a CPI of 0.8 and an SPI of 0.8. What does that mean and what will you do? Round: Role · Level: Experienced **What they’re checking:** Whether you can read earned value metrics, forecast the outcome and turn the numbers into a recovery plan rather than just reporting them. **Sample answer:** > CPI is earned value divided by actual cost, and SPI is earned value divided by planned value. Both at 0.8 means we are getting only 80 paise of work for every rupee spent, and we have done only 80 percent of the work planned by now. If the budget at completion is ₹50 lakh, a simple forecast is 50 divided by 0.8, about ₹62.5 lakh, if performance does not change. I would find where the variance comes from, often one or two work packages, check whether estimates were wrong or productivity is low, and then present the sponsor with options: recover, re-baseline or reduce scope. **Likely follow-ups:** - What is TCPI and when is it useful? - Why can SPI be misleading near the end of a project? ### 6. When would you choose waterfall, agile or a hybrid approach for a project? Round: Role · Level: All levels **What they’re checking:** Whether you pick a delivery approach based on the project’s certainty and constraints, rather than following a preference or a fashion. **Sample answer:** > Waterfall suits work where requirements are stable and changes are costly late on, such as an office fit-out, a data centre move or a regulatory system with fixed rules. Agile suits product work where requirements will change as users give feedback, like a customer app. Many projects need a hybrid. At a mid-size IT services firm I managed an ERP rollout where contract, data migration and go-live followed a fixed phase plan, while the custom reports and integrations ran in two-week sprints with demos to the finance team. The phase gates kept the client’s auditors comfortable, and the sprints let users shape the reports. **Likely follow-ups:** - How do you report progress in a hybrid project? - What is the role of a project manager in Scrum? ### 7. How do you maintain a risk register, and what responses can you choose for a risk? Round: Role · Level: All levels **What they’re checking:** Whether you manage risk actively through the project instead of filling a register once at kickoff and forgetting it. **Sample answer:** > I run a risk workshop at kickoff with the team and key stakeholders, then keep the register live. Each risk is written as cause, event and effect, with probability, impact, an owner and a trigger to watch. For threats I can avoid, for example by changing the plan, transfer through insurance or a fixed-price contract, mitigate by reducing probability or impact, or accept with a contingency. For opportunities I can exploit, share, enhance or accept. I review the top risks in every weekly meeting. On a branch rollout, an early trigger on vendor delivery let us switch suppliers before it hit the critical path. **Likely follow-ups:** - What is the difference between a risk and an issue? - How do you size contingency reserve? ### 8. The project is three weeks behind with a fixed launch date. How do you compress the schedule? Round: Role · Level: Experienced **What they’re checking:** Whether you know schedule compression techniques and their trade-offs, and whether you look at the critical path before throwing people at the problem. **Sample answer:** > I first confirm the delay is on the critical path, because slipping non-critical work may not matter. Then I look at two techniques. Fast tracking runs activities in parallel that were planned in sequence, for example starting user training while final testing finishes. It costs little but adds rework risk. Crashing adds resources to critical activities, such as extra testers or overtime, which raises cost and works only where the task can actually be split. I would also check whether some scope can move after launch. I present the options with cost and risk to the sponsor, so the decision is theirs and recorded. **Likely follow-ups:** - Why does adding people to a late software project sometimes make it later? - How do you keep the team from burning out during a crunch? ### 9. How do you prepare a status report for a steering committee? Round: Role · Level: All levels **What they’re checking:** Whether you communicate honestly and briefly to senior people, highlighting decisions needed rather than burying them in activity lists. **Sample answer:** > I keep it to one page. At the top is an overall RAG status for schedule, cost, scope and quality, with one line explaining any amber or red. Then milestone progress against baseline dates, budget spent against plan, and the top three risks and issues with owners. The most important section is decisions needed from the committee, with a recommendation and a date. I avoid long activity lists. If something is turning red, I tell the sponsor before the meeting, so they are never surprised in front of others. I also keep the RAG definitions fixed, so green means the same thing every week. **Likely follow-ups:** - What do you do if a sponsor asks you to show red as amber? - How often should a steering committee meet? ### 10. How do fixed-price and time-and-materials contracts change the way you manage a vendor? Round: Role · Level: Experienced **What they’re checking:** Whether you understand how contract type shifts risk between buyer and vendor and how that affects scope control, monitoring and change handling. **Sample answer:** > In a fixed-price contract the vendor carries cost risk, so scope must be very clear upfront and every change becomes a formal change request with a price. My focus is on acceptance criteria, milestone payments tied to deliverables and tight change control, because vague scope leads to disputes. In time-and-materials the buyer carries the risk, so I watch productivity closely: weekly timesheets, burn against plan, and output per sprint. It suits work where scope will evolve. On one data migration, we used time-and-materials for discovery and then fixed price for the bulk migration once the data volume and rules were known. **Likely follow-ups:** - What clauses do you check in a vendor contract? - How do you handle a vendor who keeps missing milestones? ### 11. What is the difference between resource levelling and resource smoothing? Round: Role · Level: Fresher **What they’re checking:** Whether you know how to handle over-allocated people in a schedule and understand which technique can move the end date. **Sample answer:** > Both deal with uneven or over-allocated resources. Resource levelling adjusts start and finish dates to match resource limits, for example when one database specialist is booked on two tasks the same week. Because it can push critical activities, it may extend the project end date and change the critical path. Resource smoothing only moves activities within their available float, so the end date does not change, but it may not remove every over-allocation. In practice I first smooth, and if a key person is still overloaded, I level or bring in another resource, and I show the date impact to the sponsor. **Likely follow-ups:** - How do you manage a person shared across three projects? - Which tools do you use for resource planning? ## Behavioural questions ### 12. Tell me about a time two senior stakeholders wanted conflicting things from your project. Round: Behavioural · Level: Experienced **What they’re checking:** Whether you can manage conflict between powerful people by using facts and the agreed objectives, without taking sides or escalating too early. **Sample answer:** > On a warehouse management rollout, the operations head wanted go-live before the festive peak, while the finance controller wanted it after, to avoid month-end risk. Both had valid reasons. I met each separately to understand their real concern, then put together a one-page comparison: risk to peak operations if we waited, and risk to closing if we went early. I proposed a middle path: go live at two smaller warehouses first, then the main one after the peak. I took it to the sponsor with both of them in the room. They agreed, and the pilot exposed two issues we fixed before the big site. **Likely follow-ups:** - What if they had not agreed? - How did you keep both of them engaged afterwards? ### 13. Describe a time you had to tell a client that a milestone would be missed. Round: Behavioural · Level: All levels **What they’re checking:** Whether you deliver bad news early and honestly, with a recovery plan, rather than hiding problems until the deadline. **Sample answer:** > Midway through a payroll system implementation for a manufacturing client, the data migration from their old system was taking far longer because employee records had many inconsistencies. By week six I could see the user acceptance milestone would slip by about two weeks. I called the client sponsor the same day instead of waiting for the monthly review. I explained the cause with examples, what we had already tried, and two options: add two data cleansing staff from their HR team, or move the milestone. They chose to lend us staff, and we slipped by only five days. The sponsor later said the early call built trust. **Likely follow-ups:** - How did you document the change in the plan? - What did you do differently on the next project? ### 14. How did you handle a team member who repeatedly missed deadlines on your project? Round: Behavioural · Level: All levels **What they’re checking:** Whether you address performance issues directly and fairly, find the cause, and protect delivery without public blame. **Sample answer:** > A developer on my team missed three task deadlines in a row on an insurance portal project. Rather than raising it in the stand-up, I spoke to him privately and asked what was happening. It turned out he was also supporting a production system for another manager, and nobody had accounted for that time. I spoke to the other manager and we agreed to a fixed split of his week, which I reflected in the plan. I also broke his tasks into smaller pieces with mid-week check-ins. Over the next month he hit every date, and the hidden dependency was removed for others too. **Likely follow-ups:** - What if the issue had been his attitude? - When would you involve HR? ### 15. Tell me about a project that failed or was cancelled. What did you learn? Round: Behavioural · Level: Experienced **What they’re checking:** Whether you take ownership of a failed project, can analyse what went wrong honestly and actually changed your approach afterwards. **Sample answer:** > I managed a mobile app for a retail chain’s loyalty programme that was cancelled after five months. We delivered most features, but the business sponsor changed and the new head did not see the value. Looking back, I had focused on delivery and not enough on benefits. We never agreed measurable outcomes, such as repeat purchase rate, and I did not build support beyond the original sponsor. Since then I agree success measures in the project charter, report progress against them, and keep at least two senior supporters informed. On my next project, that helped us survive a budget review. **Likely follow-ups:** - Could you have stopped the project earlier? - How do you write a lessons-learned report? ### 16. Tell me about a time you pushed back on a deadline set by senior management. Round: Behavioural · Level: All levels **What they’re checking:** Whether you can say no with evidence and options, and whether you protect quality and the team without appearing obstructive. **Sample answer:** > Our director promised a client that a new reporting module would be ready in four weeks. The team’s estimate was seven. I did not simply say it was impossible. I went back with the estimate broken down, showing which parts were fixed effort, and three options: deliver the five most used reports in four weeks and the rest by week seven, add a contractor who knew the reporting tool, or move the date. He chose the phased option and explained it to the client. We hit both dates, and he started asking for estimates before committing timelines. **Likely follow-ups:** - What if he had insisted on the full scope in four weeks? - How did the team react? ### 17. How have you managed a team spread across cities or time zones? Round: Behavioural · Level: Fresher **What they’re checking:** Whether you can coordinate people you do not sit with, using clear routines and written communication, which most project roles now require. **Sample answer:** > In my first role as a project coordinator, our team for a website migration was split between Bengaluru, Pune and a client team in Dubai. Early on, messages got lost and work was duplicated. I set up a short daily call at a time that suited all three locations, a shared task board where every item had one owner, and a weekly written summary for the client. I also kept a decisions log, so people who missed a call could catch up. Duplicate work stopped, and the client said the weekly summary was the most useful thing we sent. **Likely follow-ups:** - Which tools did you use? - How do you build trust with people you have never met? ## HR round questions ### 18. Do you hold a PMP, PRINCE2 or similar certification, and how has it changed the way you work? Round: HR · Level: All levels **What they’re checking:** Whether your certification reflects real practice and whether you can apply frameworks sensibly rather than reciting them. **Sample answer:** > I cleared PMP after four years of managing projects. The certification itself did not make me a better manager overnight, but preparing for it gave me a common language and filled gaps. Earlier I tracked schedule well but treated risk informally. Now I run a proper risk workshop at the start and review risks every week, and I use earned value on larger projects to forecast cost early. I also learned to tailor, so a two-month internal project gets a light charter and a simple plan, not a full set of documents. I keep up the required learning hours mainly through agile and contract management courses. **Likely follow-ups:** - Which part of the framework do you skip on small projects? - Are you planning any further certification? ### 19. What are your salary expectations for this project manager position? Round: HR · Level: Experienced **What they’re checking:** Whether you have a clear, reasoned number linked to the scope of the role, and whether you can discuss it calmly. **Sample answer:** > I currently manage projects of about ₹3 to 5 crore with teams of twelve to fifteen at an IT services company, at a CTC of ₹18 lakh. This role covers larger programmes and direct client ownership, so I am looking for ₹22 to 24 lakh fixed. I understand there may be a variable component tied to delivery and client satisfaction, and I am comfortable with that if the measures are clear. I would also like to know about certification support and how project bonuses work here, because those affect the overall picture for me. **Likely follow-ups:** - What if the fixed part is lower than you expect? - Do you have other offers in hand? ### 20. How will you hand over your current projects if you join us, and how soon can you start? Round: HR · Level: All levels **What they’re checking:** Whether you will leave your current employer responsibly, which tells the interviewer how you would treat their projects too. **Sample answer:** > My notice period is 60 days. I currently run two projects, one about to enter user testing and one in early planning. For the first, I would document the plan, risks, open issues and stakeholder contacts, and introduce my successor to the client in at least two meetings before I leave. For the second, my deputy is already involved, so the handover is simpler. If you need me sooner, I can ask for an early release after the user testing phase starts, which might bring it down to about 45 days. I would rather leave cleanly than rush, because I would expect the same from anyone joining my team. **Likely follow-ups:** - What if your employer refuses early release? - Can you join part-time before your last day? ## How to prepare for a project manager interview - Prepare two project stories in detail: one that went well and one that went wrong, with numbers for budget, team size, schedule and outcome. - Revise critical path, earned value, risk responses and change control, because case rounds often ask you to calculate or apply them on the spot. - Bring a sanitised sample of your status report, RAID log or project plan, with client names removed, to show how you actually work. - Be ready to explain how you tailor process to project size, since interviewers distrust candidates who apply heavy documentation to every project. - Practise answering stakeholder conflict and delay questions with facts, options and a recommendation, which is how good project managers present problems. ## Questions about project manager interviews ### What do project manager interviews usually focus on? They focus on delivery: planning and scheduling, managing scope and change, risk, budget tracking, stakeholder communication and team leadership. Many include a case where a project is late or over budget and you explain your next steps. Experienced candidates are asked about vendor contracts, steering committees and recovering troubled projects, while junior candidates get more questions on tools and basic techniques. ### Is PMP certification required to get a project manager job? Not always. Many employers list PMP, PRINCE2 or an agile certification as preferred, and some client contracts require certified managers. But interviewers care more about whether you have delivered real projects and can explain how. A certification helps you get shortlisted and gives a shared vocabulary, while your project stories and numbers decide the interview. ### How can a fresher or coordinator move into a project manager role? Start by owning a small project or a clear workstream inside a larger one, and track it properly with a plan, risks and status reports. Learn a scheduling tool and basic earned value. Ask to run stand-ups or client updates. In interviews, describe these responsibilities with outcomes, and consider an entry-level certification such as CAPM or a foundation-level course to show intent.