IT Coordinator interview questions, and how to answer them

An IT coordinator interview tests whether you can keep loose ends tied without being chased. You'll get some troubleshooting, but the questions that decide it are about process: onboarding, offboarding, inventory, vendors and how you talk to people who just want their laptop to work. Prepare stories about things you organised, not only things you fixed.

The process

What happens in each round

  1. 1

    Recruiter phone screen

    What happens

    Whether you've actually supported users, which ticketing and device management tools you've touched, and whether your schedule and pay expectations fit the role.

  2. 2

    Hiring manager interview

    What happens

    How you juggle competing requests, how you explain technology to non-technical staff, and whether you'd keep onboarding, inventory and vendor work moving without reminders.

  3. 3

    Practical or scenario round

    What happens

    Your troubleshooting logic on a realistic prompt, such as a user who can't reach a shared drive, or a walkthrough of setting up a new starter in Active Directory or Entra ID.

  4. 4

    Meeting the people you'd support

    What happens

    Whether HR, the office manager or a department head would want to work with you. It often feels like a casual chat, but it's a test of how clearly and calmly you explain things.

Questions you're likely to get

1.HR tells you a new employee starts next Monday. Walk me through everything you do between now and their first morning.

Why they ask

Onboarding is the most visible thing a coordinator does. If it goes wrong, the new hire's first impression of the company is a login that doesn't work.

How to answer

  • Confirm the role, manager, start date and whether they're remote or in the office
  • Create the account from a template or group so permissions match the team, not a copy of someone else's access
  • Assign and image or enroll a laptop in Intune or Jamf, and ship it early if they're remote
  • Set up licenses, email, shared mailboxes and any team-specific apps, then test the login yourself
  • Book a short first-morning check-in and close the ticket with notes
2.An employee is let go this afternoon and the parting wasn't friendly. What do you do, and in what order?

Why they ask

Offboarding is where a coordinator protects the company. They want to hear that you move fast, work with HR on timing and don't leave access open.

How to answer

  • Agree the exact cut-off time with HR and the manager so access ends as the meeting ends
  • Disable the account, revoke sessions and remove MFA methods rather than just changing the password
  • Handle the mailbox and files as the manager and policy require, such as converting to a shared mailbox
  • Recover or remote-lock devices, and update the asset register
  • Check for shared passwords or admin accounts they knew and rotate them
3.How do you keep track of hardware and software across the company?

Why they ask

Asset and license tracking is often the reason the role exists. A lost laptop or an unused license is money the manager has to explain.

How to answer

  • Name the tool you've used, whether Snipe-IT, Lansweeper, ServiceNow asset management or a well-kept spreadsheet
  • Tie every device to a person, a serial number and a status like in use, spare or retired
  • Update records as part of onboarding and offboarding, not as a separate chore
  • Review license counts before renewals so you only pay for seats people use
4.A software renewal is due soon and the vendor's quote came in higher than last time. What do you do?

Why they ask

Coordinators often handle renewals and purchase requests. They're checking whether you'll just forward the quote or actually do something with it.

How to answer

  • Pull actual usage to see how many seats or features the team really needs
  • Ask the vendor or reseller why the price changed and what options exist, such as a different tier
  • Check whether another tool the company already pays for covers the same need
  • Bring your manager a short recommendation with the options, not just the problem
5.A user says they can't get to the shared drive. Talk me through how you'd handle it.

Why they ask

This is the practical check. They want structured troubleshooting from the simplest cause outward, and they want to hear how you talk to the user while you do it.

How to answer

  • Ask what changed and whether anyone else is affected, which tells you if it's one user or the whole office
  • Check the basics: network connection, VPN if remote, and whether they can reach other resources
  • Look at permissions and group membership in Active Directory or the file share settings
  • Escalate to the systems administrator or managed service provider with clear notes if it's server-side
  • Tell the user what you found and close the loop
6.Your managed service provider has had a ticket open for days and the user keeps asking you about it. How do you handle that?

Why they ask

Many coordinators sit between staff and an outside provider. They need someone who can push a vendor politely without burning the relationship.

How to answer

  • Check the ticket history and what the provider is waiting on, including anything you owe them
  • Follow up by phone rather than another email, and ask for a named owner and a next step
  • Use the escalation path in the contract if it stays stuck
  • Keep the user updated so they hear it from you before they ask again
7.How would you roll out multi-factor authentication to staff who don't want it?

Why they ask

Coordinators run a lot of small rollouts. This question checks your planning and how you handle people who push back.

How to answer

  • Explain the reason in plain terms, such as phishing and stolen passwords, without lecturing
  • Pilot it with a friendly team first and fix the rough edges before everyone gets it
  • Send short setup steps with screenshots and hold drop-in help sessions
  • Plan for lost phones and the people who don't use smartphones
  • Give leadership a date and stick to it
8.Which ticketing and device management tools have you used, and how deeply?

Why they ask

Postings name specific tools. They want to know whether you've used them as an admin or only as someone logging tickets.

How to answer

  • Name each tool and say plainly what you did in it, such as building a request form in ServiceNow or enrolling Macs in Jamf
  • Separate what you administered from what you only used
  • Mention how quickly you picked up a tool you hadn't seen before
9.Tell me about a time you had more urgent requests than you could handle at once.

Why they ask

The job is constant interruptions. They're listening for how you decide what goes first and how you tell people they're waiting.

How to answer

  • Set the scene briefly, with the actual requests that collided
  • Explain how you ranked them, such as security and outages before convenience
  • Say who you told and how you set expectations
  • Share what happened and what you'd do differently
10.Tell me about a process you documented or improved.

Why they ask

A good coordinator leaves systems behind, not just closed tickets. This shows whether you think past today's request.

How to answer

  • Describe the messy starting point and why it was a problem
  • Explain what you built, such as a checklist, a knowledge base article or a request form
  • Say how you got people to actually use it
  • Describe the result in terms the interviewer cares about, like fewer missed setups
11.Why do you want a coordinator role rather than a purely technical one?

Why they ask

They want to be sure you won't be bored by the scheduling, ordering and vendor side of the job and leave for a sysadmin role within months.

How to answer

  • Say what you enjoy about organising and closing loops, with a real example
  • Show you still like the technical side and want to keep those skills sharp
  • Connect the role to where you want to go, such as IT management or project work

Mistakes that sink good candidates

Talking only about fixing things and never about tracking, scheduling or following up

Speaking badly about users or past vendors, since the job is mostly about keeping those relationships working

Claiming admin experience in a tool you've only logged tickets in

Giving no example of anything you organised or documented on your own initiative

Need more IT Coordinator interviews to prep for?

HeroApply applies to IT Coordinator jobs that match you, every day. 58 jobs are open today.

Find IT Coordinator jobs