Systems administrator interview questions, with a scoring guide
Runs the servers, network, backups and security that keep the business online. Here are 22 questions for a systems administrator interview. Each comes with a follow-up and a 1 to 5 scoring guide so you can compare candidates fairly.
Use these as a free interview guide
Writing the job ad too? Start from our systems administrator job description template.
Questions specific to the systems administrator role
Role-specific
When did you last test a restore from backup, and how did it go?
Follow-up: What would you change about that backup setup?
1 WeakHas never tested a restore.
3 SolidRestored a file when someone asked for it.
5 StrongRuns scheduled restore tests against recovery targets, and gives an example of a real gap they found and fixed.
Role-specific
Walk me through how you roll out a security patch to servers without disrupting the business.
1 WeakInstalls it whenever it pops up.
3 SolidPatches after hours.
5 StrongReads the release notes, tests on a less critical system, books a maintenance window, takes a snapshot, has a rollback plan, and logs the change.
Role-specific
Tell me about an outage you handled. What happened, and what did you change afterward?
Follow-up: How did you keep people informed while it was down?
1 WeakBlames the vendor or can't give details.
3 SolidGot things running again, with no follow-up.
5 StrongRestored service, kept people updated, found the root cause, made a permanent fix, and documented it.
Role-specific
What have you automated with scripting, and what did it save?
1 WeakHasn't scripted anything.
3 SolidHas run scripts that others wrote.
5 StrongA specific PowerShell or shell script they wrote, the time or errors it saved, and how it's documented for others.
Behavioural questions by skill
Behavioural questions ask about something the person actually did. Past behaviour is a better guide than "what would you do" answers alone.
Problem solving
Works out the cause and fixes it properly.
Tell me about a problem at work that you solved without being told how.
Follow-up: How did you work out what was wrong?
1 WeakWaited to be told what to do.
3 SolidSolved it with a common fix.
5 StrongFound the cause and fixed it so it stayed fixed.
Describe a time something went wrong in the middle of a busy day. What did you do first?
Follow-up: Who did you tell, and when?
1 WeakPanicked or froze.
3 SolidCalled for help right away without trying anything.
5 StrongMade it safe, tried the obvious fixes, and escalated with clear information.
Tell me about a time you noticed a better way to do a routine task.
Follow-up: What happened when you raised it?
1 WeakNever looked for one.
3 SolidNoticed it but didn't act.
5 StrongSuggested or tested it and can describe the result.
Reliability and follow-through
Shows up, keeps commitments, owns mistakes.
Tell me about a time you committed to something at work and it became hard to follow through. What did you do?
Follow-up: What was the result, and what would you do the same next time?
1 WeakLet it slide without telling anyone.
3 SolidFollowed through, but only after reminders or with a late heads-up.
5 StrongFlagged the risk early, adjusted the plan, and delivered or arranged cover.
Describe a stretch where you had to be consistent with early starts, long shifts or a tight schedule. How did you manage it?
Follow-up: What did you do on the days it was hardest?
1 WeakVague answer with no clear routine or example.
3 SolidShowed up reliably but relied on luck more than planning.
5 StrongSpecific habits that kept them on time, with an example to back it up.
Tell me about a time you made a mistake that affected someone else's work. What happened next?
Follow-up: How did the other person find out?
1 WeakHid it, blamed others, or can't recall any mistakes.
3 SolidOwned it when asked and fixed the immediate problem.
5 StrongRaised it right away, fixed it, and changed something so it wouldn't happen again.
Attention to detail
Gets the small things right.
Tell me about a time you caught a mistake before it caused a problem.
Follow-up: How did you spot it?
1 WeakNo example.
3 SolidCaught one by chance.
5 StrongCaught it because of a habit or check they always do.
Walk me through how you check your own work before calling it done.
Follow-up: Has that check ever caught something?
1 WeakThey don't.
3 SolidA quick look over.
5 StrongA clear routine that fits the task.
Describe a task where getting the small details right really mattered.
Follow-up: What would have happened if they were wrong?
1 WeakCan't name one.
3 SolidNames one, but light on how.
5 StrongExplains the details, why they mattered, and how they got them right.
Honesty and integrity
Does the right thing, including when nobody's looking.
Tell me about a time you were asked to do something at work that you felt wasn't right.
Follow-up: What happened afterwards?
1 WeakDid it without question.
3 SolidDid it but felt uneasy.
5 StrongRaised it respectfully and did the right thing.
Describe a time you handled cash, stock or private information. How did you keep it secure?
Follow-up: Did anything ever go missing?
1 WeakVague answer.
3 SolidFollowed the basics.
5 StrongSpecific precautions and an example.
Tell me about a time you admitted you didn't know something.
Follow-up: What did you do next?
1 WeakNever has.
3 SolidAdmitted it when pressed.
5 StrongAdmitted it early and found the answer.
Communication
Explains clearly and keeps people in the loop.
Tell me about a time you had to explain something complicated to someone who was new to it.
Follow-up: How did you know they understood?
1 WeakCan't explain clearly, even in the interview.
3 SolidExplained it but didn't check understanding.
5 StrongUsed plain words or examples and checked they got it.
Describe a time you had to give bad news to a customer, coworker or manager.
Follow-up: What did you say first?
1 WeakAvoided it or left it to someone else.
3 SolidDelivered it, but bluntly or late.
5 StrongDelivered it early and clearly, with a next step.
Tell me about a time a misunderstanding caused a problem at work. What did you learn?
Follow-up: What do you do differently now?
1 WeakBlames the other person entirely.
3 SolidFixed the issue with little reflection.
5 StrongFixed it and changed how they communicate, such as confirming in writing.
Working under pressure
Stays steady when it gets busy.
Tell me about your busiest shift or tightest deadline. How did you handle it?
Follow-up: What did you do first?
1 WeakFell apart or can't describe one.
3 SolidGot through it.
5 StrongPrioritized, stayed calm, and kept quality up.
Describe a time you had too much to do and not enough time. What did you drop or delay?
Follow-up: Who did you tell?
1 WeakTried to do everything and missed things.
3 SolidDropped things without telling anyone.
5 StrongPrioritized and told the right people what would slip.
Tell me about a time you stayed calm when people around you didn't.
Follow-up: What did you do to help?
1 WeakNo example.
3 SolidStayed calm themselves.
5 StrongStayed calm and helped settle others.
Prescreen questions for systems administrator candidates
Ask these on a five-minute phone call or send them as a form before you book interviews.
- Are you legally entitled to work in Canada? (Yes / No)
- Which days and times are you available to work?
- When could you start?
- What pay are you looking for?
- What interests you about this job?
- Which have you administered hands-on? (Windows Server and Active Directory or Entra ID / Linux servers / Both / Neither)
- This role includes after-hours maintenance windows and an on-call rotation for outages. Are you able to take part? (Yes / No)
How to score the answers
- Ask every candidate the same questions in the same order. That's what makes scores comparable.
- Write down what they did, not your impression. "Closed alone on a Saturday and restocked for the morning" beats "seems reliable".
- Score each answer from 1 to 5 against the guide under the question. A 3 is a solid, acceptable answer.
- Average the scores and read the notes behind any big gap between interviewers.
- Check references on the areas where you're least sure.
Questions to avoid
In Canada, hiring questions should be about the job. Human rights laws protect people from being treated differently because of things like their age, family status, disability, religion, race, place of origin, sex, sexual orientation or gender identity. Stay away from questions like these:
- "How old are you?" or "When did you finish high school?"
- "Do you have kids?" or "Are you planning a family?"
- "Where are you from originally?" (You can ask: "Are you legally entitled to work in Canada?")
- "Do you have any health problems?" (You can ask: "This job involves [a real duty]. Can you do that, with or without accommodation?")
This is general information, not legal advice. Rules vary by province.
Questions
What should I ask in a systems administrator interview?
Ask about the parts of the job that matter most: problem solving, reliability and follow-through, attention to detail, honesty and integrity, plus role-specific questions such as "When did you last test a restore from backup, and how did it go?" Ask every candidate the same questions so you can compare them fairly.
How do I score a systems administrator interview?
Score each answer from 1 to 5 against a short guide that describes a weak, solid and strong answer. Score what the person actually did in their example, not how confident they sounded. Then average the scores and read the notes behind any big differences.
What should I ask before interviewing a systems administrator?
Use a short prescreen: work eligibility, availability, start date, pay expectations and the must-haves for the role, such as "Which have you administered hands-on?"
Turn this page into a ready-to-use interview guide
Staffkin builds a systems administrator prescreen and interview guide in one click, gives you a fillable PDF, and lets you score candidates side by side. Free for your first job.
Start freeRelated roles