Technical Support Agent CV Examples & Writing Guide

One page for an agent with about four years on a support desk, now working 2nd line tickets. The name and employers are invented. Notice how each bullet says what was fixed, at what volume, and what happened to the numbers. Support is one of the most heavily measured jobs there is, so a CV without measurements looks like it is hiding something.

Support hiring is about queue capacity and customer risk. Four things carry the screen.

• Volume and channel. Tickets or calls a day, and whether it was phone, chat, email or all three. Phone is a different skill from chat, and a manager staffing a phone queue will look for it specifically.
• What you could fix alone. First contact resolution and escalation rate say this in one number each. A 1st line agent who resolves 74% without escalating is worth more than one who routes everything upwards, and the CV is where you prove which one you are.
• The actual stack. Name the ticketing system, the operating systems, the identity provider and the tools. "Zendesk, Active Directory, Okta, Microsoft 365, Intune" is searchable and specific. "Troubleshooting software and hardware issues" is neither.
• Whether customers liked you. CSAT, quality score, or a survey number. Technical ability with a 71% CSAT is a coaching project; a 92% CSAT with a gap in networking knowledge is a training plan. Managers prefer the second.

“Give me tickets a day, first contact resolution and your CSAT, and I know exactly where to slot you. What I usually get instead is "provided excellent customer service and resolved technical issues". Every applicant writes that. Nobody writes "36 tickets a day, 74% first contact resolution, 6% escalation rate", and that person gets the call.”

Three or four lines: line (1st or 2nd) and channel, daily volume, one quality number, and your certification. A career objective belongs here only if this is your first support job.

The weak versions describe the job. The strong ones describe your queue.

Name products and protocols, not categories. Then be honest about depth, because you will be asked to troubleshoot something live in the interview.

• Ticketing and service management: Zendesk, Freshdesk, ServiceNow, Jira Service Management, Salesforce Service Cloud, Intercom. Say which one and roughly how long.
• Operating systems and devices: Windows 10 and 11, macOS, iOS, Android, ChromeOS, plus printers, docking stations, peripherals and imaging or reimaging.
• Identity and productivity: Active Directory, Entra ID, Okta, Google Workspace admin, Microsoft 365 admin centre, Exchange Online, Teams, Intune or another mobile device management tool.
• Networking to the depth a support desk needs: TCP/IP, DNS, DHCP, VPN clients, Wi-Fi channels and interference, ping and traceroute, reading a router's status page, basic firewall rules.
• Application and web troubleshooting: browser console errors, HAR files, cache and cookie issues, extensions, certificate warnings, reading application logs, REST API basics and Postman.
• Remote support tools: Windows Quick Assist, TeamViewer, AnyDesk, BeyondTrust, Splashtop, and the etiquette of taking control of somebody's machine.
• Scripting and automation, if you have it: PowerShell, Bash, or even a set of saved SQL queries. This is what separates a 2nd line agent from a 1st line one on paper.
• Queue and process skills: SLA management, triage and prioritisation, backlog control, escalation criteria, incident communication during an outage, knowledge base maintenance, and UK GDPR-safe identity checks before you touch an account.
• The customer side: explaining a technical cause in plain words, staying calm with an angry caller, saying "not sure yet, here is the next thing to check", and closing a ticket in a way the customer understands.

None of these are required, and most support desks hire on aptitude. They matter most when you have no support experience yet, or when you are trying to move from 1st line to 2nd line or into systems work.

Support is one of the most common ways into IT, and desks hire people with no ticket history every month. What they screen for is troubleshooting method, patience on the phone, and whether you have taught yourself anything.

1. 1Lead with a certification if you have one, or one you have booked. CompTIA A+ or the Google IT Support certificate both signal that the interest is real.
2. 2Describe your home lab or your own projects properly. A Windows Server virtual machine, a home network you segmented, a Raspberry Pi running something, a family member's PC you rebuilt, a NAS you set up. Say what broke and how you diagnosed it, because that is the actual job.
3. 3Turn any customer-facing job into evidence. Retail, hospitality, reception, call centre, teaching. Give the volume: customers a shift, calls a day, complaints resolved. Support managers hire heavily from retail because the hard part of the job is people.
4. 4Use any technical thing you did in a non-technical job. Being the person who fixed the shop's till system, set up the tablets, or handled the printer everyone else gave up on all count. Write them as bullets with numbers.
5. 5Say which shifts you can work. Support desks run evenings, nights and weekends, and availability is a real tiebreaker for entry-level roles.
6. 6Practise describing a troubleshooting process out loud before the interview. Almost every entry-level support interview asks how you would approach a problem you have not seen, and they are listening for a method, not an answer.

• One page. Support hiring moves fast and volumes are high.
• Order: name with line and specialism, contact details plus shift availability, personal statement with two numbers, experience, technical skills, certifications, education.
• Single column, no tables, no skill rating bars, no photo or date of birth. Support teams often sit inside larger companies whose applicant tracking systems handle graphics badly.
• Mirror the advert: "1st line", "2nd line", "ticketing", "SLA", "first contact resolution", "escalation", "CSAT", "Active Directory", "Microsoft 365", "remote desktop", "incident", "knowledge base", and the exact tool names.
• Put the numbers in the personal statement. A manager scanning 80 applications will not find your CSAT in bullet four.
• Say your shift availability. Evening, overnight and weekend cover is what most desks are short of.
• PDF unless the portal asks otherwise.

One more thing worth writing down: the path out. Support is where a lot of IT careers start, and managers like candidates who know where they are heading. A line about studying for Network+ or moving towards systems administration reads as ambition, not as a warning that you will leave, as long as your ticket numbers show you are doing the current job well.