Free IT coordinator interview questions for small businesses without HR: 40 questions on access, triage, assets, and security, plus a 1-to-5 scorecard.
40 interviewer questions across six sets, each with why it is worth asking and what a good answer sounds like, plus a 1-to-5 scorecard and a red-flag checklist. Built for small businesses hiring without an HR department. Download as DOCX.
The most expensive mistake I see small businesses make with this hire is interviewing an IT coordinator as though they were a systems administrator. The technical questions feel like the serious ones, so they get all the airtime, and the company ends up hiring the deepest engineer in the pile for a job that is mostly accounts, tickets, assets, and documentation. A quarter later the routine work is slipping and the new hire is browsing job boards.
An IT coordinator role is organizational first and technical second. That means the interview has to test coordination judgment: how they rank three urgent requests, what their offboarding steps actually are, whether they write anything down. At FirstHR, we build for companies that make this hire without an HR department, where the owner or the operations lead runs the whole process alone.
This page gives you 40 interviewer questions grouped into six sets. Every question comes with why it is worth asking and what a good answer sounds like, plus a 1-to-5 scorecard and a red-flag checklist you can download and use in the room.
TL;DR
Interview an IT coordinator on five things: accounts and access, ticket triage and user support, assets and licenses and vendors, security judgment, and behavioral evidence. Ask the same core questions of every candidate and score each area from 1 to 5. The strongest single question is the offboarding walkthrough, because it is where small companies carry the most risk.
What to Assess in an IT Coordinator
Assess coordination method before technical depth. An IT coordinator owns the organizational layer of company technology: user accounts and access, support request triage, hardware and license tracking, outside vendors, and documentation. The technical work is real but shallow and repetitive, and the difference between a good and a bad coordinator shows up in process, not in knowledge.
That is why the questions in this kit are operational rather than theoretical. Before you write your version, read the IT coordinator job description you are hiring against and decide what the role must actually own, because a coordinator supporting thirty people alongside an outside provider is a different hire from one running everything in-house.
Competency
Why it matters in this role
What a strong candidate shows
Provisioning and offboarding
The most repeated task, and the largest risk when skipped
A written checklist and same-day access revocation
Triage and prioritization
The role is chronically over-requested
Ranks by business impact, not by job title
Plain-English communication
Every employee in the company talks to this person
Explains a fix without jargon or impatience
Assets, licenses, vendors
Where an untracked stack quietly leaks money
An inventory method and a renewal calendar
Security judgment
Practical security mostly happens at this layer
Cheap, low-friction controls over big proposals
Documentation
Decides whether the role scales past one person
Writes for the next reader, not for themselves
The Six Question Sets
The 40 questions are grouped into five competency sets plus a scorecard. Weight them to your scope: if you keep a managed service provider, lean on triage and vendor management, and if the coordinator will be your only technical person, lean on security judgment and documentation.
Accounts and Access
The most repeated task
Provisioning, offboarding, least privilege, and the access record. Ask this set of every candidate regardless of how the rest of the role is scoped.
Ticket Triage and Support
The best predictor
Priority judgment, plain-English explanation, escalation boundaries, and keeping people informed. Technical depth matters less here than method.
Assets, Licenses, Vendors
The part that pays for itself
Hardware inventory, seat sprawl, renewal calendars, budget requests, and managing an outside provider. Weight this if you are hiring to fix sprawl.
Security and Data
Judgment, not certifications
Account hygiene, patching, incident response, and handling the HR and payroll data a coordinator sees while fixing problems.
Behavioral and Situational
How they really operate
STAR-style questions on mistakes, pushback, overload, and learning a new stack. Past behavior beats stated intentions.
Scorecard and Red Flags
Score, do not guess
A 1-to-5 rubric across six areas plus a red-flag checklist, so the decision rests on written evidence rather than the interview that felt best.
Replace the Bracketed Names With Your Actual Stack
The question sets use bracketed placeholders such as [Microsoft 365 / Google Workspace] and [ticket system] on purpose. Swap in the systems you actually run before the interview. A candidate who has administered your exact platform ramps up in days, and the specific version of the question gets you a specific answer instead of a general claim of familiarity. The same applies to the practical exercise: use a real ticket from last month, not a hypothetical one.
40 Questions and a Scorecard to Download
Download all six as a single Word document or copy individual sets. Each set opens with why it matters, then lists the questions with a note on why each is worth asking and what a good answer sounds like, and closes with space for notes. The final file is the scorecard and red-flag checklist.
Download All 6 Question Sets and the Scorecard
Access, triage, assets, security, behavioral, plus a 1-to-5 rubric and red-flag checklist. All in one DOCX.
Set 1: Accounts, Access, and Provisioning
Provisioning, offboarding, least privilege, and the access record. Ask this set of every candidate no matter how the rest of the role is scoped, because it is the part of the job that touches every other department.
Accounts, Access, and Provisioning Questions
IT COORDINATOR INTERVIEW: ACCOUNTS, ACCESS, AND PROVISIONING
Candidate: __
Interviewer: __
Date: _
WHY THIS SET MATTERS
Provisioning and deprovisioning is the part of the job that touches every other
department. When it is done well nobody notices. When it is done badly, a new
hire sits idle on day one and a departed employee keeps a live mailbox for a
month. Ask this set of every candidate, no matter how the rest of the role is
scoped.
QUESTIONS
1. Walk me through everything you would set up for a new hire before day one.
Why ask: this is the single most repeated task in the role, and the answer
shows whether the candidate works from a checklist or from memory.
Good answer: names a written checklist and a sequence. Identity account,
email, device build, group membership, application access by role, then a
verification step before the start date. Asks who owns approval.
2. How do you decide which applications a new hire should get access to?
Why ask: separates a coordinator who provisions by role from one who copies
the last person who did a similar job.
Good answer: access tied to a documented role profile, not cloned from a
colleague. Mentions least privilege and asks the hiring manager to confirm
anything unusual.
3. Take me through your offboarding steps on an employee last day.
Why ask: offboarding is where small companies carry the most risk and the
least process.
Good answer: revoke single sign-on first, then mailbox handling, then device
recovery, license reclaim, and a written confirmation that each step is done.
Treats same-day revocation as non-negotiable.
4. An employee is leaving on bad terms and the manager wants access cut now.
What do you do?
Why ask: tests judgment under pressure and whether they follow a defined
authority chain.
Good answer: acts quickly but confirms the instruction with the right person,
documents the time and who authorized it, and preserves data rather than
deleting the account outright.
5. How do you keep track of who has access to what?
Why ask: an access record is the artifact that proves the role is being done.
Good answer: a maintained access matrix or system-of-record export, reviewed
on a schedule rather than rebuilt in a panic during an audit.
6. How would you handle a request for admin rights from someone who does not
need them?
Why ask: coordinators get pressured by senior staff constantly. This tests
whether they can say no politely and escalate.
Good answer: explains the policy without lecturing, offers the narrowest
alternative that solves the real problem, and escalates the exception rather
than quietly granting it.
7. What is your experience with [Microsoft 365 / Google Workspace] admin?
Why ask: this is where the daily work actually happens at most small
companies.
Good answer: names real tasks (groups, license assignment, shared mailboxes,
MFA enforcement, recovery), not just that they have used the product.
8. How do you handle shared accounts and shared passwords?
Why ask: shared credentials are the most common bad habit a coordinator
inherits at a small business.
Good answer: dislikes them, moves toward named accounts and a password
manager with delegated access, and has a realistic plan for the cases that
cannot be eliminated.
NOTES
__
__
Set 2: Ticket Triage and User Support
Priority judgment, plain-English explanation, escalation boundaries, and keeping requesters informed. This set is the best predictor of whether the rest of the company will be glad you made the hire.
Ticket Triage and User Support Questions
IT COORDINATOR INTERVIEW: TICKET TRIAGE AND USER SUPPORT
Candidate: __
Interviewer: __
Date: _
WHY THIS SET MATTERS
An IT coordinator is usually the first and often the only person a frustrated
employee talks to. Technical depth matters less here than triage, priority
judgment, and the ability to explain a fix to someone who does not care how it
works. This set is the best predictor of whether the rest of the company will
be glad you hired them.
QUESTIONS
1. Three requests land at once: the CEO laptop will not boot, payroll cannot
reach the payroll system on a filing deadline, and a new hire has no email.
What order do you work them in, and why?
Why ask: priority judgment is the core skill of the role, and this question
cannot be rehearsed.
Good answer: ranks by business impact and deadline, not by job title. Payroll
first because of the deadline, then the new hire, then the CEO device, with a
loaner offered. Communicates the order to everyone waiting.
2. How do you keep people informed while a ticket is still open?
Why ask: most complaints about internal IT are about silence, not speed.
Good answer: a status update on a predictable cadence, plain language, and a
clear next checkpoint even when there is no progress.
3. Explain to me, as if I were a new employee, why they need multi-factor
authentication.
Why ask: a live test of translation from technical to plain English.
Good answer: short, concrete, and free of jargon. Frames it as protecting the
employee and the company rather than as a rule from above.
4. How do you decide when to escalate instead of continuing to troubleshoot?
Why ask: a coordinator who cannot let go burns hours on problems that belong
to a vendor or a specialist.
Good answer: a time box or a defined scope boundary, plus a clean handoff
with the diagnostic steps already documented.
5. How do you handle a user who is angry, or who has been rude to you before?
Why ask: internal support absorbs frustration all week, and the answer shows
emotional steadiness.
Good answer: de-escalates, separates the person from the problem, fixes the
issue, and raises a pattern of abuse with a manager rather than retaliating
through slow service.
6. Walk me through how you would troubleshoot an employee who cannot print.
Why ask: a deliberately mundane problem that reveals method rather than
knowledge.
Good answer: a structured narrowing process. Confirm the symptom, check
whether it is one user or many, isolate device, driver, queue, and network,
then verify the fix with the user before closing.
7. What belongs in a ticket record, and why?
Why ask: documentation habits are the difference between a role that scales
and one that lives in one person head.
Good answer: the request, the diagnosis, the resolution, and anything a
future person would need. Writes for the next reader, not for themselves.
8. How would you reduce the number of tickets you receive?
Why ask: distinguishes a ticket closer from someone who improves the system.
Good answer: finds repeat causes, fixes the root, writes short self-service
guides, and improves the onboarding setup so the same questions stop arriving.
NOTES
__
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Hardware inventory, seat sprawl, renewal calendars, budget requests, and managing an outside provider. This is the part of the role that pays for itself, so weight it if you are hiring to bring order to a sprawling stack.
Assets, Licenses, and Vendor Questions
IT COORDINATOR INTERVIEW: ASSETS, LICENSES, AND VENDORS
Candidate: __
Interviewer: __
Date: _
WHY THIS SET MATTERS
This is the part of the role that pays for itself. Unused software seats,
untracked laptops, and auto-renewing contracts are ordinary small business
leaks, and a coordinator who owns them recovers real money. If you are hiring
this role to bring order to sprawl, weight this set heavily.
QUESTIONS
1. How would you build a hardware inventory from nothing?
Why ask: most small companies hiring a first coordinator have no inventory at
all, so this is often the first project.
Good answer: a phased approach. Pull what exists from purchase records and
device management, then physically verify, then assign an owner to every
item and keep it current through onboarding and offboarding.
2. What do you record for each device, and how do you keep it accurate?
Why ask: an inventory that is not maintained is worse than none, because
people trust it.
Good answer: identifier, model, assigned user, purchase date, warranty, and
status, updated as part of the provisioning process rather than as an annual
project.
3. How do you track software licenses and catch what nobody uses?
Why ask: seat sprawl is the most common recoverable cost in a small company.
Good answer: a renewal calendar, a per-application owner, and a periodic
review of active users against paid seats, with a recommendation to cut or
downgrade.
4. A department wants a new tool. Walk me through what you do.
Why ask: tests whether the coordinator is a gatekeeper, a rubber stamp, or a
partner.
Good answer: understands the underlying need, checks whether an existing tool
covers it, reviews cost, data handling, and access implications, then presents
an option to whoever approves spending. Does not simply say no or simply buy.
5. How do you manage an outside vendor or a managed service provider?
Why ask: many small companies keep an external provider, and the coordinator
is the interface.
Good answer: a defined split of responsibilities, tickets logged and tracked
rather than handled by phone, and regular review of response times against
what was agreed.
6. How would you prepare a technology budget request?
Why ask: reveals whether the candidate can think in business terms rather
than product terms.
Good answer: ties spending to headcount, refresh cycles, and renewals, and
presents cost against outcome rather than a shopping list.
7. What is your approach to a device refresh cycle?
Why ask: unplanned replacement is expensive and always happens at the worst
moment.
Good answer: a predictable cycle by role and device type, budgeted in
advance, with a small buffer of spare machines for failures and new starters.
8. How do you handle a vendor contract that renews automatically?
Why ask: auto-renewal is where small businesses lose money quietly.
Good answer: a renewal calendar with notice dates set well before the
deadline, and an owner responsible for deciding to renew, renegotiate, or
cancel.
NOTES
__
__
Set 4: Security and Data Handling
Account hygiene, patching, incident response, and the personal data a coordinator sees while fixing problems. You are not hiring a security specialist, so ask for judgment rather than certifications.
Security and Data Handling Questions
IT COORDINATOR INTERVIEW: SECURITY AND DATA HANDLING
Candidate: __
Interviewer: __
Date: _
WHY THIS SET MATTERS
You are not hiring a security specialist, and you should not interview as if you
were. What you need is someone with sound habits who understands that the
coordinator role is where most practical security either happens or does not:
account hygiene, device standards, patching, and fast offboarding. Ask for
judgment, not certifications.
QUESTIONS
1. If you joined us on Monday, what are the first three things you would check
about our security posture?
Why ask: shows priorities and practicality within your actual constraints.
Good answer: something like MFA coverage, who holds admin rights, and whether
departed employees still have access. Practical and cheap, not a proposal for
an enterprise program.
2. An employee reports clicking a suspicious link. What happens next?
Why ask: incident response at a small business starts with this exact moment.
Good answer: thanks them first so reporting is never discouraged, then
isolates, resets credentials, reviews sign-in activity, and escalates to
whoever owns the decision. Documents the timeline.
3. How do you keep devices patched and up to date?
Why ask: patching is unglamorous, ongoing, and quietly essential.
Good answer: automated updates where possible, a compliance view of which
devices are behind, and a way to reach remote or rarely connected machines.
4. How do you handle a lost or stolen laptop?
Why ask: a specific scenario that reveals whether device management is
configured or merely intended.
Good answer: remote lock or wipe, credential reset, an assessment of what data
was on it, and a note on whether encryption was enabled.
5. How would you run security awareness for people who are not interested in it?
Why ask: coordinators usually own awareness training at a small company.
Good answer: short, frequent, and specific to real threats the company faces,
with a blame-free reporting culture rather than an annual slide deck.
6. What personal data do you expect to touch in this role, and how would you
handle it?
Why ask: the coordinator often sees HR files, payroll exports, and customer
records while fixing a problem.
Good answer: recognizes the exposure without being asked, expects to work
under confidentiality terms, and describes access on a need-to-know basis.
7. How do you balance security with people being able to get their work done?
Why ask: a coordinator who cannot balance this either gets ignored or becomes
a bottleneck.
Good answer: picks controls with a high ratio of protection to friction,
explains the reason rather than issuing rules, and accepts that a control
everyone routes around provides nothing.
8. What would you do if you found a serious problem that management created?
Why ask: tests candor and how they raise bad news upward.
Good answer: reports it directly and privately, with the risk explained in
business terms and a proposed fix, rather than either hiding it or making it
a public accusation.
NOTES
__
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
STAR-style questions on mistakes, pushback, overload, and learning a new stack quickly. Past behavior predicts performance better than stated intentions, which is why these belong in every round.
Behavioral and Situational Questions
IT COORDINATOR INTERVIEW: BEHAVIORAL AND SITUATIONAL
Candidate: __
Interviewer: __
Date: _
HOW TO EVALUATE THESE
Score behavioral answers with the STAR pattern: a real Situation and Task, the
specific Action the candidate personally took, and a measurable Result. Push for
the detail. The most useful follow-up in the entire interview is some version of
"what happened after that?"
QUESTIONS
1. Tell me about a time you were the only technical person in the room.
Why ask: this is the actual job at most small companies.
Good answer: comfort with the responsibility, a network of vendors or peers
for the gaps, and honesty about what they escalated.
2. Describe a process you documented or improved.
Why ask: coordination work is process work, and this is the strongest signal
that the candidate will leave things better than they found them.
Good answer: a concrete before and after, with the artifact named, and
evidence that other people actually used it.
3. Tell me about a time you made a mistake that affected other people.
Why ask: everyone in this role eventually revokes the wrong access or wipes
the wrong device. What matters is what happened next.
Good answer: owns it plainly, says how it was caught and fixed, and describes
the change that stopped it recurring. Blaming others is a real warning sign.
4. Describe a time you had to push back on a senior person.
Why ask: coordinators face pressure from people far above them on the org
chart, weekly.
Good answer: respectful, specific, offered an alternative, and escalated
through a defined path rather than either caving or digging in.
5. Tell me about the busiest period you have handled. How did you decide what
to drop?
Why ask: this role is chronically over-requested, so triage under load is a
permanent condition, not an exception.
Good answer: an explicit prioritization method, communication about what was
being deferred, and no pretense that everything got done.
6. Describe a time you learned a new system quickly.
Why ask: your stack will not match their last one, so learning speed matters
more than a specific tool on the resume.
Good answer: a repeatable method (documentation, sandbox, vendor support, a
small first task), with a timeline attached.
7. Tell me about a time you worked with a vendor who was not delivering.
Why ask: vendor management is a large and under-tested part of the role.
Good answer: documented the gap, escalated inside the vendor, kept internal
stakeholders informed, and had a fallback plan.
8. What part of an IT coordinator role do you like least, and how do you handle
it?
Why ask: a candor test, and a check that they understand the job includes
repetitive administrative work.
Good answer: honest about the routine parts, with a system for staying on top
of them anyway. A candidate who claims to love every part of the role is
usually telling you what they think you want.
NOTES
__
__
Set 6: Scorecard and Red Flags
A 1-to-5 rubric across six areas plus a red-flag checklist, so the decision rests on written evidence rather than on whichever conversation felt best. This is the asset most question lists leave out.
IT Coordinator Scorecard and Red Flags
IT COORDINATOR INTERVIEW SCORECARD AND RED-FLAG CHECKLIST
Candidate: __
Interviewer: __
Date: _
HOW TO SCORE
Score each area from 1 to 5 immediately after the interview, while the answers
are 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 most senior 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
Accounts and access: provisioning, offboarding, least privilege, access records
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Triage and prioritization: ranks by business impact, communicates the order
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Communication: explains technical things plainly, keeps requesters informed
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Assets, licenses, and vendors: inventory method, renewals, vendor management
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Security judgment: practical habits, incident response, handles personal data
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Documentation and process: writes things down, improves what they inherit
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
RED FLAGS (WEIGH CAREFULLY)
[ ] Prioritizes by job title instead of business impact
[ ] Cannot explain a technical concept without jargon
[ ] Treats documentation as someone else responsibility
[ ] Dismissive or impatient about non-technical users
[ ] No offboarding process beyond "disable the account"
[ ] Wants to redesign everything before understanding the business
[ ] Vague about what they personally did versus what the team did
[ ] Uncomfortable with the administrative and repetitive parts of the role
The questions open the door; the follow-ups tell you who the candidate is. Push for the artifact, the actual sequence, the real outcome. Across all six sets, the same four families of signal keep appearing, and they are visible whether or not you are technical yourself.
Coordination signals
Works from a written checklist, not memory
Names an artifact: access matrix, inventory, runbook
Confirms who approves before acting
Communication signals
Explains a technical fix without jargon
Updates requesters before they have to chase
Says no politely and escalates the exception
Judgment signals
Ranks by business impact, not by job title
Time-boxes troubleshooting before escalating
Picks controls with low friction and real protection
Red flags
Offboarding stops at disabling the account
Dismissive about non-technical users
Wants to rebuild the stack before learning the business
Below are three of the highest-signal questions in the kit, with the difference between a strong and a weak answer spelled out, so you have something concrete to score against rather than a general impression.
Three requests land at once. What order do you work them in?
Strong answer: Ranks by business impact and deadline rather than by seniority: the payroll filing that has a legal cutoff, then the new hire who cannot start work, then the executive device with a loaner offered in the meantime. A strong candidate also says they would tell each requester where they sit in the queue.
Weak answer: Starts with the most senior person by reflex, or gives no ordering logic at all. Both predict a coordinator who will be pulled around by whoever complains loudest.
Take me through your offboarding steps on an employee last day.
Strong answer: Revokes single sign-on and session access first, then handles the mailbox and file ownership, recovers the device, reclaims the license, and confirms each step in writing. Treats same-day revocation as non-negotiable and preserves data rather than deleting the account.
Weak answer: Stops at disabling the account, or treats offboarding as a task to catch up on later in the week. This is the most common gap in the role and the most expensive one.
Explain multi-factor authentication as if I were a new employee.
Strong answer: Short, concrete, and jargon-free, framed as protecting the person as well as the company. The point is not the definition. It is whether you understood it easily and would not mind hearing it from them on your own first day.
Weak answer: Reaches for acronyms, explains the mechanism instead of the reason, or sounds faintly irritated at having to explain it. That tone will reach your whole staff.
The single most useful follow-up in the whole interview is some version of what happened after that? Strong candidates have the sequel ready: the fix held, or it did not and here is what changed. Weaker ones stop at the point where the story flattered them.
A Short Practical Beats a Trivia Quiz
A 15 to 20 minute practical exercise is more revealing than any technical quiz, because it tests the judgment the role actually needs rather than recall. Avoid questions about command syntax or product version numbers. A coordinator can look those up; what they cannot look up is how to sequence a new hire setup or how to talk to an angry user.
Exercise
Time
What it reveals
Build a new hire setup checklist for our stack, out loud
15 min
Whether they think in sequences and ask about approvals
Here is a real ticket from last month. How would you triage it?
10 min
Priority judgment against genuine business context
Explain a technical concept to me as a new employee
5 min
Translation ability and tone toward non-technical staff
Walk me through offboarding someone leaving on Friday
10 min
Process discipline and risk awareness
Review this messy asset list. What would you do first?
15 min
Whether they start with method or with a purchase
Keep an unpaid exercise short and generic. If you want work specific to your business that takes real hours, pay for it, the same way you would for any other skills-based assessment. Browse the rest of the hiring templates if you need the surrounding paperwork.
How to Run the Interview
Running this interview well is mostly structure. Decide the scope, prepare the questions, ask the same core set of everyone, score on the rubric, and decide from written evidence. The sequence below works whether you are a single founder or a small panel.
Step
What to do
1. Define scope
Decide what the role owns and whether a provider covers the depth
2. Pick your sets
Weight the six sets to that scope; swap in your real platforms
3. Standardize
Ask the same core questions, in the same order, of everyone
4. Test triage and translation
The prioritization scenario and the plain-English explanation
5. Run a short practical
A real ticket or a new hire checklist, 15 to 20 minutes
6. Score independently
Rate six areas 1 to 5 with evidence before anyone discusses
7. Decide and offer
Compare written scores, then make the offer and onboard
Score immediately after each conversation while the answers are fresh. If more than one person interviews, each should complete the rubric before the group talks, which is the core discipline of a structured interview and the reason the scores end up meaning anything. A clean interview feedback step follows naturally from that.
Fair, Legal, and Structured Interviewing
A fair interview and an effective one are the same interview. Asking every candidate the same job-related questions and scoring them on the same rubric keeps you clear of the questions employers cannot ask, and it also reduces bias in a role where rapport is easy to mistake for competence.
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. Keep away from age, race, religion, national origin, sex, pregnancy or family plans, disability, and genetic information. Technical interviews have their own version of this trap: guessing when someone learned to work with computers, asking where an accent is from, or commenting on how long ago a certification was earned all drift toward age and national origin. Keep every question tied to running accounts, tickets, assets, and vendors. This is general information, not legal advice.
Use the same core questions for every candidate
Asking each candidate the same core questions and scoring them against the same rubric is both fairer and more predictive than a free-flowing conversation. It matters more than usual for a technical support role, because rapport is easy to confuse with competence when the interviewer is not technical. Write the questions before you meet anyone, ask them in the same order, and score them the same way. The six sets on this page are built to be used exactly like that: pick the sets that fit your scope, then hold them constant across the whole candidate pool.
Score independently, then discuss
When more than one person interviews, have each interviewer complete the scorecard alone before the group talks. Otherwise the first opinion voiced, or the most senior one, anchors everybody else. This is how strong quiet candidates get talked out of and confident weak ones get talked in. Compare written evidence first and discuss the gaps second. For an owner who is the only interviewer, the scorecard still earns its place: it forces you to name the evidence behind a rating instead of carrying a general impression into the offer.
Match the questions to your actual stack and scope
An IT coordinator supporting thirty people with an outside provider is a different hire from one running everything in-house across three sites. Decide first what the role must own, then weight the sets accordingly. If you keep a managed service provider, weight vendor management and triage. If the coordinator is your only technical person, weight security judgment and documentation. Replace the bracketed platform names in the question sets with the systems you actually run, so the answers you get are about your environment rather than a generic one.
Structure Is Both the Fairer and the More Effective Approach
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 within the EEOC rules against basing decisions on protected characteristics. For a technical support hire specifically, the National Institute of Standards and Technology maintains a small business cybersecurity resource that is a useful reference for what to expect a coordinator to know.
One classification note before you write the offer. Most IT coordinator roles are non-exempt and therefore overtime-eligible, because the federal computer employee exemption requires a primary duty of systems analysis, system design, or programming, which coordination work generally does not meet. Classify on the duties you actually assign. This is general information, not legal advice.
What the Role Pays
Anchor the range before the first interview, because a scope you cannot pay for produces candidates you cannot hire. There is no federal occupation titled IT coordinator, so the honest approach is to benchmark against the nearest classification and adjust for scope and location.
Nearest Benchmark: $61,860 Median (BLS OEWS, May 2025)
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), computer user support specialists had a national median annual wage of $61,860, with the 10th percentile at $40,980, the 25th at $49,000, the 75th at $79,040, and the 90th at $100,540. More technical adjacent classifications run higher: $76,220 for computer network support specialists and $99,130 for network and computer systems administrators (U.S. Bureau of Labor Statistics, OEWS national estimates).
For a standard in-house coordinator, the median is the honest anchor. Adjust down for a part-time or hybrid office and technology role, and up where the coordinator genuinely owns assets, licenses, and budget in a high-cost metro. If your range sits well below the benchmark, expect to interview candidates closer to a help desk profile and scope the role accordingly.
Interviewing an IT Coordinator Without HR
At a large company this hire runs through a recruiter, a technical panel, and a structured debrief. At a small business the owner or the operations lead runs the interview alone, usually without the technical background to grade the answers. Here is how to make that work rather than pretending otherwise.
You are not technical enough to grade the technical answers
Most owners hiring a first IT coordinator cannot tell a deep answer from a confident one, which is why the question sets here pair every question with a note on what a good answer sounds like. You are not grading the technology. You are grading method: does the candidate work from a checklist, rank by business impact, explain plainly, and write things down. Those four signals are visible to anyone. If you want a technical opinion, ask your existing provider or a technical friend to sit in on the second round and score the same rubric independently.
You will be tempted to hire a systems administrator by mistake
The strongest resume in the pile is often someone more technical than the role needs, and hiring them feels like a bargain. It usually is not. A coordinator role is organizational first: accounts, tickets, assets, vendors, and documentation, day after day. A candidate who wants deep engineering work will be bored within a quarter and gone within a year, and the routine work is exactly what will slip first. Interview for appetite as well as ability, and ask directly which parts of the job they like least.
The interview is step one, and access is what makes this hire different
An IT coordinator gets administrative rights across your systems on their first week, which is earlier and broader than almost any other hire. That changes onboarding: a signed offer, a confidentiality agreement, documented access grants, and a written record of what was issued and when. FirstHR fits that people side for a small business: send the offer for e-signature, run the new hire paperwork as a task workflow, and keep the signed documents and access acknowledgments on the employee profile. To be clear on scope, FirstHR is an onboarding and HR platform, not device management, a ticket system, or an applicant tracking system, so pair it with those. Applicant tracking is coming soon to FirstHR.
One more practical safeguard: check references properly for this role. A reference check that asks specifically about reliability, documentation habits, and how the person handled being the only technical contact will tell you more than another interview round would.
From Interview to Onboarding
Once you choose someone, this hire has an unusual onboarding requirement: administrative access across your systems, granted earlier and more broadly than for almost any other role. That means a signed offer letter and a confidentiality agreement before any credentials are issued, not after.
Send the offer and the NDA
Confirm role, pay, classification, and start date in writing, and have a confidentiality agreement signed before any system access is granted.
Grant access on the record
Document every admin right issued, who approved it, and when. Your new coordinator should inherit a clean record and then maintain it.
Set the first 90 days
Name the first project: usually the inventory, the access matrix, or a documented onboarding checklist, with a review date attached.
Store the paperwork
Keep the signed offer, NDA, I-9, W-4, and policy acknowledgments in one place, organized and easy to produce later.
Then give the new coordinator a named first project. The technology side of onboarding is usually the right one, because building the new hire setup checklist forces them to learn every system you run, and it leaves you with an artifact. Applicant tracking is coming soon to FirstHR, so pair this kit with whatever you currently use to track candidates.
FirstHR connects the offer, the confidentiality agreement, e-signatures, the new hire paperwork, and the access acknowledgment checklist in one place, and keeps the signed documents on the employee profile where you can produce them later. FirstHR is an onboarding and HR platform, not device management, a ticket system, or accounting software, so connect those separately. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Interview an IT coordinator on coordination method first and technical depth second, because the role is organizational before it is technical.
The offboarding walkthrough is the single highest-signal question, since it is where small companies carry the most risk and the least process.
Test triage with a real scenario: a strong candidate ranks by business impact and deadline, never by job title.
Ask the candidate to explain something technical in plain English, because that tone will reach every employee in the company.
A 15 to 20 minute practical on a real ticket beats a technical quiz, which tests recall rather than judgment.
Benchmark pay against computer user support specialists, a $61,860 national median (BLS OEWS, May 2025), then adjust for scope and location.
Score six areas from 1 to 5 independently with written evidence before anyone discusses the candidate.
Frequently Asked Questions
What questions should I ask an IT coordinator candidate?
Ask across five areas: accounts and access, ticket triage and user support, assets and licenses and vendors, security and data handling, and behavioral evidence. The highest-value questions are specific and operational. Walk me through everything you would set up for a new hire before day one. Take me through your offboarding steps on an employee last day. Three urgent requests land at once, what order do you work them in and why. Explain multi-factor authentication as if I were a new employee. Tell me about a process you documented or improved. Each of these reveals method rather than memorized knowledge, which is what actually predicts performance in a coordination role. This page groups 40 such questions into six downloadable sets, each with a note on why the question is worth asking and what a good answer sounds like.
What is the difference between an IT coordinator and a systems administrator?
An IT coordinator owns the organizational layer of company technology while a systems administrator owns the technical layer. The coordinator handles user accounts and access, triages and routes support requests, tracks hardware and software licenses, manages outside vendors, and keeps documentation current. A systems administrator designs, builds, and maintains servers, networks, and infrastructure, and works at greater technical depth. The distinction matters in the interview because the most common hiring mistake is interviewing a coordinator as though they were an administrator, then hiring someone more technical than the role needs, who becomes bored with the routine coordination work within a quarter. Decide what your role must own before you write the questions, and interview for appetite as well as ability.
How do I interview an IT coordinator if I am not technical myself?
You do not need to grade the technology, because you can grade the method. Four signals are visible to any interviewer: does the candidate work from a written checklist rather than memory, do they rank competing requests by business impact rather than by job title, can they explain a technical thing in plain English, and do they write things down for the next person. Every question in these sets includes a note on what a good answer sounds like so you can judge against something concrete. If you want a technical opinion as well, ask your existing provider or a technical friend to join the second round and complete the same scorecard independently, then compare written evidence before you discuss.
Should I give an IT coordinator candidate a practical test?
A short practical exercise is more revealing than a technical quiz, and 15 to 20 minutes is usually enough. Good options include asking the candidate to talk through building a new hire setup checklist for your actual stack, walking them through a real ticket you received last month and asking how they would triage it, or asking them to explain a technical concept to you as though you were a new employee. Keep it unpaid only if it is brief and generic. If you want work that is specific to your business and takes real hours, pay for it. Avoid trivia questions about command syntax or product version numbers, because they test recall rather than the coordination judgment the role actually needs.
How much does an IT coordinator make?
There is no federal occupation titled IT coordinator, so the figure has to be benchmarked against the nearest classification. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), computer user support specialists had a national median annual wage of $61,860, with the 10th percentile at $40,980 and the 90th at $100,540. More technical adjacent classifications run higher: computer network support specialists at a $76,220 median and network and computer systems administrators at $99,130. For a standard in-house coordinator role, the median is the honest anchor. Adjust down for a part-time or hybrid office and technology role, and up where the coordinator genuinely owns assets, licenses, and budget in a high-cost metro area.
What are the biggest red flags in an IT coordinator interview?
The clearest red flags are prioritizing by job title instead of business impact, an offboarding process that stops at disabling the account, and any dismissiveness toward non-technical users, since that tone will reach your whole staff. Watch also for candidates who cannot explain a concept without jargon, who treat documentation as someone else’s responsibility, who want to redesign your entire stack before understanding the business, or who are vague about what they personally did versus what their team did. One softer signal matters too: a candidate who claims to enjoy every part of the role is usually telling you what they think you want to hear, because a coordinator job contains real repetitive administrative work.
Is an IT coordinator exempt or non-exempt under the FLSA?
Most IT coordinator roles are non-exempt and therefore overtime-eligible, though classification always depends on actual duties rather than the job title. The federal computer employee exemption is narrow: it requires a primary duty of systems analysis, program or system design, or programming, and coordination work such as account provisioning, ticket triage, asset tracking, and vendor management generally does not meet that test. The administrative exemption is also a poor fit for most coordinator roles because it requires the exercise of discretion and independent judgment on matters of significance. Classify based on the duties you actually assign, and review the Department of Labor guidance or ask an employment attorney before treating the role as exempt. This is general information, not legal advice.
How long should an IT coordinator interview be?
Plan 45 to 60 minutes for the main interview, which is enough to cover two or three questions from each set, ask real follow-ups, and leave room for the candidate’s own questions. Depth beats breadth here: the follow-up probe on a strong question tells you more than three more questions would. A common structure is a 20-minute screen, then a 60-minute structured interview using these sets, then a short practical exercise with whoever the coordinator will work alongside. Score immediately after each conversation while the answers are still fresh, using the same rubric for every candidate, and have each interviewer score independently before the group compares notes.
