Technology Management
IT Manager interview questions
The questions this panel really asks — and what they’re testing, from the chair across the table.
Question 1
Tell me about a time when a critical system went down on your watch — something that affected the business materially. Take me through what happened, what you did in the first hour, and how you prevented it happening the same way again.
Why they’ll ask it
This tests whether you actually know how to operate under pressure, not just theoretically. Interviewers are listening for whether you stayed calm, communicated clearly to non-technical stakeholders, owned the problem rather than deflecting, and extracted a real lesson that changed your processes. Candidates often either sanitise the story into something trivial or blame external factors; strong answers show specific decisions you made and what you learned about your own team's readiness.
How would this land on your CV? Run the free analysis →Question 2
You've got someone on your team — technically strong, been here years — who actively pushes back against a migration or new tool the business has decided to adopt. They're not being insubordinate, just vocal about why it's a bad idea. How do you work with that?
Why they’ll ask it
This separates managers who lead from those who just enforce. The panel wants to know if you can distinguish between legitimate technical concerns and mere resistance to change, whether you'll listen before deciding, and how you'll handle someone who won't simply comply. Weak answers either dismiss the engineer's view entirely or capitulate to keep the peace. Strong answers show you'd understand their concern, test it against the business case, and find a way to either address it or get their buy-in on why the decision stands.
How would this land on your CV? Run the free analysis →Question 3
Your team currently runs most of your infrastructure and applications. A vendor approaches you with a managed service that would reduce your headcount by two or three people and cut operational overhead. Walk me through how you'd evaluate that decision and what factors matter most to you.
Why they’ll ask it
This tests whether you think beyond cost and headcount to strategic capability, risk, and your team's future. Interviewers want to see if you understand the difference between commodity work and work that builds competitive advantage, whether you consider team morale and career development, and if you can articulate a real business case rather than just chasing savings. Candidates often either default to 'cheaper is better' or resist outsourcing reflexively; the strong answer shows you'd weigh control, cost, quality, and what your team needs to grow.
How would this land on your CV? Run the free analysis →Question 4
Your CTO or CFO asks you why your IT budget needs to increase by 20 percent next year. They're not hostile, just sceptical. What's your pitch, and how do you frame it so they actually understand what you're asking for and why?
Why they’ll ask it
IT managers live at the boundary between technical reality and business priorities; this question tests whether you can translate one into the other's language. Interviewers are checking if you lead with business impact rather than technical jargon, whether you've done the homework to justify the ask, and if you can handle pushback without becoming defensive. Weak answers either descend into technical detail or make vague claims about 'security' and 'stability'. Strong answers show you've quantified the risk or opportunity, tied it to something the business cares about, and anticipated the objections.
How would this land on your CV? Run the free analysis →How interviewers size you up for this role
You're walking in with a resume that shows you've managed teams and systems; the interview needs to confirm you can actually lead under pressure, make sound trade-off decisions, and communicate across the technical and business divide. Panels assume you know how to run a help desk or manage a data centre — what they're testing is whether you think strategically about capability, whether your team trusts you in a crisis, and whether you can advocate for IT without losing credibility with the rest of the business. Strong candidates on paper often stumble because they either lean too hard on technical depth (showing they haven't fully stepped into management) or they're vague about how they've actually solved problems. You'll be rejected if you can't point to concrete examples of decisions you've made, people you've developed, or processes you've changed — not because you're inexperienced, but because you haven't yet shown you can think like a manager.
IT Manager interviews — common questions
How technical should I be in an IT Manager interview?
You need to demonstrate enough technical fluency to earn credibility with your team and understand what they're telling you, but the panel isn't testing whether you can code or architect systems yourself. They're testing whether you ask the right questions, understand the constraints, and can translate technical trade-offs into business language. If you can't explain why you chose one database over another or what your team's on-call rotation looks like, that's a red flag.
What does the final round for an IT Manager role usually look like?
You'll typically face the CTO, CFO, or another C-level executive who wants to understand how you think about resource allocation, risk, and business alignment. They're less interested in your team's day-to-day and more interested in whether you can sit at the table and make decisions that balance technical reality with commercial pressure. Prepare to discuss a significant investment decision or a moment when you had to say no to something the business wanted.
Should I talk about certifications and formal qualifications?
Only if they're recent and directly relevant to the role you're interviewing for — ITIL, cloud certifications, or security credentials matter more than older general IT certs. But don't lead with them. Interviewers care far more about what you've actually run and how you've improved it than about what certificate is on your wall. If you don't have formal qualifications, that's rarely a blocker if you can point to real examples of managing complexity.
Related guides
- Chief Technology Officer (CTO) interview questions
- Engineering Manager interview questions
- Head of Engineering interview questions