Head of IT Interview Questions UK: 8 Real Questions and What Interviewers Want
Before your Head of IT interview, it helps to see the questions from the interviewer's side. We have picked eight from our set of 16 and added the reason each one gets asked.
Eight Head of IT interview questions, and what the interviewer is thinking
1. How would you go about developing an IT strategy for an organisation you have just joined?
Why they ask: Tests strategic thinking and the ability to link technology to business outcomes.
2. How do you decide which legacy systems to retire, replace or keep, and how do you make the business case for it?
Why they ask: Assesses pragmatic management of technical debt and investment decisions.
3. How do you decide between an in-house IT team and a managed service provider, and how would you structure a team of about fifteen people?
Why they ask: Looks at operating-model judgement, including resourcing and sourcing decisions.
4. What would you expect to see on an IT risk register, and how do you report risk to a board or audit committee?
Why they ask: Tests governance maturity and the ability to communicate risk at executive level.
5. Which KPIs would you report to show the value of IT to the business, beyond uptime and ticket numbers?
Why they ask: Checks whether you measure outcomes and business value rather than just activity.
6. The chief executive wants to roll out a generative AI assistant to the whole organisation within a month. How do you respond?
Why they ask: Tests ability to enable innovation while managing data protection and security risk.
7. Tell me about a major IT transformation or migration you led, such as a move to Microsoft 365, cloud or a new ERP, and how you kept the business on board.
Why they ask: Evaluates experience of leading large change and stakeholder engagement.
8. What does a typical week look like for a Head of IT, and how do you balance strategic work with day-to-day operations?
Why they ask: Checks realistic understanding of the role and time management at leadership level.
A sample answer to question 1
How would you go about developing an IT strategy for an organisation you have just joined?
I would spend my first ninety days listening before writing anything. I would meet the executive team and heads of department to understand the business plan, pressures and frustrations with IT, and meet my own team and key suppliers. In parallel I would audit what exists: applications, infrastructure, contracts, licences, security posture, support performance, technical debt and spend. From that I would build a clear picture of where IT is helping or holding back the business. The strategy itself would be short and written in business language, with a handful of themes such as secure foundations, better user experience, data and automation. Each would have measurable outcomes, a sequenced roadmap over three years, costed initiatives and named owners. I would test it with the board and department heads, agree the funding approach, and review it every six months because priorities and technology change.
Common mistake to avoid: Presenting a technology wish list; writing a strategy without consulting the business
Want the rest?
Full model answers, key points and common mistakes for all 16 questions are on the Head of IT interview questions page. The first five are free, no sign-up needed.

Comments