How IT manager interviews work
IT manager interviews test both technical leadership and operational management. Expect questions covering infrastructure management, vendor and budget oversight, team development, project delivery, and IT strategy. The technical depth varies by company size and the specific scope of the role. For hands-on IT manager roles at mid-size companies, expect detailed infrastructure questions. For IT director or VP-level roles at larger companies, expect more strategic and organisational questions.
Many IT manager interviews include a scenario exercise: here is a current IT challenge the business is facing, how would you approach it? These scenarios test how you structure a problem, communicate with non-technical stakeholders, and balance competing priorities on a limited budget.
Infrastructure and technical questions
"How would you approach migrating a company from on-premises infrastructure to cloud?" Start with an inventory and assessment: what applications exist, what are their dependencies, which are candidates for lift-and-shift versus rearchitecting versus retirement? Define the migration sequence based on risk and dependency. Plan for identity management, network connectivity, data migration, and rollback procedures. Show that you treat migration as a project with governance rather than a technical exercise.
"How do you ensure business continuity and disaster recovery for critical systems?" Cover: RTO (Recovery Time Objective) and RPO (Recovery Point Objective) for each critical system, backup architecture, failover testing cadence, and documentation. The most important part is testing: DR plans that have never been tested do not work when needed. Show that you run regular tests and update plans based on what you learn.
Team management questions
"How do you develop technical staff who have strong skills but struggle with communication?" IT teams frequently include highly skilled people who find stakeholder communication difficult. Show that you provide specific, constructive feedback on communication (not just "be more concise"), create low-stakes practice opportunities (presenting at team meetings before presenting to the board), and pair them with colleagues who are stronger in this area for joint stakeholder work.
"Tell me about a time you had to manage underperformance in a technical team member." Show that you addressed it early rather than waiting, had clear and honest conversations about the gap between expected and actual performance, set measurable improvement targets, provided the support needed (training, mentoring, clearer expectations), and made a fair decision based on the outcome. Avoiding the conversation is the most common failure here.
Vendor and budget management questions
"How do you evaluate and select a new technology vendor?" Define requirements clearly before engaging vendors. Run a structured evaluation with scored criteria covering technical fit, security and compliance, total cost of ownership (not just licence cost), vendor stability, and support quality. Involve technical and business stakeholders in the assessment. Check references with existing customers at similar scale. Show that you separate the procurement decision from the vendor's sales relationship.
"How do you manage IT spend in a budget-constrained environment?" Prioritise based on risk and business impact: security and resilience spend should be protected. Evaluate every contract at renewal and negotiate based on actual usage data rather than historical spend. Consolidate vendors where possible. Identify shadow IT spend and bring it under management. Show that you treat the IT budget as a business investment rather than a cost to be minimised.
IT security and compliance questions
"What is your approach to managing IT security risk across an organisation that has limited IT resources?" Prioritise controls based on risk: multi-factor authentication, patching cadence, privileged access management, and endpoint detection are the highest-impact controls for most organisations. Use frameworks (ISO 27001, CIS Controls) to structure your approach rather than building from scratch. Train users regularly because phishing and social engineering account for the majority of incidents.
"How would you respond to a ransomware incident?" Isolate affected systems immediately, activate the incident response plan, assess the scope of the breach, engage your cyber insurance provider and legal team, and determine whether you have clean backups that allow recovery without paying. Communicate transparently with leadership and (if required) regulators. Show that you have thought about this scenario before it happens, not only when it does.
Behavioral questions
"Tell me about a significant IT project you delivered and what made it successful." Focus on a project that had real business impact and was not straightforward to deliver. Show how you managed stakeholder expectations, handled risks and issues as they emerged, kept the team aligned, and delivered against the original business case. Quantify the outcome where possible.
"How do you keep non-technical stakeholders engaged and informed on IT initiatives?" Show that you translate technical decisions into business language: not "we are upgrading the database to PostgreSQL 16" but "we are reducing the risk of a payment system outage by updating a critical component that no longer receives security patches." Use dashboards and executive summaries tuned to the audience rather than technical status reports.