Free IT manager interview questions for small businesses without HR: 6 sets on leadership, security, budget, and vendors, plus a scorecard. Download DOCX.
40+ interviewer questions across leadership, technical judgment, security, budget, and behavioral evidence, each with why it is worth asking and what a strong answer sounds like, plus a 1-to-5 scorecard. Download as DOCX.
Hiring an IT manager is the point where a small business stops treating technology as somebody's side job. The person you pick will hold administrator rights over email, files, and finance systems, decide what gets fixed first, and own whatever security posture you end up with. That is a lot of trust to hand over after two conversations, especially if you are not technical yourself.
At FirstHR, we build for owners and managers who make this hire without an HR department behind them. This page gives you more than 40 interviewer questions across five competencies, each with why it is worth asking and what a strong answer sounds like, plus a 1-to-5 scorecard. If you have not written the posting yet, start with the IT manager job description and come back here.
TL;DR
Interview an IT manager on five things: leadership and prioritization, technical judgment, security and risk, budget and vendor control, and behavioral evidence. The most revealing questions are when did you last restore from a backup, how do you decide what IT works on this week, and explain a recent technical decision in plain language. Score every candidate on the same 1-to-5 rubric. Download six question sets and the scorecard as DOCX.
What to Assess in an IT Manager
Assess an IT manager on ownership and judgment rather than hands-on speed. The role exists to decide what matters, control spend, keep the business running, and translate technology into business terms. A brilliant technician who cannot prioritize or explain a decision is the wrong hire at this level, and it is the most common mistake small companies make.
Scope drives everything else. If this is your first dedicated technology hire, the person needs to be genuinely hands-on and comfortable building where there is no structure, which is closer to the system administrator profile with ownership added. If you already have technicians or an outside provider, weight leadership and vendor management instead, and compare the level against an IT director before you commit.
Write down what the role must accomplish in the first 90 days before you interview anyone. That single paragraph tells you which of the question sets below to lean on, and it gives you something concrete to score candidates against instead of a general impression of competence.
The Six Question Categories
The questions are grouped into five competencies plus a scorecard. Each targets a different part of the job, and a strong candidate should hold up across all of them rather than only on the leadership questions most people rehearse. Ask at least two from every category.
Leadership and Priorities
Can they own it?
Prioritization, support intake, managing an outside provider, and explaining technology to a non-technical owner. The core of a manager hire.
Technical Judgment
Do they know what breaks?
Backups actually restored, patching, cloud tradeoffs, and documentation. You are grading judgment and honesty, not configuration trivia.
Security and Risk
They are your security team
Admin accounts, same-day offboarding, incident response, and awareness training. At your size the IT manager is the security function.
Budget and Vendors
Do they control spend?
Owning a budget, finding license waste, building a business case, and tracking renewals before they auto-renew. This one pays for itself.
Behavioral Scenarios
How do they really operate?
STAR questions on the worst outage, an over-budget project, pushing back on a senior person, and a security near miss.
Scorecard and Red Flags
Score, do not guess
A 1-to-5 rubric across six areas, a red-flag list, and an access-and-continuity checklist to complete before day one. The asset generic lists skip.
Do Not Skip Budget and Security
Candidates prepare hardest for leadership and behavioral questions. The categories that actually separate a manager from a senior technician are budget and vendors, where you learn whether they can control spend and read a contract, and security, where at your size they are the whole security function. If the role leans heavily toward network infrastructure, borrow a few questions from the network administrator set as well. Browse the rest of the hiring templates for the posting and evaluation forms.
40+ Questions and a Scorecard to Download
Download all six as a single Word document, or copy individual sets. Every set follows the same structure: how to use it, the questions with a note on why each is worth asking and what a good answer sounds like, what to listen for, and space for notes. The final file is the scorecard.
Download All 6 IT Manager Question Sets
Leadership, technical judgment, security, budget and vendors, behavioral scenarios, and a 1-to-5 scorecard with red flags. All in one DOCX.
Set 1: Leadership, Team, and Priorities
Prioritization, support intake, managing an outside provider, and explaining technology to a non-technical owner. This is the set that tells you whether you are hiring a manager or a technician with a manager title.
Leadership, Team, and Priorities Questions
IT MANAGER INTERVIEW: LEADERSHIP, TEAM, AND PRIORITIES
Candidate: __
Company: __
Interviewer: __
Date: _
HOW TO USE THIS SET
An IT manager is hired to own outcomes, not tickets. This set tests whether the
candidate can set priorities, run a small team or an outside provider, and speak
to a non-technical owner without hiding behind jargon. Ask 5 to 7 of these, then
score on the rubric in Set 6.
QUESTIONS
1. Walk me through the first 90 days if you took this job.
Why ask: it separates candidates who assess before acting from those who
arrive with a shopping list.
Good answer: inventory the systems, meet the people who use them, find the
top risks, then propose a short plan. Not "we replace everything."
2. How do you decide what IT works on this week when everything is urgent?
Why ask: prioritization is the single most-used skill in a small IT shop.
Good answer: a stated method (business impact, number of people blocked,
risk, deadline) plus a visible queue. Names a real tradeoff they made.
3. How do you run support: intake, triage, and response expectations?
Why ask: without a system, IT becomes whoever shouts loudest.
Good answer: one intake channel, a ticket record, a rough response target by
severity, and a way to spot repeat issues instead of re-fixing them.
4. How do you manage an outside provider or contractor doing part of the work?
Why ask: most small companies run a mix of in-house and outsourced IT.
Good answer: clear scope, an agreed response standard, regular reviews, and
the candidate keeping ownership rather than handing over the whole function.
5. Explain a recent technical decision to me as if I have no IT background.
Why ask: the manager is the translator between technology and the business.
Good answer: plain language, the business consequence first, the technology
second, no jargon shield. Ask a follow-up and see if the answer stays clear.
6. How do you develop the people on your team, or yourself if you are solo?
Why ask: the technology changes, so learning habits predict the next 3 years.
Good answer: specific examples, a certification or lab habit, and time
protected for it. For a solo hire, a real plan to stay current alone.
7. Tell me about a time you told the business no, or not yet.
Why ask: an IT manager who says yes to everything creates a broken estate.
Good answer: framed as a tradeoff with options and a cost, not a refusal.
WHAT TO LISTEN FOR
•A stated method for prioritizing, not "whatever is most urgent"
•Plain language when explaining technology to a non-technical listener
•Ownership of the outcome even when the work is outsourced
•Concrete examples with a result, not a description of the ideal
NOTES
__
__
Set 2: Technical Judgment and Infrastructure
Backups actually restored, patching, cloud tradeoffs, and documentation. You are grading judgment and honesty here, not configuration trivia, so each question comes with a note on what a good answer sounds like.
Technical Judgment and Infrastructure Questions
IT MANAGER INTERVIEW: TECHNICAL JUDGMENT AND INFRASTRUCTURE
Candidate: __
Company: __
Interviewer: __
HOW TO USE THIS SET
You are not testing whether the candidate can out-configure your engineer. You
are testing judgment: do they know what matters, what breaks, and what they do
not know. Every question below has a note on what a good answer sounds like, so
a non-technical owner can grade it.
QUESTIONS
1. Describe the environment you own today: users, sites, servers, cloud, devices.
Why ask: it establishes scale and whether their experience matches your size.
Good answer: specific numbers and systems. Vagueness here usually means the
candidate supervised the work rather than understanding it.
2. How do you handle backups, and when did you last restore from one?
Why ask: untested backups are the most common serious gap in a small estate.
Good answer: a schedule, a copy that an attacker with admin rights cannot
delete, and an actual restore test with a date. "We have backups" is a fail.
3. What would you do first if email stopped working for the whole company?
Why ask: incident behavior under pressure is the job.
Good answer: confirm scope, check provider status, communicate to staff early
with an update time, then diagnose. Communication belongs in the first minute.
4. How do you decide between cloud and on-premises for a given system?
Why ask: the answer reveals whether they think in tradeoffs or in slogans.
Good answer: cost over time, recovery needs, compliance, staff to run it, and
what the business actually requires. Not "cloud is always better."
5. How do you keep devices and software patched across the company?
Why ask: patching is unglamorous, constant, and where breaches start.
Good answer: a managed process with device management tooling, a patch
window, exceptions tracked, and a way to prove coverage rather than assume it.
6. How do you document systems, passwords, and how things are wired together?
Why ask: a small business is one departure away from losing all context.
Good answer: a maintained runbook and a shared password vault the owner can
reach. A candidate who keeps it all in their head is a continuity risk.
7. Tell me about something you did not know how to do. What did you do?
Why ask: honesty about limits is more useful than claimed omniscience.
Good answer: names the gap plainly, describes how they closed it or who they
brought in. Candidates who claim to know everything usually know less.
WHAT TO LISTEN FOR
•Backups that have actually been restored, with a date
•Tradeoff thinking rather than vendor slogans
•Documentation and password practices the business can survive
•Comfort saying "I did not know that, here is what I did"
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Admin accounts, same-day offboarding, incident response, and awareness training. At a small company the IT manager is the security function, so ask every one of these of every candidate.
Security, Risk, and Compliance Questions
IT MANAGER INTERVIEW: SECURITY, RISK, AND COMPLIANCE
Candidate: __
Company: __
Interviewer: __
HOW TO USE THIS SET
At a small company the IT manager is usually also the security function. Ask
these of every candidate. A manager who treats security as somebody else's job,
or who answers only with product names, is a poor fit for a business with no
security team behind them.
QUESTIONS
1. If you joined us tomorrow, what are the first three security gaps you expect?
Why ask: it shows whether they carry a working model of small-business risk.
Good answer: usually multi-factor authentication coverage, admin accounts,
backups, and phishing. Concrete and prioritized, not a compliance recital.
2. How do you handle privileged and admin accounts?
Why ask: shared admin logins are common and dangerous at small companies.
Good answer: named individual accounts, least privilege, separate admin
credentials, multi-factor everywhere, and periodic review of who has what.
3. Walk me through your offboarding process on the day someone leaves.
Why ask: unrevoked access is the quiet risk nobody notices until it matters.
Good answer: a checklist tied to HR notification, same-day revocation across
every system, device return, and a record that it was done.
4. An executive asks you to bypass a control for convenience. What do you do?
Why ask: it tests spine and diplomacy at the same time.
Good answer: explains the risk in business terms, offers a practical
alternative, escalates if needed, and documents the decision either way.
5. How would you run a phishing or security awareness program here?
Why ask: people are the attack surface at a company without a security team.
Good answer: short, regular training, simulated phishing used to coach rather
than punish, and a culture where reporting a mistake is safe.
6. What is your incident response plan when you suspect a breach?
Why ask: the first hour decides how bad it gets.
Good answer: contain, preserve evidence, notify leadership, engage outside
help and insurance, and know that breach notification duties may apply.
7. Which compliance or contract security requirements have you worked under?
Why ask: customer contracts and regulated data often drive the real workload.
Good answer: names the actual frameworks or client security questionnaires
they have handled and what changed operationally as a result.
WHAT TO LISTEN FOR
•Risk ranked by likelihood and impact, not a list of purchases
•Offboarding treated as a same-day, checklist-driven event
•Willingness to push back on convenience requests, politely
•Awareness that a breach has legal and notification consequences
NOTES
__
Set 4: Budget, Vendors, and Buy-or-Build
Owning a budget, finding license waste, building a business case, and tracking renewals before they auto-renew. A manager who controls spend well often pays for their own salary.
Budget, Vendors, and Buy-or-Build Questions
IT MANAGER INTERVIEW: BUDGET, VENDORS, AND BUY-OR-BUILD
Candidate: __
Company: __
Interviewer: __
HOW TO USE THIS SET
For a small business, an IT manager who controls spend well pays for their own
salary. This set tests commercial judgment: license waste, vendor contracts,
renewal discipline, and the ability to make a case for money in business terms
rather than technical ones.
QUESTIONS
1. Walk me through an IT budget you have owned. What was in it?
Why ask: it shows whether they have handled money or only requested it.
Good answer: separates recurring subscriptions, hardware refresh, projects,
and contingency. Knows their numbers without reaching for a guess.
2. How would you find waste in our current technology spend?
Why ask: unused licenses and forgotten subscriptions are near universal.
Good answer: license audit against the employee list, usage reports,
overlapping tools consolidated, renewal calendar. Usually finds real savings.
3. How do you build a business case for a technology purchase?
Why ask: the manager must sell spend to a skeptical owner.
Good answer: the business problem first, options with costs, risk of doing
nothing, and a payback or risk-reduction argument. Not a feature list.
4. How do you evaluate and negotiate with vendors?
Why ask: small companies rarely have procurement support.
Good answer: real references, a trial or proof of concept, attention to
contract terms and exit, and renewal dates tracked before the auto-renewal.
5. When do you buy a service versus build or self-host it?
Why ask: over-building is a common way small IT teams create fragility.
Good answer: weighs staff time, continuity if the person leaves, total cost,
and whether the capability is core to the business.
6. Where would you spend the first ten thousand dollars we gave you?
Why ask: it forces a priority ranking with real constraints.
Good answer: ties spend to the risks they identified earlier and explains why
that order. Backups, identity, and endpoint protection often come first.
7. How do you plan a hardware refresh cycle without a big-bang expense?
Why ask: device replacement is the budget item small companies defer forever.
Good answer: a rolling replacement schedule, standardized models, and warranty
coverage, so the cost is predictable rather than a crisis.
WHAT TO LISTEN FOR
•Numbers offered without prompting
•Business framing for spend, not feature enthusiasm
•Renewal and contract discipline
•Awareness that self-hosting has a staffing cost
NOTES
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
STAR-style questions on the worst outage they have managed, an over-budget project, pushing back on a senior person, and a security near miss. Past behavior is the better predictor.
Behavioral and Incident Scenario Questions
IT MANAGER INTERVIEW: BEHAVIORAL AND INCIDENT SCENARIOS
Candidate: __
Company: __
Interviewer: __
HOW TO USE THIS SET
Score these with the STAR pattern: Situation, Task, Action, Result. You want the
specific action the candidate personally took and a measurable outcome. Push for
detail whenever the answer stays at the level of what a team generally does.
QUESTIONS
1. Tell me about the worst outage you have managed. What happened?
Why ask: outages reveal composure, method, and honesty at once.
Good answer: a real timeline, what they did first, how they communicated, and
what changed afterward so it could not repeat the same way.
2. Describe a project that went over budget or over schedule.
Why ask: everyone has one; the tell is whether they own it.
Good answer: names their own contribution to the miss and the correction.
Blaming vendors or users entirely is a warning sign.
3. Tell me about a time you had to push back on a senior person.
Why ask: an IT manager who cannot disagree upward becomes a rubber stamp.
Good answer: respectful, evidence-based, offered an alternative, and accepted
the final decision without sabotage.
4. Describe a time a user or department was unhappy with IT. What did you do?
Why ask: internal customer service is half of this role.
Good answer: listened, found the underlying issue, fixed the process, and
followed up. Not "the user did not understand."
5. Tell me about a system or process you built that is still in use.
Why ask: durable work is a better signal than a list of projects started.
Good answer: something specific, adopted by others, with a stated benefit.
6. Describe a security incident or near miss you were involved in.
Why ask: candor here is rare and valuable.
Good answer: honest about what happened, what the response was, and what
changed. A candidate who has never seen one at all may be inexperienced.
7. Tell me about a time you changed your mind about a technology decision.
Why ask: it tests whether evidence can move them.
Good answer: names the evidence, the reversal, and the cost of switching.
WHAT TO LISTEN FOR
•"I" rather than "we" when describing the action
•A measurable result, not a description of intent
•Ownership of the miss before the explanation
•Follow-through: what changed afterward
NOTES
__
Set 6: Scorecard and Red Flags
A 1-to-5 rubric across six areas, a red-flag checklist, and an access-and-continuity checklist to complete before day one. This is the asset generic question lists leave out.
IT Manager Scorecard and Red Flags
IT MANAGER INTERVIEW SCORECARD AND RED-FLAG CHECKLIST
Candidate: __
Company: __
Interviewer: __
Date: _
HOW TO SCORE
Score each area from 1 to 5 immediately after the interview, while it is fresh.
Anchor every score to something the candidate actually said. If more than one
person interviews, each scores independently before the group talks, so the
loudest voice does not set the tone. Use the same rubric for every candidate.
Rating scale:
5 = Strong, specific evidence 4 = Solid evidence 3 = Some evidence
2 = Weak or mixed evidence 1 = No evidence or red flags
SCORING AREAS
Leadership and prioritization: sets priorities, runs support, owns outcomes
You do not need to grade the technology to run a good interview; you need to tell a specific answer from a vague one. The pattern holds across every question: strong answers carry a stated method, a real example, and a date or a number, and they get clearer when you ask a follow-up. Weak answers get foggier.
How do you handle backups, and when did you last restore from one?
Strong answer: Names a schedule, describes a copy that an attacker holding admin rights cannot delete, and gives a date for the last real restore test with what it revealed. A strong candidate treats the restore, not the backup job, as the thing that counts.
Weak answer: A weak answer stops at we have backups running, cannot say when a restore was last attempted, or assumes the provider handles it without ever checking.
How do you decide what IT works on this week when everything is urgent?
Strong answer: Gives a stated method: business impact, how many people are blocked, risk exposure, and a hard deadline, plus a visible queue anyone can see. A strong candidate then names a real tradeoff they made and what they told the person who waited.
Weak answer: A weak answer is whatever is most urgent, or whoever asks loudest, with no queue, no criteria, and no example of telling someone their request would wait.
Explain a recent technical decision to me as if I have no IT background.
Strong answer: Leads with the business consequence, uses plain language, and stays clear when you ask a follow-up question. This is the single best predictor of whether you will actually be able to work with this person day to day.
Weak answer: A weak answer hides behind acronyms, gets less clear when questioned, or treats the request as beneath them. Jargon under pressure usually signals shallow understanding.
Three follow-ups do most of the work. Ask what was the result, ask when did that happen, and ask what would you do differently. A candidate who has actually run the thing they are describing answers all three without hesitating. One who has watched someone else run it starts speaking in generalities about what a team should do.
Why the Security Questions Matter Most
At a company without a security team, the IT manager is the security function, so those questions carry more weight than any other set. The two that reveal the most are what would you fix first here, and walk me through offboarding on the day someone leaves. Both are specific enough that bluffing shows immediately.
Small Businesses Are a Primary Target
Federal guidance is direct about the exposure: the NIST Small Business Cybersecurity Corner exists because smaller organizations hold valuable data while typically lacking dedicated security staff, and CISA Cyber Essentials frames the basics as leadership decisions rather than technical projects: back up data, use multi-factor authentication, patch known vulnerabilities, and control who has administrator rights. Ask your candidate about exactly those four.
Notice what those four have in common: none of them is a purchase. A candidate whose security answer is a shopping list of products, with no mention of admin account hygiene, offboarding, or restore testing, has told you they treat security as procurement rather than practice.
Named individual accounts, least privilege, separate admin credentials
Offboarding on the day someone leaves
Same-day revocation across every system, tied to HR notification
An executive asks you to bypass a control
Risk explained in business terms, an alternative offered, decision documented
What is your incident response plan?
Contain, preserve evidence, notify leadership, engage outside help
What to Probe For (and Red Flags)
The prepared questions open the door; the follow-ups are where you learn what you actually need. Push for the specific number, the actual date, the real example, and watch for the patterns that separate a manager who owns outcomes from a candidate who interviews well.
Management signals
A stated method for setting priorities
One intake channel and a real ticket record
Keeps ownership when work is outsourced
Operational rigor
A restore test with an actual date
Patching that can be proven, not assumed
Runbook and password vault the owner can reach
Communication
Explains decisions without jargon
Tells staff early during an outage
Handles an unhappy department without blame
Red flags
Answers only with product names
Wants to replace everything before assessing
Treats security as someone else's job
None of the red flags is disqualifying on its own. Two or three together, though, usually predict the problems you will be living with in month six, which is why writing them down during the interview matters more than trusting your recall afterward.
Welcomes owner administrator access
A professional candidate expects the business to hold its own keys and will help you set that up. Discomfort here is worth exploring.
Documents by habit
Ask what documentation they left behind at their last job. Strong candidates can describe a runbook someone else could follow.
Uses a shared password vault
Credentials in a personal browser profile or a spreadsheet is the single most common continuity failure at small companies.
Knows vendor contracts and dates
A candidate who tracked renewals and contract terms in their last role will do the same for you, and it saves real money.
How to Run the Interview
Run the process in two or three rounds over two to three weeks, using the same core questions and the same rubric for everyone. Consistency is what makes candidates comparable, and it is the part a busy owner skips first. The sequence below works for a solo interviewer or a small panel.
Step
What to do
1. Define scope
Write what the role must accomplish in the first 90 days
2. Screen
30 to 45 minutes on scope match and plain-language communication
3. Standardize
Pick 2 to 3 questions per competency and ask everyone the same set
4. Probe security
Backups, admin accounts, and offboarding, in every interview
5. Score
Rate each area 1 to 5 with written evidence, independently
6. Reference and offer
Check references for integrity and handover, then make the offer
Score immediately after each round while the answers are fresh, and if more than one person interviews, have each complete the scorecard before the group talks. This matters more here than in most hiring, because the most technical person in the room will otherwise set the tone for everybody else. A structured interview is what makes the comparison hold up.
Fair, Legal, and Structured Interviewing
Fair, legal, and structured are the same thing in practice. Asking the same job-related questions of every candidate keeps you compliant, reduces bias, and produces better hires at once. Technical interviews drift more than most, which makes the discipline worth more here than elsewhere.
Ask about the job, not the person
Federal anti-discrimination law, enforced by the EEOC, prohibits basing a hiring decision on protected characteristics, and questions that probe them create risk even when they are asked as small talk. Avoid age, race, religion, national origin, sex, pregnancy or family plans, disability, and genetic information. In technology hiring there is one trap worth naming: do not ask how many years of experience the candidate has as a proxy for age, or when they graduated. Ask what they have built and run instead. Every question in these sets is tied to the ability to run technology for a business. This is general information, not legal advice.
Ask every candidate the same core questions
A structured interview, where each candidate answers the same questions and is scored against the same rubric, predicts on-the-job performance better than a free-flowing technical chat, and it reduces the chance that a decision rests on rapport. Technical interviews drift more than most, because a conversation between two engineers naturally follows whatever they both find interesting, which makes candidates impossible to compare. Write the core questions in advance, ask them of everyone, and score them. The sets and scorecard here are built for that. This is general information, not legal advice.
Score independently, then discuss
When more than one person interviews an IT manager candidate, have each interviewer complete the scorecard alone before the group compares notes. This matters more in technical hiring than almost anywhere else, because the most technical person in the room tends to anchor everyone else, and a founder who feels out of their depth will often defer rather than raise a real concern. Compare written evidence first, then discuss the gaps. A simple 1-to-5 rubric per area turns a subjective debate into a structured decision you can defend later.
Interview for your environment, not a generic one
An IT manager running a 200-person multi-site network and one who is the entire technology department at a 30-person company are different hires. Weight the questions to your reality. If the role is your first dedicated technology hire, lean on the priorities, security, and budget sets, and test explicitly for willingness to stay hands-on. If you already have technicians and an outside provider, weight leadership, vendor management, and behavioral evidence. Be specific about what the role must accomplish in the first 90 days, then ask questions that test for exactly that.
Same Questions, Same Rubric, Better Decisions
A structured interview, where every candidate answers the same questions scored against a consistent rubric, predicts on-the-job performance more reliably than an unstructured conversation, and asking the same job-related questions of everyone also keeps you inside the EEOC rules against basing decisions on protected characteristics. Structure is both the fairer approach and the more effective one.
Keep every question tied to the job and skip the small-talk traps, including the technology-specific one of using years of experience or graduation year as a stand-in for age. Ask what they have built and run instead. For the full list of what to avoid, see the guide to illegal interview questions. This is general information, not legal advice.
IT Manager Pay Benchmarks
Benchmark the offer before the first interview, so you do not spend three weeks on candidates you cannot afford. Use federal data as the baseline, then adjust down or up for your market, your scope, and how hands-on the role really is.
Median $175,140 a Year (BLS OEWS, May 2025)
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), computer and information systems managers had a median annual wage of $175,140, about $84.20 an hour, with the lowest 10 percent under $107,550 and the highest 10 percent above $297,510 (U.S. Bureau of Labor Statistics). The occupation held about 667,100 jobs, with roughly 55,600 openings projected each year on average.
Read that median carefully. The occupation bundles chief information officers and IT directors at large employers together with hands-on IT managers at 30-person companies, which pulls the middle sharply upward. A small business hiring its first dedicated technology manager should usually benchmark toward the lower half of the range and be honest in the posting about scope.
Trait
First IT Hire (Manager)
IT Manager Over a Team
Hands-on support and system work daily
Owns priorities, budget, and vendors
Manages employees or contractors
Is the entire security function
Benchmarks near the occupation median
The simplest rule: if the person will be your only technology employee, interview and pay for a hands-on manager, and say so plainly during the interview. Candidates who want a pure leadership role will self-select out, which saves everyone a wasted final round. If you are weighing a more senior technology leader instead, the CIO and IT leadership question kits cover that level.
Interviewing an IT Manager Without HR
A large company puts an IT manager candidate through a recruiter, a technical panel, and a hiring committee with calibrated scorecards. A small business puts them through one owner, between everything else, often without a technical person in the room. That reality shapes how you should run the interview, and it is where the avoidable mistakes happen.
You are hiring an IT manager but you are not technical yourself
Most owners making this hire cannot grade a technical answer on its merits, which is exactly why the questions in these sets come with a note on what a good answer sounds like. You are not judging whether the configuration is correct. You are judging whether the answer is specific, whether it stays clear when you ask a follow-up, and whether the candidate admits a limit rather than bluffing past it. Ask the question, listen against the note, write down what they said, and score it. If you want extra confidence, ask a trusted technical acquaintance to sit in on one round rather than trying to become an expert yourself.
This person will hold the keys to everything you own
An IT manager ends up with administrator rights across email, files, finance systems, and often the building. That makes continuity part of the evaluation, not an afterthought. The fix is structure rather than suspicion: keep an owner administrator account in every critical system, share the password vault rather than letting one person hold it, require documentation of systems and vendor contracts, and check references specifically for integrity and handover behavior. A strong candidate treats all of that as normal professional practice. Resistance to owner access, or a habit of keeping everything in their own head, is a meaningful red flag at any company size.
The interview is one step; the offer and onboarding are where it becomes real
Once you choose someone, the work shifts from evaluating to hiring well: a clear written offer, a confidentiality agreement, the new hire paperwork, and a structured first 90 days that includes the access handover in both directions. FirstHR fits that people side for a small business: send the offer and the confidentiality agreement for e-signature, run the onboarding workflow and policy acknowledgments as tracked tasks, and keep the signed documents on the employee profile. To be clear on scope, FirstHR is an onboarding and HR platform, not an IT management or device management tool, so pair it with those. Applicant tracking is coming soon to FirstHR.
Reference checks deserve extra weight for this role. Ask former employers two specific things: what documentation did this person leave behind, and how did the handover go when they left. The answers tell you more about continuity risk than any interview question can.
From Interview to Hire
The interview is step one. Once you choose someone, the work becomes hiring well: a written offer letter, a signed confidentiality agreement before any access is granted, and a first 90 days that includes a deliberate access handover in both directions.
Send the offer and confidentiality agreement
Confirm role, pay, and start date in writing, and have the agreement signed before any system access is granted.
Hand over access with controls
Grant administrator rights deliberately, keep an owner account in every critical system, and share the password vault.
Document what they inherit
Systems, licenses, vendor contacts, and renewal dates written down on day one, not reconstructed six months later.
Structure the first 90 days
Assess, then plan, then execute. Agree what a good first quarter looks like before they start, so progress is measurable.
Standard new hire paperwork still applies, and an onboarding template keeps the first weeks structured rather than improvised. For a technology hire, add the access and continuity items from the scorecard to that checklist so they are done on day one instead of reconstructed later.
FirstHR connects the offer, the confidentiality agreement, e-signatures, policy acknowledgments, and the onboarding workflow in one place, and keeps the signed documents on the employee profile, so a small business can run the whole hiring-to-onboarding sequence from a single system. FirstHR is an onboarding and HR platform, not an IT management or device management tool, so connect those separately. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Assess an IT manager on ownership and judgment, not hands-on speed: priorities, security, budget, vendors, and communication.
Ask when they last restored from a backup and expect a date; a candidate who has never done it is a serious risk.
Have them explain a technical decision in plain language, then ask a follow-up and see whether the answer gets clearer.
Treat security as the heaviest set, because at a small company the IT manager is the entire security function.
Score every candidate on the same 1-to-5 rubric independently, so the most technical voice in the room does not anchor the decision.
Benchmark pay against BLS data but read it down: the occupation median of $175,140 includes CIOs and directors at large employers.
Frequently Asked Questions
What questions should I ask an IT manager candidate?
Ask across five areas: leadership and prioritization, technical judgment, security and risk, budget and vendors, and behavioral evidence. The highest-value questions for a small business are walk me through your first 90 days here, how do you decide what IT works on this week when everything is urgent, how do you handle backups and when did you last restore from one, what are the first three security gaps you would expect to find here, and how would you find waste in our technology spend. Each one has a right shape of answer: a stated method, a real example, and a number or a date. Avoid quizzing on configuration trivia, because an IT manager is hired for judgment and ownership rather than for hands-on speed. This page groups more than 40 such questions by competency, each with why it is worth asking and what a strong answer sounds like.
How do I interview an IT manager if I am not technical?
You do not need to grade the technology; you need to tell a specific answer from a vague one. Ask the candidate to explain a recent technical decision as if you have no background, then ask a follow-up question and see whether the answer gets clearer or hides further behind jargon. Listen for dates and numbers: when did you last restore a backup, how many devices did you manage, what did that project cost. Strong candidates give concrete detail and admit what they did not know. Weak ones answer with product names and generalities. Every question in the sets on this page includes a note on what a good answer sounds like, so you can score without technical expertise. If you want more confidence, ask a trusted technical contact to join one interview round.
What is the difference between an IT manager, an IT director, and a system administrator?
They differ in scope and seniority. A system administrator is hands-on: servers, accounts, devices, patching, and support, usually reporting to someone else. An IT manager owns the technology function for the business, meaning priorities, budget, vendors, security posture, and any team or outside provider, while often still being hands-on at a smaller company. An IT director sits above that in larger organizations, owning strategy across multiple teams and typically several managers. For a small business, the IT manager level is the common first dedicated hire, because it combines ownership with a willingness to do the work. Interview for the level you actually need rather than the most senior title you can find, and be explicit in the interview about how hands-on the role will be.
What is an IT manager interview scorecard?
An IT manager interview scorecard is a rubric that rates a candidate from 1 to 5 on each area you care about, with space for the evidence behind each score. A useful set of areas is leadership and prioritization, technical judgment, security and risk, budget and vendor management, communication, and fit for your company size. Each interviewer completes the scorecard independently before the group discusses, which matters more in technical hiring than almost anywhere else because the most technical person in the room tends to anchor everyone else. The scorecard turns a subjective impression into a structured decision you can defend. This page includes a downloadable scorecard alongside a red-flag checklist and an access-and-continuity checklist to complete before the new hire starts.
What are the red flags in an IT manager interview?
The most reliable red flags are a candidate who has never personally restored from a backup, one who answers every question with product names instead of a method, and one who cannot explain a technical decision in plain language. Add to that anyone who treats security as somebody else's responsibility, keeps documentation and passwords only in their own head, blames users or vendors for every past failure, or wants to replace the whole environment before understanding it. At a small company, unwillingness to stay hands-on is its own red flag, because there is no one else to do the work. None of these is automatically disqualifying on its own, but two or three together usually predict the problems you will have in month six. The downloadable scorecard includes this checklist.
How much does an IT manager cost to hire?
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), computer and information systems managers had a median annual wage of 175,140 dollars, with the lowest 10 percent under 107,550 dollars and the highest 10 percent above 297,510 dollars. Read that median with care, because the occupation bundles chief information officers and IT directors at large employers together with hands-on IT managers at small companies, which pulls the middle upward. A small business hiring its first dedicated technology manager should benchmark toward the lower half of that range and adjust for local market and scope. Budget for the total cost of the role, including certifications, tooling, and the outside providers the manager will still need. This is general information, not compensation advice.
Should a small business hire an IT manager or use a managed service provider?
It depends on how much technology risk sits inside your business rather than on headcount alone. An outside provider is often the better first step when your needs are standard support, patching, and helpdesk coverage, because you buy a team and after-hours cover for a predictable monthly fee. A dedicated IT manager makes sense when technology decisions are becoming strategic, when compliance or customer security requirements are growing, or when nobody internally owns priorities and vendors. Many small companies end up with both: a manager who owns direction, security, and spend, plus a provider that handles volume support. If you hire the manager, interview specifically for vendor management, because supervising that relationship will be part of the job. Applicant tracking is coming soon to FirstHR.
How long should an IT manager interview process take?
Two to three rounds over two to three weeks is typical and usually sufficient for a small business. A first conversation of 30 to 45 minutes screens for scope match and communication, a main interview of about 60 minutes covers two or three questions from each competency with real follow-ups, and a final round brings in whoever the manager will work with most, plus reference checks. Resist adding rounds to feel more certain, because strong technology candidates move quickly and a slow process loses them. Depth beats breadth: follow-up probes on a handful of strong questions reveal more than a rushed list of thirty. Score each round immediately afterward while the answers are fresh, and use the same core questions and rubric for every candidate.
