IT Project Manager Evaluation Framework
IT PM is the role most often hired wrong. Clients ask for a PM and they actually want either (a) a delivery manager who can unblock teams, or (b) a project coordinator who can manage status reports. The two are different jobs and need different rubrics. This guide is for the first kind — the senior IT PM who owns delivery on cross-functional, multi-vendor projects.
Key skills
Must-have
Delivered software projects end-to-end
2+ projects from kickoff to launch, owning schedule, scope, and stakeholder communication. Not "I attended standups."
Stakeholder management across function
Has worked with engineering, product, design, and business stakeholders simultaneously and kept them aligned.
Risk management instinct
Can spot a slipping milestone 2 weeks out, not 2 days out. Has a documented risk register or equivalent.
Comfort with technical concepts
Does not need to write code, but can ask informed questions about architecture, dependencies, and trade-offs without becoming the bottleneck.
Nice-to-have
PMP or equivalent certification
Useful for enterprise clients that require it. Not a quality signal on its own.
Agile coaching experience
Some clients want PMs who can also coach Agile practices. Worth a premium if true.
Vendor management
Has managed third-party vendors (offshore teams, integration partners) — common in enterprise IT.
Budget ownership
Has owned a P&L for a project. Useful for senior PM roles.
Interview questions (6)
Walk me through a project that slipped its deadline. What did you do?
What to listen for
Real timeline + early warning signs they noticed (or missed). Specific re-baselining or scope reduction. Not "the engineers were too slow."
How do you handle a senior stakeholder who keeps changing requirements?
What to listen for
Polite escalation + change-control process + impact analysis. Not "I push back hard" or "I just absorb it."
Describe how you run a status update with a non-technical executive.
What to listen for
Top-down summary, RAG status, asks for decisions, not technical detail. 5 minutes max.
What is your approach to estimation? How do you handle the "engineers always underestimate" problem?
What to listen for
Three-point estimates, historical velocity, padding for the unknown unknowns. Not "I just multiply by 2."
A developer tells you a feature will take 3 days. You think it should take 1. What do you do?
What to listen for
Asks why, listens, does NOT override the engineer. Senior PMs trust their teams.
How do you decide what NOT to do in a project?
What to listen for
Cost-of-delay framing, MVP framing, explicit out-of-scope list. Not "we do everything."
Evaluation rubric
Score each candidate against these weighted criteria. Total: 100%.
| Criterion | Weight | Signal |
|---|---|---|
| Delivery track record | 30% | Multiple projects shipped on time and on scope. Specific outcomes, not titles. |
| Stakeholder management | 25% | Has wrangled difficult execs, customers, vendors. Examples of escalation done well. |
| Risk + scope discipline | 20% | Has caught and mitigated real risks. Has said "no" to scope creep with a clean process. |
| Communication | 15% | Writes clear status updates. Adjusts message for audience. |
| Technical literacy | 10% | Asks informed questions. Does not need code, does need vocabulary. |
Red flags
CV is all titles and no outcomes ("Managed projects" with no specifics)
Cannot name a single project that slipped — has not run real projects
Avoids ownership ("the team decided") — not actually accountable
Has never said "no" to a stakeholder
Claims Agile expertise but cannot define a sprint goal
Apply this rubric automatically with CVPRO
Upload Project Manager CVs and let AI score every candidate against the same 42-point evidence rubric.
Try CVPRO Free