Interview questions · IT Technician

IT Technician interview questions

Recruiters look for IT Technicians who combine solid technical troubleshooting skills with clear communication—someone who can diagnose hardware and software issues quickly and explain solutions to non-technical users without condescension. They want evidence of systematic problem-solving, documentation discipline, and the ability to manage a high-volume ticket queue without dropping service quality. Candidates who show ownership of incidents from first contact to resolution stand out.

Walk me through your process for troubleshooting a workstation that powers on but shows no display.

A classic diagnostic scenario that reveals whether the candidate thinks systematically rather than randomly swapping components.

Model answerI start by confirming the monitor and cable are working using a known-good machine, then check that the GPU is fully seated. If integrated graphics are available I switch to those to isolate the GPU. I then test RAM sticks one at a time and check for POST beep codes. In a recent case this process identified a loose RAM stick in under 12 minutes, avoiding an unnecessary board replacement.

Describe a situation where you resolved a recurring ticket that no one else had been able to permanently fix.

Recruiters want problem-solvers who dig for root causes, not just quick fixes.

Model answerA finance team member logged the same 'network share disconnects' ticket weekly for three months. Previous fixes were reconnecting the drive—a symptom, not a cause. I reviewed event logs and found that her machine's NIC driver was mishandling power management in sleep mode. Updating the driver and disabling selective NIC sleep resolved the issue permanently; the ticket never reappeared in the eight months before I left.

How do you handle a situation where a frustrated user is blaming IT for a business-critical system being down?

Soft skills under pressure are as important as technical skills for user-facing technicians.

Model answerI acknowledge the business impact first—'I understand this is affecting your ability to close orders, let's fix that now'—before I start diagnostics. I keep the user informed every 10 minutes with a brief status update even if I have nothing resolved yet. In one case a CRM outage was a vendor-side issue; I set up a simple Excel workaround in 20 minutes so the team could keep working while I liaised with the vendor, turning a frustrated stakeholder into an advocate.

How do you prioritise a queue of 30 open tickets when everything feels urgent?

Workload management and triage judgment are critical in busy IT teams.

Model answerI apply a simple impact-urgency matrix: a full department blocked on a core system takes priority over a single user with a cosmetic issue. I communicate realistic ETAs to all users so expectations are set, and I batch similar tickets—if five users have the same VPN error, one fix often closes all five. Using this approach I consistently cleared 90% of tickets within SLA in a team with a weekly average intake of 120 tickets.

Tell me about an experience you have had deploying or migrating workstations at scale.

Larger organisations need technicians who have managed rollouts, not just one-off fixes.

Model answerI participated in a 200-machine Windows 11 migration over six weeks. I built and tested the base image, used MDT for automated deployment, and handled user data migration via USMT with a per-user validation checklist. We completed 34 machines per week with zero data-loss incidents and a helpdesk call rate of under 5% post-migration, well below the 15% we had budgeted for.

How do you ensure that your technical documentation is actually used by other team members?

Documentation quality and adoption are often weak spots; recruiters want organised, collaborative technicians.

Model answerI write documentation at the moment I resolve an unusual issue, while the steps are fresh, and I include screenshots and a 'common mistake' note at the end. I then share it in our team channel and link it from the original ticket. In my last role I contributed 40 articles to our internal knowledge base over 18 months; ticket recurrence for documented issues dropped by 30%.

Describe how you have handled a security incident such as a suspected phishing compromise or malware infection.

Security awareness is now a baseline expectation for IT technicians.

Model answerA user reported clicking a phishing link and entering credentials. I immediately isolated the machine from the network, forced a password reset on all her accounts, and reviewed Azure AD sign-in logs for anomalous activity. Finding a suspicious login from an Eastern European IP, I revoked all active sessions and briefed the IT manager within 20 minutes. The incident was contained with no data exfiltration confirmed, and I documented the full timeline for the incident report.

What steps do you take when onboarding a new employee to ensure their setup is complete and they feel supported from day one?

Onboarding quality reflects on IT and directly affects new-hire productivity and satisfaction.

Model answerI prepare a standard new-hire checklist that covers hardware, software licensing, email and Teams access, VPN credentials, and printing—verified 48 hours in advance. On their first morning I spend 15 minutes with the new hire walking through the setup and answering questions, and I send a follow-up message at day three to catch anything that slipped through. In our engagement survey IT onboarding scored 4.6 out of 5, the highest-rated onboarding touchpoint.

Tips for this role

Practise for THIS role

Paste your job offer, pick a recruiter, and run a mock interview with a detailed coaching report.

🎤 Start an interview

Everything you can do