IT Project Manager Interview Questions: 20 Questions With Model Answers
Project management interviews mix three things: your knowledge of the vocabulary, your judgement in realistic situations and your ability to communicate under pressure. Interviewers rarely want textbook definitions alone; they want to hear how you think and what you have actually done. This lesson gives twenty common questions with model answers you can adapt. Use your own experience and numbers, since a memorised answer is easy to spot.
How to Structure Your Answers
For behavioural questions, use the STAR approach: Situation (context, briefly), Task (your responsibility), Action (what you did and why) and Result (measurable outcome and what you learned). Spend most of your time on action and result. For scenario questions, state your assumptions, explain the steps and mention trade-offs. If you lack direct experience, say so honestly and describe how you would approach it.
Fundamentals
1. What is the difference between a project, a programme and a portfolio?
Model answer: A project is a temporary effort to create a unique product, service or result. A programme groups related projects managed together to get benefits not available from managing them separately. A portfolio is the set of projects and programmes an organisation funds to meet strategic goals. For example, a retailer’s digital programme might contain website, mobile app and payments projects, within a portfolio that also includes warehouse and finance projects.
2. Explain the triple constraint and how you manage it.
Model answer: Scope, time and cost are linked: a change in one affects the others, and quality suffers if they are squeezed silently. At the start I ask the sponsor which is fixed and which can flex, and record it in the charter. When changes arrive, I present options with numbers, such as reducing scope, extending the date or adding budget, and let the sponsor decide. See Projects vs Operations and the Triple Constraint.
3. How do you decide between Agile, Waterfall and a hybrid approach?
Model answer: I look at how stable the requirements are, the risk and compliance needs, how available the customer is, contract constraints and the team’s experience. Stable, regulated work favours predictive methods; evolving products favour Agile. Often I use hybrid: governance, budget and milestones at programme level, and iterative delivery inside the build phase. I explain the rules to the team and sponsor so everyone knows which controls apply. See SDLC Models Compared.
4. What are the process groups in a project?
Model answer: Initiating, planning, executing, monitoring and controlling, and closing. Monitoring and controlling runs throughout, and the groups repeat inside phases. Initiating produces the charter and stakeholder register; planning produces scope, schedule, budget and risk plans; executing delivers the work; monitoring and controlling tracks and manages change; closing hands over and captures lessons.
Planning and Control
5. How do you build a project plan from scratch?
Model answer: I start from the charter and business case, gather requirements and agree the scope statement. I break scope into a WBS, define activities and dependencies, estimate with the people doing the work, build the schedule and critical path, and check resource availability. I add a budget with contingency tied to risks, and plans for risk, quality and communication. Then I get the baseline approved by the sponsor. See Scope Statement and WBS.
6. What is the critical path, and why does it matter?
Model answer: It is the longest sequence of dependent activities and sets the minimum project duration. Activities on it have zero float, so any delay delays the project. I monitor it closely, use float on other paths to level resources and compress the schedule only by crashing or fast tracking critical activities. See Project Scheduling.
7. A project has a budget of ₹60 lakh, EV of ₹24 lakh and AC of ₹30 lakh. What do you conclude?
Model answer: CPI is 24 divided by 30, which is 0.8, so we are getting 80 paise of value per rupee. The cost variance is minus ₹6 lakh. If the trend continues, the estimate at completion is 60 divided by 0.8, which is ₹75 lakh, a ₹15 lakh overrun. I would investigate the cause, check whether it is one-off or systemic, and take options to the sponsor rather than wait. See Earned Value Management Explained.
8. How do you estimate when information is limited?
Model answer: I give ranges, not single numbers, state assumptions and use techniques suited to the stage: analogous from similar projects early, three-point estimates for uncertain tasks and bottom-up as scope becomes clear. I involve the people who will do the work and promise to refine the estimate at defined points. See Estimating IT Projects.
9. How do you handle scope creep?
Model answer: By preventing it with a clear scope statement including exclusions, and managing it with a change process. Every request is logged, assessed for impact on time, cost, quality and risk, and decided by the right authority. I present trade-offs to the sponsor, such as “we can add this for twelve days and ₹6 lakh, swap it with something equal, or defer it”, instead of refusing outright. See Scope Creep and Change Control.
Risk, Issues and Quality
10. What is the difference between a risk and an issue? Give an example.
Model answer: A risk is an uncertain future event; an issue is already happening. “The vendor API may be late” is a risk; once it is late, it is an issue. I manage risks with owners, responses and triggers, and issues with owners, actions and escalation. See Project Risk Management.
11. Tell me about a risk you identified early that prevented a problem.
Model answer structure: Situation: a payments integration depended on a vendor specification not yet confirmed. Task: protect the schedule. Action: I logged it as a high risk, built an early prototype to test assumptions, added a spec sign-off date to the contract and asked the vendor’s manager for a named technical contact. Result: the prototype exposed two mismatches in week three, avoiding about a month of rework. Use your own example with real numbers.
12. How do you ensure quality on a project?
Model answer: I define quality criteria and acceptance criteria with the sponsor at the start, plan testing at unit, integration, system and UAT levels, set entry and exit criteria, track defects by severity, and involve users early through demos. I do not compress testing to hit a date without telling the sponsor what risk that adds. See Quality Management and Testing.
People and Stakeholders
13. How do you manage a difficult stakeholder?
Model answer: First I try to understand the concern behind the behaviour, which is often fear, lack of information or a competing priority. I meet privately, listen, find shared goals and agree specific actions. I involve them in decisions that affect them. If it still blocks progress, I escalate to the sponsor with facts, not complaints. See Stakeholder Identification and Analysis.
14. How do you motivate a team you have no formal authority over?
Model answer: I explain the purpose, give people autonomy over how they do their work, remove obstacles quickly, recognise contributions specifically and build trust through fairness and honesty. I also work with their line managers to align priorities and feedback. Influence comes from credibility.
15. Two team members are in conflict and it is affecting delivery. What do you do?
Model answer: I speak to each privately to understand their view, then bring them together to focus on the shared goal and the specific behaviours or decisions at issue, not personalities. I look for a solution that serves both, document agreements and follow up. If it is a structural problem such as unclear roles, I fix that, perhaps with a RACI matrix. See Resource Management and Team Building.
Delivery Scenarios
16. Your project is two weeks behind and the sponsor wants the original date. What do you do?
Model answer: I first confirm the facts: where the delay is, whether it affects the critical path and why it happened. Then I develop options: crash critical activities with added resources, fast track with risk, reduce scope to essentials or move the date. I quantify cost, risk and quality effect for each, recommend one and ask the sponsor to decide. I do not hide the delay or promise recovery I cannot support.
17. A key developer resigns midway through the project. How do you respond?
Model answer: I arrange knowledge transfer immediately, pair a colleague on the work, document critical items, review the schedule and critical path for impact, and look at replacement options such as internal reallocation or contractors. I update the risk register, inform the sponsor of the effect and options, and consider whether to reduce single points of failure on the rest of the team.
18. How would you prepare for a go-live?
Model answer: With a readiness checklist and a formal go/no-go meeting using predefined criteria; a rehearsed cutover runbook with owners and timings; tested rollback and clear decision points; trained users and support; and a hypercare plan with exit criteria. See Go-Live, Deployment and Cutover Planning.
19. Describe a project that failed or struggled. What did you learn?
Model answer structure: Choose a real example, take ownership without blaming others, explain the root causes (for example, requirements were not validated with end users) and describe specific practices you changed afterwards, such as monthly demos or earlier data profiling. Interviewers value honesty and learning more than a flawless record. See Why IT Projects Fail.
20. Why do you want to be a project manager, and where do you see yourself in three years?
Model answer: Connect your motivation to the work itself: enjoying bringing people and plans together to deliver something concrete, and building skills in planning, communication and leadership. Mention your learning plan, such as certifications or a move into larger programmes, and tie it to the value you would bring this employer. See PMP vs PRINCE2 vs CAPM vs PMI-ACP.
Questions to Ask the Interviewer
- What are the biggest challenges the current projects face?
- How are projects governed and how are priorities set?
- What is the balance between Agile and predictive work here?
- How does the organisation measure project success?
- What support does the PMO or leadership provide?
Preparation Checklist
- Prepare five STAR stories: a success, a failure, a conflict, a change request and a risk you managed.
- Practise the formulas and techniques: EVM, critical path, PERT and probability-impact scoring.
- Research the company’s projects, industry and methodology.
- Bring examples of artefacts you have produced, with confidential information removed.
- Rehearse answers aloud, aiming for two minutes each.
If you are also preparing for Agile roles, see Scrum Master Interview Preparation.
- Use STAR for behavioural questions; state assumptions for scenario questions.
- Show judgement: facts first, options with trade-offs, a recommendation and escalation when needed.
- Back answers with numbers and your own examples, including an honest failure story.
- Know the core techniques: scope control, critical path, EVM, risk responses and go-live readiness.