Build the brief around the users and issues you support.
An IT support role changes with the environment. A single office with a small application set differs from a multi-site business with shared services, field users and several escalation teams. Explain who needs support, which devices and applications are involved and how requests arrive. Describe typical incidents alongside the more complex issues the person will encounter.
Clarify what first-line, second-line or desktop support means in your business. Specify which tasks the person can resolve, the access they will have and where issues go next. For site-based or shift work, include the location, travel between sites and coverage pattern. A realistic brief helps you assess technical competence, user communication and practical availability together.
Which profile does your team need?
The job title should reflect the responsibilities, seniority and contribution you expect. These are some of the appointments we can discuss within this area.
First-line service desk analysts
Second-line support specialists
Desktop support technicians
IT support administrators
Service desk team leaders
Technical support coordinators
Three decisions that sharpen the brief.
01
Describe the support queue
List typical request types, channels and user groups. Explain whether the role includes desk-side support, equipment setup or remote assistance. Useful examples tell candidates more than a broad requirement for excellent troubleshooting skills.
02
Define escalation and access
Identify the teams available for specialist help and the actions the new hire may perform independently. Include documentation expectations and how permission is obtained for sensitive changes. Assess candidates against those real responsibilities.
03
Plan coverage and handover
Set out shifts, site attendance and the process for transferring unresolved issues. If you are hiring several people, distinguish their levels and coverage needs. This helps avoid a shortlist of similar profiles for different gaps.
A MORE RELEVANT SHORTLIST
What matters in the search.
Support environment
Explore the systems, devices and ticketing tools the person has supported and the complexity of those requests.
Troubleshooting and escalation
Discuss how incidents are prioritised, documented and escalated when another team needs to help.
Communication with users
Consider clarity, patience and ownership when assisting people with different levels of technical understanding.
MAKE THE CONVERSATION COUNT
Assess the route to a resolution, not just the answer.
Present a familiar issue and ask the candidate to talk through their diagnosis. Look for sensible questions, basic checks, a safe approach to access and a clear record of what they have tried. Explore how they would decide whether the problem affects one person, a team or a wider service, and when escalation becomes appropriate.
Add a communication scenario involving a user who is frustrated or unfamiliar with technical language. Ask the candidate to explain the next step, an uncertainty or a delay. Clear ownership matters even when another team must resolve the fault. For team leaders, discuss workload allocation, coaching and the difference between a busy queue and a recurring service problem.
Ready to talk through the role?
Share your priorities, working arrangements and timing. We can discuss the brief and the recruitment approach with you.
Yes. We first clarify which issues the person will own, where they can escalate and the technical depth required.
Can you support hiring for a whole team?
Tell us the number of roles, shift coverage and start-date requirements. We can discuss an appropriate recruitment approach and delivery expectations.
Do you consider customer-service ability?
Yes. User communication and ticket ownership are important parts of the brief alongside technical experience.
How can we assess communication fairly?
Give candidates the same short user scenario and ask them to explain what they would say or write. Assess clarity, useful questions and ownership of the next step. Keep the exercise relevant to the users they will support, without treating a particular accent or presentation style as technical competence.
What information helps with a service desk team-leader search?
Share team size, shift coverage, reporting responsibilities and the balance between hands-on support and supervision. Explain whether the leader will coach analysts, manage escalations, improve knowledge articles or report on service performance. These details help distinguish a strong analyst from someone with the leadership experience required.
Recruitment across South Africa.
Epitome is based in Bryanston, Johannesburg. Tell us where your team works and whether the role is office-based, hybrid or remote so we can align the search with your requirements. Include regular site attendance, travel or collaboration hours when these affect the appointment.