Interview scorecard for IT support specialists, with anchors for each competency
On this page
- Which competencies should an IT support specialist scorecard cover?
- The scorecard: weights and what a 1, 3 and 5 look like
- Copy-ready IT support specialist scorecard
- What should each interviewer ask, and what counts as evidence?
- Two work samples that produce scoreable evidence
- A filled example
- How do you adjust it for the seat and the level?
- Mistakes specific to scoring IT support specialists
- Where does this scorecard fit in the hiring process?
- Questions people ask
An IT support specialist interview scorecard should score six things: troubleshooting method, communication with non-technical users, security and access judgment, technical knowledge of your environment, documentation and ticket notes, and prioritization with escalation. Below is a copy-ready scorecard with example weights, what a 1, 3 and 5 look like on a 1–5 scale, two work samples and a filled example. Resetting a password or multifactor authentication for an unverified caller is a pass/fail gate, not a low score, and certifications such as CompTIA A+ are checked with the issuer, never scored.
The five points follow the 1–5 interview rating scale: 1 is no evidence or evidence of the opposite, 3 is a clear example that meets the bar for the level, 5 is rare. The layout comes from the interview scorecard template. The full loop, with a five-ticket queue exercise, a frustrated-user role-play and a social engineering call, is in the interview guide for IT support roles; this page adds the anchors each row is scored against and two different exercises, a same-day leaver ticket and a knowledge base rewrite. The scorecard builder prints a 1–4 version if your team uses four points.
Which competencies should an IT support specialist scorecard cover?
- Troubleshooting method. Do they gather facts, isolate the layer (account, device, network, service) and change one thing at a time, or reboot and reimage by reflex?
- User communication and service. Can they calm a stressed user, explain in plain words, offer a workaround and set a clear next step?
- Security and access judgment. Do they verify identity before resets, grant only the access a request needs, remove access promptly for leavers and report what looks wrong?
- Technical knowledge of the environment. Operating systems, directory and identity, email and collaboration tools, endpoint management and basic networking at the depth your tier needs.
- Documentation and ticket notes. Could the next technician pick up their ticket without a conversation, and do recurring fixes become knowledge base articles?
- Prioritization and escalation. Do they rank work by impact and urgency, and hand off with enough notes that tier 2 does not start over?
The scorecard: weights and what a 1, 3 and 5 look like
Weights are an example for a tier 1–2 IT support specialist in a 300-person office with remote staff. Agree yours with the IT manager at intake and lock them before the first interview; weighted interview scorecard shows how.
| Competency | Weight | 1 looks like | 3 looks like | 5 looks like |
|---|---|---|---|---|
| Troubleshooting method | 25% | Guesses, or jumps to a reboot or reimage without asking what changed or who else is affected. | Asks scoping questions, isolates the layer, tests one change at a time and confirms the fix with the user. | All of a 3, plus finds a root cause behind a repeat ticket and removes it for everyone (a policy, a script, a vendor fix). |
| User communication and service | 20% | Jargon, blame ("you must have clicked something"), or no next step given. | Acknowledges the impact, offers a workaround first, explains in plain words and says when they will follow up. | Turns an angry user into a calm one under a deadline, and changes something afterward so the next user does not hit the same wall. |
| Security and access judgment | 15% | Would reset or grant access because the caller sounds senior or urgent. | Follows the verification process every time, grants only what the request needs, and knows the steps for a leaver. | Spotted and reported a social engineering attempt or an access pattern that looked wrong, and can say what changed after. |
| Technical knowledge of the environment | 15% | Cannot explain the basics the tier needs (an IP address versus DNS, a local versus a directory account). | Explains the core systems of the seat accurately and knows where their knowledge stops. | Depth beyond the tier in one area (scripting, endpoint management, networking) used to fix something real. |
| Documentation and ticket notes | 15% | Notes like "fixed" or "user ok now". | Symptom, cause, steps taken and fix, written so the next technician can follow it; links or writes an article for a recurring issue. | Built or reorganized a knowledge base that measurably cut repeat tickets, and can say how they knew. |
| Prioritization and escalation | 10% | Works tickets in arrival order; escalates with no notes, or holds a ticket they cannot fix. | Ranks by impact and urgency, acknowledges waiting users, and escalates with what was tried and what was ruled out. | Notices that separate tickets share a cause, raises it as one incident, and keeps users informed until it is closed. |
Copy-ready IT support specialist scorecard
Candidate: [name] Role: [IT support specialist], [tier]
Interviewer: [name] Stage: [screen / ticket exercise / role-plays / hiring manager]
Pass/fail (checked before scoring)
Social engineering call: followed verification; no reset or MFA change
for an unverified caller: [ ] pass [ ] fail
Certification required by the job description (e.g. CompTIA A+): [ ] verified [ ] n/a
Can meet the schedule and essential functions in the job description,
with or without reasonable accommodation: [ ] yes [ ] no
Troubleshooting method (25%) Score 1-5: [ ]
Evidence: [questions asked, layer isolated, fix confirmed with the user]
User communication and service (20%) Score 1-5: [ ]
Evidence: [workaround offered, plain words, next step and time given]
Security and access judgment (15%) Score 1-5: [ ]
Evidence: [leaver steps, least privilege, what they would report]
Technical knowledge of the environment (15%) Score 1-5: [ ]
Evidence: [systems explained accurately, limits named]
Documentation and ticket notes (15%) Score 1-5: [ ]
Evidence: [resolution note, knowledge base rewrite]
Prioritization and escalation (10%) Score 1-5: [ ]
Evidence: [order chosen and why, handoff notes]
Weighted score: sum of (weight x score) / sum of weights scored = [ ]
Recommendation: [Strong yes / Yes / No / Strong no]
What should each interviewer ask, and what counts as evidence?
The table gives the 1, 3 and 5. Here is the question that tests each row and what a 2 and a 4 sound like.
Troubleshooting method
Ask: "A user says Wi-Fi works on their phone but not their laptop, in the same room. Talk me through it." Evidence: questions before fixes (one device or many, what changed, any error), then the layer: adapter, network profile, address, DNS, then the service.
- 2: Reaches a plausible fix but by trying several things at once, so cannot say which one worked.
- 4: Methodical, and checks whether other laptops of the same model or update level have the same fault.
User communication and service
Ask: "Explain to me, as a user who does not care about computers, why I have to restart for this update today." More in interview questions for customer service mindset.
- 2: Accurate but full of terms the user would not know, or no answer to "how long will it take?"
- 4: Short, plain and honest, with a choice of time where policy allows.
Security and access judgment
Ask: the leaver ticket below, and "What do you do when a caller cannot pass verification but says they are an executive?" The reason this row exists: CISA's advisory on the Scattered Spider group (AA23-320A, first released November 16, 2023 and last revised July 29, 2025, checked November 2026) describes attackers who posed as employees to get IT and help desk staff to reset passwords and transfer multifactor authentication tokens.
- 2: Holds the line on verification but has no route to help the genuine caller (a call-back to the number on file, a manager's confirmation).
- 4: Holds the line, offers the approved route, and reports the call to security the same day.
Technical knowledge of the environment
Ask: two or three questions written from the job description's own systems, the same for every candidate, such as "A new laptop cannot join the domain or enroll in device management. What do you check?" Accept a different but correct route.
- 2: Knows the terms but cannot connect them to a fault.
- 4: Explains the cause and how they would confirm it, and says what they would look up rather than guess.
Documentation and ticket notes
Ask: the knowledge base rewrite below, and "Show me, in words, the note you would leave on a ticket you are escalating." More in interview questions for documentation skills.
- 2: Notes have the fix but not the symptom or what was ruled out.
- 4: Notes a stranger could follow, and a habit of turning the third repeat of a fix into an article.
Prioritization and escalation
Ask: "You have a printer ticket from the CEO's assistant, an outage report from three people in sales and a new starter arriving tomorrow with no laptop. What order, and what do you tell each person?"
- 2: Ranks by the sender's seniority rather than impact.
- 4: Multi-user outage first, a quick acknowledgment to the others, and the new starter set up before day's end with the manager told.
Two work samples that produce scoreable evidence
Both are invented and the same for every candidate. Tell candidates the format in advance and ask whether they need an adjustment for the process; the EEOC's guidance on pre-employment questions says an employer may ask applicants whether they will need a reasonable accommodation for the hiring process, and may ask applicants to describe or demonstrate how they would perform job tasks if everyone in the job category is asked. See also ADA accommodations in interviews.
Same-day leaver ticket (15 minutes, verbal). "It is 4:40 p.m. on Friday. An email from an HR partner says an employee in finance was let go this afternoon, is still signed in on a company laptop at home, and asks you to 'shut everything off now'. Your process says terminations come as a ticket from HR with the manager copied. What do you do, in what order, and what do you write down?"
What to listen for: confirming the request is genuine through the channel the process names before acting (a call to HR on a known number, the HR ticket), because a forged urgent email is a classic attack; then disabling the account and ending active sessions, removing or resetting the multifactor methods, blocking or locking the device under policy, and holding the mailbox and files as the manager or legal decides rather than deleting them; arranging return of equipment; and a timed note of each step. This scores security and access judgment, documentation and prioritization.
Knowledge base rewrite (15 minutes, written). Hand over an invented internal article: "VPN not working: open the client, go to settings, change the DNS server to 10.0.0.5, reboot. If still broken call IT." Brief: "Rewrite this for non-technical staff working from home."
What to listen for: a first check that the home internet works at all; numbered steps in plain words, one action each; removing the DNS change, which most users should not make, into a technician-only section; when to stop and call; and what to have ready for the desk (the error text, the time, the device name). This scores documentation and user communication.
A filled example
A made-up candidate for a tier 2 IT support specialist at a 300-person firm, scored after the ticket exercise, the role-plays, the leaver ticket, the rewrite and the hiring manager interview:
Pass/fail: passed the social engineering call; offered a call-back to the number on file.
Troubleshooting method — 4. Isolated the VPN ticket to a missing route for one subnet and asked whether other remote users on that office's share were affected.
User communication and service — 3. In the frustrated-user role-play, offered web access to the files first and gave a clear time for a loaner.
Security and access judgment — 4. Called HR back before acting on the leaver email, ended sessions before disabling the account, and asked who decides about the mailbox.
Technical knowledge of the environment — 3. Solid on identity and email; said plainly that device management was new to them.
Documentation and ticket notes — 2. The rewrite kept the DNS step for users and left out what to have ready when calling.
Prioritization and escalation — 3. Took the sales outage first and acknowledged the others.
Weighted score: 3.25 ((4×25 + 3×20 + 4×15 + 3×15 + 2×15 + 3×10) ÷ 100). Recommendation: Yes. Strong method and security habits; documentation is the gap to coach, so put a knowledge base goal in the first month.
How do you adjust it for the seat and the level?
| Seat or level | Adjustment |
|---|---|
| Tier 1 service desk (phone and chat) | Raise user communication to 25% and documentation to 20%; keep technical knowledge to the basics the first-call scripts need. |
| Desktop or field support | Add hardware setup and asset handling to technical knowledge; if the job involves moving equipment or travel between sites, put it in the job description and ask every candidate the same essential-functions question. |
| Tier 2 or systems support | Raise technical knowledge and troubleshooting; add a short scripting or endpoint management exercise scored inside technical knowledge. |
| Managed service provider technician | Add switching between client environments and client-specific documentation; weight documentation at 20%. |
| Junior or career changer | Accept home lab, course or volunteer examples; score method and communication at full weight and accept smaller scope for a 3. |
| Team lead | Add a row on queue management and coaching; a 3 on prioritization needs examples of balancing a team's queue, not one person's. |
Mistakes specific to scoring IT support specialists
| Mistake | Why it fails | Fix |
|---|---|---|
| Points for certifications | An exam pass shows study, not how someone handles a stressed user or an odd lockout | Pass/fail line only if the job requires it; verify with the issuer |
| Scoring the fastest answer | Rewards guessing over method; on the job, guesses cost time on the next ticket | Score the questions asked and how the fix was confirmed |
| Treating "helpful" resets as good service | Help desk resets are a known attack route | Make verification a gate and score service above it |
| Scoring accent or "native English" | National origin is a protected basis under federal law (see the EEOC's prohibited practices page) | Score whether the user in the role-play understood and knew the next step |
| Asking about injuries or health for field work | Disability-related questions are not allowed before a conditional offer | Ask only whether they can perform the listed essential functions, with or without accommodation |
| Asking about family to judge on-call availability | Not job-related and invites a discrimination claim | State the rotation and ask every candidate whether they can meet it |
Where does this scorecard fit in the hiring process?
The IT support specialist phone screen places the candidate by tier and runs the on-call and schedule knockouts; for a pure first-line seat, the help desk technician screening questions fit. Keep the rows consistent with the must-haves in the IT support specialist job description template, verify any required certification as pass/fail (see how to verify CompTIA certifications and how to verify an ITIL certification), and carry the weakest row into the first month of the 30-60-90 day plan for IT support specialists.
If you hold the role-plays or the hiring manager interview on a video call with Interview Signal, the desktop app we make, these rows can become the scorecard areas in its kit, each with a weight of 1, 2 or 3 and rubric lines on a 1–10 scale; each score carries the candidate's own quotes, checked word for word against the transcript, and an area with no surviving quote is capped at 5 and marked "Probe further" (see how the scorecard with verified quotes works). The written rewrite is still scored by the person who reads it. Whatever you use, have each interviewer score before reading the others, then compare in a calibration session.
Questions people ask
What should an IT support specialist interview scorecard measure?
Six things for most support seats: troubleshooting method, communication with non-technical users, security and access judgment, technical knowledge of the environment, documentation and ticket notes, and prioritization with escalation. Weight them for the tier, and write what a 1, 3 and 5 sound like for each row before the first interview.
Should a CompTIA A+ certification add points on an IT support scorecard?
No. If the job description requires A+ or another certification, verify it with the issuer as a pass/fail line before scoring. The scored rows should measure how the candidate troubleshoots, talks to users and protects accounts, which an exam pass does not show on its own.
Is identity verification a scored row or a pass/fail gate for help desk hiring?
Both, in most loops. Resetting a password or moving multifactor authentication for a caller who has not been verified is a gate failure whatever the total, because attackers target help desks with exactly that request. Above the gate, score how well the candidate handles access more broadly: leavers, least privilege and reporting a suspicious call.
Can I ask an IT support candidate whether they can lift equipment?
You can ask every applicant whether they can perform the essential functions in the job description, such as moving equipment, with or without reasonable accommodation. Do not ask about injuries or medical history before a conditional offer, and score only the functions the job actually requires.