Interview questions

IT Project Manager Interview Questions

19 IT project manager interview questions on SDLC delivery, cutovers, vendors and technical risk, with what a strong answer sounds like. For both sides.

IT Project Manager Interview Questions

What's here

19 IT Project Manager interview questions, grouped into 4 areas: delivery and methodology, technical fluency and risk, stakeholders and vendors and situational questions. Each one comes with why it is worth asking and what a strong answer contains, so the same question can be scored the same way by different interviewers.

  • Ask for a real cutover or migration they ran and probe the details; generic project answers fall apart under two follow-up questions
  • Have an engineer on the panel to test whether the candidate can discuss technical risk credibly
  • Give a short scenario with a slipping vendor and a fixed date, and ask for the options they would put to a sponsor
For hiring teams

Cohesyve finds, contacts and tests IT Project Manager candidates on the real work, then ranks them for these interviews. 14-day free trial for 10 candidates, not charged until it ends.

Preparing for this interview yourself? Practise it free →

An IT project manager delivers technology change: system implementations, infrastructure upgrades, migrations and integrations, usually with a mix of internal engineers, vendors and business users who all want different things. These questions test whether someone can run that kind of project end to end, speak credibly to engineers, and protect go-live dates without hiding risk. Interviewers can use the 'what to look for' notes as a scoring guide; candidates can use them to see what a strong answer contains.

Delivery and Methodology

How the candidate plans, runs and closes technology projects, and how they pick an approach that suits the work.

  1. 1

    Walk me through the last IT project you took from kickoff to go-live. What was your role at each stage?

    Why ask it

    Separates people who ran a project from people who attended one. The stages they mention reveal how complete their delivery habits are.

    What to look for

    A clear arc: scope and business case, plan and resourcing, build and test, cutover, hypercare and handover to support. Strong candidates name the artefacts they owned (plan, RAID log, test plan, cutover runbook) and the decisions they personally made.
  2. 2

    When do you choose Agile, Waterfall or a hybrid for an IT project? Give an example of each.

    Why ask it

    IT work ranges from fixed-scope infrastructure jobs to evolving software builds. A good IT PM fits the method to the work.

    What to look for

    Waterfall or phased plans for hardware, network or compliance-driven work with fixed dependencies; iterative delivery where requirements are uncertain. Hybrids are common, e.g. Agile build inside a fixed release and cutover plan. Weak answers pick one method for everything.
  3. 3

    How do you build a schedule for a system implementation when the vendor, the internal IT team and the business all have their own timelines?

    Why ask it

    Integrated planning across parties is the core of the job.

    What to look for

    Working back from a fixed date or forward from dependencies, an integrated plan with named owners, explicit hand-off points, buffers on known-risky items (data migration, integrations, UAT) and agreed checkpoints with each party.
  4. 4

    What goes into a cutover plan, and how do you decide whether to go live or roll back?

    Why ask it

    Go-live is where IT projects fail visibly. This tests operational discipline.

    What to look for

    Step-by-step runbook with owners and timings, rehearsals, data validation checks, communication plan, support cover, and go/no-go criteria agreed in advance with a named decision-maker. Rollback steps should be tested, with a point of no return identified.
  5. 5

    How do you know a project is healthy halfway through? Which signals do you track?

    Why ask it

    Shows whether status reporting is real or decorative.

    What to look for

    Milestones against baseline, burn of budget and effort, open defects and their trend, risks and issues ageing, dependency status and team capacity. Good candidates talk about leading indicators (slipping test entry, unresolved design decisions) and admit when green status reports hid problems.
For hiring teams

Before the IT Project Manager interviews, see who can do the work

Cohesyve finds and contacts IT Project Manager candidates from your job description and tests each one on an AI job simulation of the role, so these questions go to a ranked shortlist. 14-day free trial for 10 candidates, not charged until it ends.

Technical Fluency and Risk

IT project managers do not need to write code, but they need enough depth to challenge estimates and spot technical risk early.

  1. 6

    Explain how you would manage a data migration from a legacy system to a new platform.

    Why ask it

    Migration problems often surface only at cutover, when they are hardest to fix. This shows whether the candidate plans for data quality, sign-off and fallback early.

    What to look for

    Data profiling and cleansing early, field mapping signed off by data owners, trial migrations, reconciliation counts and sample checks, a freeze window, and a fallback plan. Strong answers mention that business users must validate migrated data, not only IT.
  2. 7

    An engineer tells you a task will take three weeks. How do you judge whether that estimate is sound?

    Why ask it

    Tests whether the candidate can engage with engineers without either rubber-stamping or overruling them.

    What to look for

    Asking what the work breaks down into, what assumptions and unknowns exist, comparing against similar past work, and involving a second engineer. Respect for the engineer's expertise while making the uncertainty visible to stakeholders.
  3. 8

    What security and compliance checks do you build into an IT project plan?

    Why ask it

    Security reviews that arrive late can block go-live.

    What to look for

    Engaging security and compliance at design stage, access and data classification reviews, vendor security due diligence, penetration or vulnerability testing before go-live, and change-advisory approval. Candidates who treat security as a final sign-off box are a risk.
  4. 9

    How do you keep a RAID log useful instead of letting it become a list nobody reads?

    Why ask it

    Risk management in IT projects often exists on paper only.

    What to look for

    Few, specific risks with owners, probability and impact, mitigation actions with dates, a regular review rhythm, and escalation thresholds. Examples of a risk they spotted early that changed the plan.
  5. 10

    Describe a technical issue that threatened a go-live date. What did you do?

    Why ask it

    Real examples show judgement under technical pressure.

    What to look for

    Fast triage with the right engineers, clear options with trade-offs (delay, descope, workaround), a recommendation to the sponsor, and honest communication. Strong candidates explain what they changed afterwards to avoid a repeat.

Stakeholders and Vendors

Most IT projects succeed or fail on how well the PM manages sponsors, users and third parties.

  1. 11

    How do you manage a vendor who is consistently missing deliverables?

    Why ask it

    IT PMs often depend on suppliers they do not directly control.

    What to look for

    Facts first (missed milestones against the statement of work), an escalation path through the vendor's account and delivery leads, joint recovery plan, use of contractual levers where needed, and keeping procurement and the sponsor informed.
  2. 12

    Business users are pushing for new features late in the project. How do you handle it?

    Why ask it

    Late feature requests test whether the candidate can protect scope, time and budget without alienating the business.

    What to look for

    A change control process: log the request, assess impact on time, cost and risk, present options to the sponsor, and either approve with a re-baselined plan or defer to a later release. Tone matters: firm on process, respectful of the need.
  3. 13

    How do you explain a technical delay to a non-technical executive sponsor?

    Why ask it

    Translation between engineering and leadership is a core IT PM skill.

    What to look for

    Plain language, impact on business outcomes and dates, what caused it in one or two sentences, options and a recommendation, and what decision is needed. No jargon and no blame.
  4. 14

    Tell me about a time you had to get buy-in from end users who did not want a new system.

    Why ask it

    Adoption decides whether a technically successful project delivers value.

    What to look for

    Early involvement of users, champions in each team, training timed close to go-live, listening to real objections and fixing some of them, and measuring adoption after launch.

Situational Questions

Scenarios that mirror the decisions IT project managers face in the run-up to and after go-live.

  1. 15

    UAT is due to start Monday, but the build has a long list of open defects. What do you do?

    Why ask it

    Tests whether the candidate protects quality or protects the date at any cost.

    What to look for

    Triage defects by severity, agree UAT entry criteria with the business, consider starting UAT on stable modules only, and re-plan openly if criteria are not met. Starting UAT on a broken build to hit a date is a red flag.
  2. 16

    Two weeks before go-live, the key engineer on the integration resigns. How do you respond?

    Why ask it

    Single points of failure are common on IT teams.

    What to look for

    Immediate knowledge transfer during notice period, documentation of the integration, pairing with a backup, vendor or contractor support, and a frank reassessment of the date with the sponsor.
  3. 17

    The project is on schedule but forecast to run over budget. The sponsor wants the date held. What options do you present?

    Why ask it

    Checks commercial thinking and the ability to frame trade-offs.

    What to look for

    Quantified options: request contingency, descope lower-value items, phase delivery, change resourcing mix. Each with impact on scope, risk and value, and a recommendation.
  4. 18

    After go-live, the service desk is flooded with tickets about the new system. What is your plan for the first week?

    Why ask it

    Hypercare is often under-planned.

    What to look for

    A hypercare team with daily triage, categorising tickets into defects, training gaps and change requests, quick fixes and user comms, clear exit criteria for handing over to business-as-usual support.
  5. 19

    You join a troubled IT project mid-flight. What do you do in your first two weeks?

    Why ask it

    Many IT PMs are hired to rescue projects.

    What to look for

    Listen first: one-to-ones with team, vendor and sponsor; review plan, budget, RAID and defect data; establish the real status; then reset the plan with the sponsor. Candidates who promise quick heroics without diagnosis are a concern.

Running the interview well

  • 1Ask for a real cutover or migration they ran and probe the details; generic project answers fall apart under two follow-up questions
  • 2Have an engineer on the panel to test whether the candidate can discuss technical risk credibly
  • 3Give a short scenario with a slipping vendor and a fixed date, and ask for the options they would put to a sponsor
  • 4Ask to see a status report or RAID log they wrote (with sensitive details removed) to judge how they communicate
  • 5Check certifications such as PMP or PRINCE2 as a plus, but score delivery evidence above them

Common questions

What is the difference between an IT project manager and a general project manager?

An IT project manager runs technology work: implementations, migrations, infrastructure and integrations. They need enough technical understanding to plan around environments, testing, data migration and cutover, and to challenge engineering estimates. The project management fundamentals are the same.

How should I prepare for an IT project manager interview?

Prepare two or three detailed project stories, ideally including one go-live and one project that went wrong. Be ready to explain your planning, how you managed vendors and scope, how you handled technical risk, and what you would do differently. Bring numbers you can stand behind, such as budget size or team size.

Do IT project managers need a certification?

Many employers list PMP, PRINCE2 or an Agile certification as preferred. Interviewers usually weigh real delivery experience more heavily, so describe what you delivered as well as the credentials you hold.

For hiring teams

Save these questions for the IT Project Manager candidates who can do the work

Cohesyve takes your IT Project Manager job description, finds candidates, reaches out to them and runs an AI job simulation of the real work, then returns a ranked shortlist.

1,500+

assessments completed

50%

faster time-to-hire

5 min

from JD to assessment

14-day free trial · 10 candidates · Not charged until the trial ends

For job seekers

Preparing for an IT Project Manager interview yourself? Practise on an AI job simulation of the role. 3-day free trial, cancel anytime.

Practise an IT Project Manager interview free →

See Cohesyve in action

Free 30-min walkthrough

See it on your role