Why pre-screen IT portfolio managers before the executive interview
The point of portfolio management is to stop things. Any organisation can start projects; the constraint is delivery capacity, and the value of the function is in reallocating it away from work that is no longer worth doing. That requires telling a senior sponsor their initiative is being cancelled, which is uncomfortable and therefore frequently avoided. A manager who has never cancelled anything has been administering a list. A short screen asks for the cancellation directly.
What actually matters when screening IT Portfolio Manager candidates
- 01
Record of outcomes
Probe the portfolios they governed: annual spend, number of programmes, and outcomes such as retired legacy apps, benefits realised post go-live, or demand backlog cleared.
- 02
Strategic judgement
Test how they prioritise competing investments: scoring models, capacity versus demand analysis, stage-gate or investment committee criteria, and which projects they recommended killing.
- 03
Building and leading teams
Assess how they lead programme and project managers: PMO staffing, coaching on schedule quality, RAID discipline, and handling a delivery lead who kept missing gate reviews.
- 04
Influence across the business
Look for influence over CIO, finance, and business unit heads: budget reforecasts, roadmap negotiation, and how they used tools like ServiceNow SPM, Clarity, or Planview to make trade-offs visible.
Pre-screening questions to ask IT Portfolio Manager candidates
12 questions grouped by what they test. Ask the same set in every screen and score answers on a consistent scale, or send them as an async video screen and compare answers side by side.
Portfolio outcomes
3 questions01How do you evaluate the performance of an IT portfolio?
Listen forMeasures of value delivered rather than delivery statistics, with benefits reviewed after go-live rather than assumed from the business case.
Performance reported as projects delivered on time and budget, with no check on whether benefits materialised.
02Can you describe a time you managed a project that did not meet its objectives?
Listen forAn honest account with what was learned and whether the portfolio process changed as a result of it.
Failures attributed entirely to delivery teams, or no project in the portfolio that missed its objectives.
03How do you assess the potential return of a new project?
Listen forScepticism about sponsor-supplied benefits, with a method for testing assumptions and a case where they challenged a business case successfully.
Accepts the sponsor's benefits figures, or approvals driven by who is asking rather than by the case.
Prioritising on value
3 questions04How do you prioritise projects within an IT portfolio?
Listen forAn explicit framework applied consistently, with capacity treated as the real constraint rather than budget alone.
Priority determined by seniority of the requester, or a framework that is overridden whenever an executive intervenes.
05How do you handle non-performing projects or assets in a portfolio?
Listen forA project they actually stopped, with the evidence used and how the sponsor was told, plus where the capacity went afterwards.
Nothing ever cancelled, or underperforming projects allowed to continue quietly until they ran out of funding.
06How do you balance a portfolio to achieve strategic goals?
Listen forA deliberate mix across run, change and innovation, with a decision to underweight something and the reasoning behind it.
Balance described as covering all business units, or a portfolio dominated by whichever area lobbies hardest.
Leading without authority
3 questions07Can you explain your approach to team leadership in portfolio management?
Listen forGetting work from project managers who do not report to them, including how they handled one who ignored portfolio process.
Leadership described only over direct reports, or no experience of influencing delivery teams outside their line.
08What strategies do you use to manage several projects running at once?
Listen forAttention allocated by risk rather than evenly, with a clear view on which projects they leave alone deliberately.
Reviews everything at the same cadence, or attention driven by which project manager reports most frequently.
09Can you describe your approach to risk management across a portfolio?
Listen forRisks aggregated across projects to see concentration, such as several depending on the same team or vendor.
Risk managed project by project, with no view of where the portfolio is collectively exposed.
Telling executives no
3 questions10Can you describe a time you had to make a crucial decision about an IT project?
Listen forA decision that went against a senior stakeholder, with the evidence used and how the relationship survived it.
Decisions described with no opposition, or a recommendation withdrawn once an executive pushed back.
11How do you deal with stakeholder demands and expectations?
Listen forTrade-offs made visible so a sponsor sees what their request displaces, rather than absorbing demands into an overcommitted plan.
Accommodates every request, or expectations managed by not telling sponsors what was deprioritised.
12How comfortable are you making decisions that affect the whole organisation's technology estate?
Listen forA specific estate-wide decision with what they consulted on and where they decided alone, plus the consequence they had anticipated.
Comfort claimed with no example, or every significant decision escalated rather than owned.
How to score responses
Score every candidate on the same four criteria immediately after the screen. At this stage you are shortlisting for panel interviews, not making the final call.
Record of outcomes
35%5Names portfolio size in spend and programme count, and cites realised benefits or decommissioning results verified after delivery, not at approval.
Strategic judgement
25%5Describes a defensible scoring or capacity model and a specific project they stopped or deferred, with the reasoning and downstream effect.
Building and leading teams
25%5Gives concrete examples of raising PM capability, including how they intervened on a failing programme without taking over delivery themselves.
Influence across the business
15%5Shows they changed a funding or sequencing decision using portfolio data, and names the forum and stakeholders they had to convince.
The value of this function is in stopping things, which is uncomfortable and therefore often avoided. A one-way video screen asks what a candidate has actually cancelled.
Try it on HirevireScreening FAQ
Process basics
How long should a pre-screening round for a portfolio manager take?
Fifteen minutes across eight to ten questions, answered async. Enough to establish portfolio size and budget, hear one project they stopped, and check how they handled the sponsor before an executive interview.
What should the screen establish beyond methodology?
Decision rights. Ask what they could stop on their own authority and what needed a board. Managers who could only recommend have a different skill set from those who could reallocate, and the resume rarely says which.
Evaluating answers
What is the strongest signal when screening a portfolio manager?
A project they cancelled. Portfolio management exists to reallocate capacity, which means stopping work someone senior wanted. Managers who have done it can name the project, the evidence and the conversation. Those who have not have been maintaining a report.
How do I judge benefits claims?
Ask whether anyone checked after delivery. Business cases are written to secure funding and are rarely revisited. A portfolio manager who has run a benefits review, and can say which projects did not deliver what they promised, is doing the actual job.
























