Cohesyve · Practice for candidates
Going for an IT Support Specialist role? Find out how you'd actually score.
Run an IT Support Specialist simulation built the same way employers build theirs, and get a full report showing exactly where you lost marks — before it counts.
3
free assessments
$0
no card required
Full
scored report every run
Every
question type included
3 free assessments · No card required · Pro from $16/mo
Overview
IT support assessments are built around real tickets. You are given a user problem described in the user's own words, sometimes with an error message or a screenshot, and asked how you would diagnose it and what you would say to the person reporting it. Both halves are scored, and the communication half is the one candidates underestimate. This page covers the formats and the marking.
Why employers assess this role
Support is one of the few technical roles where the quality of the interaction matters as much as the fix, and both are hard to assess in an interview where the candidate is describing themselves. Employers use practical exercises because a methodical troubleshooter who writes clearly is immediately visible in a ticket scenario and almost invisible on a CV.
What gets tested
The format
Duration
30–60 minutes
Question types
- Ticket scenarios with a diagnosis and response
- Prioritisation exercise across a queue
- Written user-facing communication
- Short knowledge base or documentation task
Levels
Entry · Mid · Senior
What you'll be asked to do
Diagnose a user-reported problem
A vague report and limited information. You are scored on the questions you ask, the order you check things in, and whether you isolate the fault rather than guessing at it.
- •A user cannot print, and printing worked yesterday
- •A laptop is slow only when connected to the office network
- •An application crashes for one user but not for their colleagues on the same team
Prioritise a queue
Several tickets arrive at once with different impact and different levels of urgency in the wording. Assessors look at whether business impact or tone of voice drives the ranking.
- •Order five tickets ranging from a single stuck password to a shared drive being unavailable
- •Decide what to do when a senior manager marks a minor issue as critical
- •Identify which two tickets are symptoms of the same underlying outage
Write to the user
A written reply to the person who raised the ticket. Marked on clarity, tone and whether the user knows what happens next without needing to ask.
- •Explain to a non-technical user why their file cannot be recovered
- •Ask for the information you need without making the user feel interrogated
- •Tell a user their request has to be escalated and what that means for them
Escalate and document
When to hand something on, and what the next person receives. Weak handovers are a common and easily detected failure.
- •Write the escalation note for an issue you cannot resolve at first line
- •Turn a resolved ticket into a knowledge base article for the next occurrence
- •Decide whether a suspected security issue should be escalated immediately
Cohesyve for candidates
Practise an IT Support Specialist assessment before the real one
Run the same AI job simulations companies use to evaluate applicants. You get a scored report showing where you're strong and where you're not, plus what to work on.
Sample tasks — and what strong looks like
A user writes: "My computer is not working." Respond.
EntryWhat strong looks like: Asks a small number of narrowing questions that quickly separate the possibilities — what exactly happens, when it started, whether anything changed, whether it affects one application or everything — while acknowledging the disruption. Weak answers either send a list of a dozen questions at once or start suggesting fixes before knowing what is broken.
Three tickets arrive together: one user cannot access a shared drive, a whole team cannot access the same drive, and a director cannot open one email attachment. Order them and justify it.
MidWhat strong looks like: Recognises that the first two are almost certainly the same incident and treats them as one, ranks by number of people blocked rather than seniority, and communicates the expected wait to the director rather than silently deprioritising them. Weak answers place the director first because of their title.
A user has permanently lost a document that was never backed up. Write the reply.
MidWhat strong looks like: Says clearly that the file cannot be recovered without hedging, avoids blaming the user, states what was checked so they know it was taken seriously, and offers the practical next step to prevent a repeat. Weak replies bury the bad news in technical detail or leave a false impression that recovery might still happen.
Several users across different teams report the same authentication failure within ten minutes. Decide what to do.
SeniorWhat strong looks like: Treats the pattern as a probable single incident rather than several independent tickets, escalates early with the correlation evidence attached, and communicates proactively to affected users instead of answering each ticket separately. Weak answers work the tickets individually and never notice they are related.
How to prepare
- #1
Practise writing narrowing questions that isolate a fault in as few exchanges as possible, because the number of round trips a candidate needs is directly visible to assessors.
- #2
Rewrite technical explanations for a non-technical reader until the jargon is gone, since tone and clarity carry a substantial share of the marks in these assessments.
- #3
Rehearse prioritising a queue by business impact so that seniority or urgent wording does not pull your ranking off course.
- #4
Write escalation notes for problems you have solved yourself and check whether someone picking one up cold would know exactly what has been tried.
- #5
Learn the common causes behind the recurring ticket types — printing, connectivity, account lockouts, slow machines — so that diagnosis starts from a short, ordered list rather than from nothing.
- #6
Do a full timed run including the written responses, because candidates frequently diagnose well and then leave the user-facing communication rushed or unfinished.
Common mistakes
Suggesting fixes before establishing what the actual symptom is.
Sending a long list of questions at once instead of a few that narrow the problem.
Prioritising by the seniority of the person reporting rather than by business impact.
Using technical vocabulary in a reply to a user who will not understand it.
Escalating with a one-line note that forces the next person to start from scratch.
Closing a ticket without confirming with the user that the problem is actually resolved.
How it's scored
| Criterion | What strong looks like |
|---|---|
| Troubleshooting method | Possibilities are eliminated in a sensible order, each question or check has a clear purpose, and the candidate can say what a given result would rule in or out. |
| Prioritisation | Ranking follows business impact and number of users affected, related tickets are recognised as one incident, and the reasoning is stated. |
| User communication | Plain language, an appropriate tone for the situation, and a reply that leaves the user knowing what is happening next without having to ask. |
| Escalation judgement | Escalation happens at the right point rather than too early or too late, and the handover contains the symptoms, the steps already taken and the results. |
| Documentation | Notes and articles are written so that a colleague can resolve the same issue next time without repeating the investigation. |
Frequently Asked Questions
How long do IT support assessments usually take?
Most run between thirty and sixty minutes and cover several short ticket scenarios rather than one long exercise. The pace is deliberate, since handling volume without dropping quality is part of the role.
Is the written communication section really scored?
Heavily. In many support assessments the user-facing reply carries as much weight as the diagnosis, because a correct fix explained badly still generates a follow-up ticket and a frustrated user.
What if I do not know the answer to a technical scenario?
Show the method anyway. Describing how you would narrow the problem down, what you would check first and where you would escalate scores well; guessing at a fix with no reasoning does not.
Do I need experience with a specific ticketing system?
Rarely. Assessments focus on triage, diagnosis and communication because ticketing platforms are learned in days, and where a particular system matters the employer normally says so in advance.
How do I practise before an assessment I have not seen?
Work through scored ticket scenarios rather than reading about troubleshooting. Cohesyve gives you three free assessments with a full report, so you can see how your diagnosis and your written replies are marked separately before it counts.
Practise another role
Cohesyve · Practice for candidates
Practise an IT Support Specialist assessment now — free.
Three free scored assessments, a full report on every run, and a learning pathway built from what you got wrong. No card required.
3
free assessments
$0
no card required
Full
scored report every run
Every
question type included
3 free assessments · No card required · Pro from $16/mo
For hiring teams
Hiring for an IT Support Specialist role? See how your applicants perform before you spend interview time.