IT Manager interview questions, and how to answer them
An IT manager interview isn't a quiz on subnetting. The panel wants to know if you can keep the lights on, spend money sensibly, and tell a vice president no without starting a feud. Here's what they'll ask and what a good answer sounds like from someone who's actually carried the pager.
What happens in each round
- 1
Recruiter screen
What happens
Whether your scope matches theirs. They'll ask how big your team was, what you owned (help desk, network, cloud, security) and whether you've managed a budget. Be specific about what was yours and what belonged to someone else.
- 2
Hiring manager
What happens
Usually the CIO, IT director or a COO who inherited IT. They're testing judgment: how you run the service desk, how you handle a bad vendor, and whether you'll bring them problems early or late.
- 3
Technical panel
What happens
Senior engineers or sysadmins who might report to you. They want to see you still understand the stack well enough to spot a bad plan, even if you haven't touched a firewall rule in a while.
- 4
Business stakeholder or case
What happens
A finance, HR or operations lead, sometimes with a scenario like a ransomware scare or a messy office move. They're checking whether you talk to non-technical people like adults and tie IT work to what the business needs.
Questions you're likely to get
1.Walk me through the last major outage you owned, from the first alert to the post-incident review.
Why they ask
Every IT manager has had a bad day. They want to see how you run one: who you call, how you communicate, and whether you learn from it or just survive it.
How to answer
- Name the real incident: what broke, who it hit, and how you found out
- Explain how you split the work, with one person fixing and one person handling updates to leadership and users
- Say how often you sent status updates and through which channel, even when there was nothing new
- Describe the blameless review afterward and the one or two changes that actually shipped because of it
2.How do you run the service desk, and how do you know it's working?
Why they ask
The help desk is how most of the company judges IT. If tickets rot, nobody cares how good your network design is.
How to answer
- Name the tool you've run, such as ServiceNow, Jira Service Management or Freshservice, and how you set up categories and priorities
- Talk about response and resolution targets and how you reviewed them weekly with the team
- Mention a knowledge base and self-service for password resets and common requests
- Point to user feedback, like the survey after a ticket closes, and one fix it led to
3.Tell me about a time you had to say no to a senior leader's technology request.
Why they ask
Executives will ask for a new app, a personal exception to MFA, or a tool someone saw at a conference. They need to know you can push back without burning the relationship.
How to answer
- Set up the request and why it was a problem (security, cost, support load, or duplicate tools)
- Show that you asked what they were really trying to solve before refusing
- Explain the alternative you offered and how you put the tradeoff in their terms
- Close with how it landed and whether the relationship held up
4.How do you build and defend the IT budget?
Why they ask
A lot of IT managers are handed a budget for the first time in this role. Finance will be sitting in on some of these conversations, so they want to hear you think like an owner.
How to answer
- Split it the way you actually track it: licenses, hardware refresh, contracts, people and projects
- Describe how you audit software licenses and cut seats nobody uses
- Talk about a refresh cycle for laptops and network gear so spending isn't a surprise
- Give an example of justifying a spend with risk or time saved, not with 'it's best practice'
5.We think we're behind on security. What would you look at in your first month?
Why they ask
Plenty of mid-sized companies hire an IT manager partly because a cyber insurance form or an audit scared them. This is the most common situational question in the room.
How to answer
- Start with the basics you'd confirm: MFA everywhere, patching status, backups that have actually been restored, and admin accounts
- Mention endpoint protection and device management, such as Intune or Jamf, and who has local admin
- Say you'd check offboarding, because old accounts that still work are a common hole
- Explain that you'd write up what you found in plain language, ranked by risk, before asking for money
6.How do you manage vendors and managed service providers?
Why they ask
Much of IT work is outsourced to an MSP, a cloud provider, or a carrier. A weak manager lets vendors run them.
How to answer
- Talk about reading the contract and the SLA before there's a problem
- Describe a regular review with the account rep where you bring the ticket data, not feelings
- Give a real example of escalating or replacing a vendor that wasn't delivering
- Mention how you avoid getting locked in, like owning your own admin credentials and documentation
7.Describe a project you led that touched the whole company, like a migration or an office move.
Why they ask
Email migrations, identity changes, a new ERP rollout, or opening a site. These projects break in front of everyone, so they want to hear how you plan and how you handle the mess.
How to answer
- Set the scope and the deadline, and who was on the project
- Explain the rollout plan: a pilot group, then waves, with a rollback plan
- Describe how you told users what was changing and when, and how you staffed the desk for launch day
- Be honest about one thing that went wrong and how you handled it
8.How do you handle a team member who's technically strong but hard to work with?
Why they ask
IT teams often have a brilliant sysadmin who's rude to users or hoards knowledge. They want to see you manage people, not just systems.
How to answer
- Describe the real behavior and the effect on users or teammates
- Explain the direct, private conversation and the specific expectation you set
- Talk about fixing the knowledge-hoarding risk with documentation and cross-training
- Say what happened next, including if it didn't improve and you had to escalate
9.How do you decide what gets fixed first when everything's on fire?
Why they ask
You'll have a broken printer on the CEO's floor, a failing backup job, and a project deadline on the same afternoon. Prioritization is most of the job.
How to answer
- Explain a clear priority model based on business impact and how many people are affected
- Say who you tell and how, so nobody is left guessing
- Mention protecting your project people from getting dragged onto the desk every time
- Give a quick real example of a call you made and why
10.How do you keep your technical skills current now that you're managing?
Why they ask
The panel doesn't want someone who stopped learning when they got a title. They also don't want a manager who's still the best engineer and won't delegate.
How to answer
- Name the areas you keep up with, like cloud identity, networking, or endpoint management
- Mention a lab, a certificate you're working on, or reading change logs from your key vendors
- Explain that you stay close enough to review designs and ask good questions
- Say plainly that you let your engineers own the hands-on work
11.Tell me about a time a backup or disaster recovery plan was actually tested.
Why they ask
Lots of teams have backups. Far fewer have restored from them. This question separates people who've checked from people who've assumed.
How to answer
- Name what was backed up and with what tool, such as Veeam or a cloud provider's native backup
- Describe the restore test itself, including what failed or took longer than expected
- Explain how you wrote down recovery steps so someone other than you could run them
- Mention agreeing recovery targets with the business, not just picking them yourself
12.How would you explain a technical risk to our CFO in two minutes?
Why they ask
You'll spend real time in rooms with finance and legal. They want to hear you drop the jargon on the spot.
How to answer
- Pick a real risk, like an unsupported server or no MFA on email
- Say what could happen in business terms: downtime, lost data, an insurance claim denied
- Give the fix, a rough effort and the choice they need to make
- Keep it short and actually do it in the interview
Mistakes that sink good candidates
Talking only about technology and never about users, budget or the business
Blaming your old boss, your old team or a vendor without owning your part
Claiming projects as yours when a vendor or another team clearly ran them
Promising a fix for their security or help desk problems before you've asked a single question about them
Need more IT Manager interviews to prep for?
HeroApply applies to IT Manager jobs that match you, every day. 970 jobs are open today.