IT project manager screening questions: delivery, cutovers, vendors and change control
On this page
- What kind of IT project?
- Knockout questions
- Delivery lifecycle questions
- Cutover, go-live and rollback questions
- Vendors and statements of work
- Change control in production
- Budget and resourcing in IT terms
- IT-related certifications
- How IT project manager resumes overstate the work
- Knockout checklist and scorecard
- Legal cautions
- Questions people ask
IT project manager screening questions should place the candidate's projects first (infrastructure, software delivery, ERP or SaaS implementation, data migration, security), then test the parts of IT delivery that general project management questions miss: environments and test exit criteria, cutover and rollback plans, vendor statements of work, and change control in a live production environment. A candidate who has run IT go-lives can describe one step by step, with owners and a go or no-go decision.
This page builds on project manager phone screen questions, which covers scope and budget ownership, stakeholder conflict, schedule recovery and the main certifications for any project manager. Use that page for the general questions and this one for the IT layer. If the role is mostly facilitating Scrum teams, see scrum master screening questions.
What kind of IT project?
| Type | What the work looks like | Facts to ask for |
|---|---|---|
| Infrastructure and cloud | Data center moves, network refreshes, cloud migrations, device rollouts | Number of sites or users, maintenance windows, who did the technical work |
| ERP, CRM or SaaS implementation | Configuration with an implementation partner, data conversion, training, go-live | System, modules, partner, number of users, how many go-lives they led |
| Software delivery | Releases with development teams, often agile, integrations with other systems | Team size, release cadence, who owned the backlog |
| Data migration or integration | Moving records between systems, reconciliation, cutover | Record volumes, number of mock loads, reconciliation method |
| Security or compliance remediation | Audit findings, identity and access changes, tooling rollouts | Framework or audit driver, deadline, who signed off |
Knockout questions
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| This role leads [type] projects for [system or environment]. Which of your projects is closest? | Names one, with size, their role and the outcome. | Only adjacent work, presented as a match. |
| Go-lives here happen in [weekend or overnight] windows. How have you handled that? | Has done it and plans for it realistically. | Surprised by off-hours cutovers. |
| The client requires [PMP, ITIL, clearance, none]. Do you hold it, and is it current? | Names it and the date; for a clearance, says only what level they hold or held and whether it is active, as the client asks. | "In progress" with no date. |
| Are you legally authorized to work in the US, and will you now or in the future need visa sponsorship? | A direct answer to both. | None. Ask everyone the same two questions; see work authorization questions. |
Delivery lifecycle questions
-
"Which environments did your last project use, and how did changes move between them?"
- Strong answer: names the environments (development, test, staging or user acceptance, production), who promoted changes, and how they kept configuration or data in step between them.
- Red flags: no idea how code or configuration reached production.
-
"What were the exit criteria for user acceptance testing?"
- Strong answer: a defined set: test cases executed, no open critical defects, an agreed number of lower-severity defects with workarounds, and named business sign-off.
- Red flags: "When the business was happy."
-
"How did you track defects, and who decided severity?"
- Strong answer: a tool, a triage meeting with business and technical leads, and an agreed severity definition.
- Red flags: the project manager set all severities alone, or nobody did.
Cutover, go-live and rollback questions
This is the section that separates IT project managers from general ones. Ask for the last real go-live, not a hypothetical.
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| Walk me through your last cutover plan. | A timed runbook with tasks, owners and dependencies; communications; a freeze period; dress rehearsals or mock cutovers; checkpoints. | "The vendor handled it." |
| Who made the go or no-go decision, and on what criteria? | Names the decision makers and criteria (test results, data reconciliation, readiness of support and users). | No defined decision point. |
| What was the rollback plan, and what would have triggered it? | Specific triggers and a time limit after which rollback was no longer possible, plus who could call it. | "We didn't need one." |
| What happened in the first two weeks after go-live? | Hypercare: a support model, daily triage, a defect burn-down, handover to operations with criteria. | Moved to the next project the day after go-live with no handover. |
Reading a data migration answer (invented example)
A candidate says they "migrated 2 million customer records". Ask how many mock loads they ran, how they reconciled counts and values between systems, and what share of records failed in the first mock. A candidate who ran it will give numbers like "three mocks, about 4% failed the first time, mostly bad addresses, under 0.1% by the final mock". One who did not will repeat the headline.
Vendors and statements of work
- "Did you manage an implementation partner or vendor? Who signed the statement of work?" Strong: knows the SOW's deliverables, milestones and acceptance criteria, and who owned the contract. Red flag: has never read the SOW.
- "Tell me about a change request with a vendor." Strong: assessed scope, cost and schedule impact, took it through the change process, and got it approved before work started. Red flag: let the vendor bill for work nobody approved.
- "A vendor misses a milestone. What do you do?" Strong: facts first, the contract's remedies, a recovery plan with dates, and escalation to the sponsor if needed.
Change control in production
Many IT projects end in an operations team's change process. Ask how the candidate worked with it. For the people side of change (adoption, training, resistance), use interview questions for change management.
| Question | What a strong answer sounds like | Red flags |
|---|---|---|
| How did production changes get approved where you worked? | Describes the change advisory process, risk categories, change windows and lead times. | Pushed changes outside the process to hit a date. |
| Who owned the system after go-live? | Names the support team and the handover criteria they agreed. | Unclear ownership. |
| How did security or compliance requirements affect your project? | A concrete example: access reviews, a security sign-off gate, data handling rules. | "Security reviewed it at the end." |
Budget and resourcing in IT terms
- "What made up the budget on your last project?" Strong: separates software licenses or subscriptions, partner fees, internal and contractor hours, hardware or cloud costs, and contingency. Red flag: one number with no idea what was in it.
- "How did you get time from engineers who also supported production?" Strong: agreed allocations with their managers, planned around incidents and on-call, and raised conflicts early. Red flag: assumed full-time availability.
- "What did you report to the sponsor each week?" Strong: status against milestones, budget burn, top risks and decisions needed, in a consistent format.
IT-related certifications
The general project management credentials, including PMP and its registry, are covered on the project manager phone screen page. Two more come up often for IT roles (as of October 2026, from the issuers' sites):
| Credential | What it is | What it does not show |
|---|---|---|
| ITIL 4 Foundation (PeopleCert) | An entry-level IT service management exam: 40 multiple-choice questions, 60 minutes, closed book, 65% to pass. | Experience running changes or projects. |
| CompTIA Project+ | An entry-level project management exam aimed at IT professionals; current version PK0-005, up to 90 questions in 90 minutes. | Leadership of large or complex projects. |
How IT project manager resumes overstate the work
- "Led the ERP implementation" as one of several workstream leads, or as the partner's coordinator.
- Go-lives counted per site on a single rollout. Ask how many separate cutover plans they wrote.
- Budget quoted for the whole program when they managed one project within it.
- Technical work claimed that engineers did. Fine for a project manager, but ask who did it.
Knockout checklist and scorecard
Pass or fail
- Has led the same type of IT project, at comparable size.
- Can support off-hours go-lives if required.
- Holds any credential or clearance the client requires.
- Work authorization answers fit the role.
Scored 0 to 2 each (10 possible)
- Environments and test exit criteria.
- Cutover runbook and go or no-go decision.
- Rollback triggers and hypercare.
- Vendor and SOW management.
- Production change control and security gates.
Write the go-live story into the submittal in the candidate's own words, with the size and their role, because it is the first thing an IT hiring manager will ask about.
Legal cautions
Ask about weekend and overnight availability the same way for everyone, not about family or religion. Do not ask about age ("how many years until retirement") or national origin; ask only the standard work authorization questions. This is general information as of October 2026, not legal advice.
Questions people ask
What is the best single question for an IT project manager?
Ask them to walk you through their last go-live: the cutover plan, the go or no-go decision, the rollback criteria and what happened in the first week. IT project managers who ran the cutover describe a sequence, owners and a decision point. Those who watched it describe the outcome.
Does an IT project manager need a PMP?
Only if the client requires it. PMP shows verified project experience and an exam, but not IT delivery skill. Some IT roles value ITIL 4 Foundation for service management vocabulary or an agile certification more. Ask what the client actually screens for and check any credential with the issuer.
What is the difference between an IT project manager and a scrum master?
A scrum master serves one or more Scrum teams and the process; an IT project manager owns scope, schedule, budget, vendors and the go-live across teams, often including non-agile work such as infrastructure and data migration. Some roles combine them, so ask the client what share of the job is each.
How do I check technical depth without being technical?
Ask about environments, testing exit criteria, cutover and rollback. You do not need to judge the technology; listen for specific steps, named owners and decisions they made. Vague answers about 'working closely with engineering' are the signal.