How to move from first line to second line IT support
Second line support takes the tickets first line cannot close: deeper faults on servers, accounts and the network, with fewer scripts to follow and the ticket yours until it is fixed. The way up is to start doing a small part of that work while you are still on first line, keep a record of it, and then ask for the job.
A common route from first line to second line support is doing a slice of second line work before anyone gives you the title: taking a ticket one step further before escalating it, learning enough PowerShell to read a log, writing up the fix so the next person does not need to escalate at all. Second line is where tickets go when first line's scripts run out, and third line is the specialists behind them. Whether you apply inside your organisation or outside it, the strongest case you can make is evidence that you already think like the person who receives the escalation rather than the person who sends it.
First, second and third line in plain terms
There is no official definition of the "lines", and every organisation draws them slightly differently. What is consistent is the idea behind them. The SFIA framework's description of incident management notes that different groups may be needed to diagnose and resolve incidents, naming service desk staff, support teams, subject matter experts, suppliers and partners among them. The lines are just the order in which a ticket meets those groups.
First line is the service desk. The National Careers Service profile for IT support technicians describes the work: responding to requests for help, recording each issue in a tracking system, and finding and fixing faults or assigning them to the correct team. Password resets, known printer faults, setting up accounts from a template and anything with a written procedure tend to stay here.
Second line takes what first line could not close. That usually means work on servers rather than on one person's laptop, changes in Active Directory or Microsoft Entra ID that need admin rights, network faults that affect more than one desk, and investigations where nobody has written the answer down yet.
Third line is the people who build and own the systems: the network engineers, the identity team, the cloud platform team, or the vendor's own support. A ticket reaches them when the fault is in the design or the product itself, not in how it was set up for one user.
What actually changes in the work
The obvious change is technical depth. The bigger one is ownership. On first line, the measure of a good shift is often how many tickets you handled. On second line, a ticket is yours until it is fixed, which might take a morning of reading logs, a call with a supplier and a change that has to wait for an approved window.
You also start working on both sides of a distinction that ITIL makes. PeopleCert, which runs the ITIL certifications, describes incident management as restoring normal service quickly after a disruption, and problem management as identifying and managing the root causes of incidents to prevent them happening again, including managing workarounds and known errors. SFIA's incident management skill puts the priority bluntly: restore service to users as quickly as possible, putting service continuity ahead of permanent solutions.
First line mostly lives in the incident. Second line is where someone notices that the same account has locked out every Monday for a month and asks why. You do not need to sit an ITIL exam to work like that, but knowing the words helps in interviews and in conversations with the people who run the service desk.
There are fewer scripts, too. Second line engineers follow procedures for changes and for anything risky, but much of the diagnosis is your own judgement. That is the part that makes the job interesting, and it is the part you most need to show you can be trusted with.
Skills to build while you are still on first line
You do not need to master any of these before applying. You need to have started, and to be able to talk about what you did with each.
PowerShell, read-only at first
Microsoft describes PowerShell as a task automation solution made up of a command-line shell, a scripting language and a configuration management framework, and notes that it passes .NET objects rather than plain text between commands. On second line it is how you answer questions about many users or machines at once.
Start with commands that only read. KBY's script library holds short, read-only scripts that each answer one question, such as which accounts were locked out and from which computer. Read each line until you can explain what it does. Running something you cannot explain is the habit to avoid, especially once you have admin rights. The PowerShell page has more background.
Active Directory and Entra ID
Microsoft's overview of Active Directory Domain Services explains that it stores information about objects on the network, such as user and computer accounts, servers and printers, and replicates that information between all the domain controllers in a domain. Microsoft Entra ID is the cloud identity and access management service behind Microsoft 365 and Azure; every Microsoft 365 tenant is also an Entra tenant.
Many organisations run both side by side, and accounts, groups and sign-ins are everyday second line work, so learn how the two fit together. KBY's Identity and Access Management lessons work through real Entra ID sign-in errors, and the runbook on Kerberos logons failing because of clock skew is a good example of how an on-premises fault is diagnosed step by step.
Networking basics
You need to be comfortable with IP addressing, DNS and DHCP, and with the order you check things in when "the internet is down" for one floor. CompTIA's Network+ covers IP addressing, ports and protocols, monitoring and troubleshooting, and lists CompTIA A+ plus 9 to 12 months of hands-on experience in a junior network administrator or network support role as its recommended background, so treat it as a target once you have some network tickets behind you. KBY's Enterprise Networking Fundamentals lessons and the CIDR planner are useful practice.
Reading logs
Much of second line diagnosis is reading what a system has already recorded. On Windows, Get-WinEvent reads the event logs, including the System and Application logs, and can filter them by log name, event ID and time. A concrete exercise: account lockouts are recorded as event 4740, which includes a Caller Computer Name field naming the computer the failed sign-in came from. Next time a user is locked out repeatedly, finding that computer is a second line answer you can give from first line. Microsoft notes that without administrator rights you may not be able to read some logs, so if you lack that access, ask a second line engineer to show you where they look.
Writing knowledge base articles
Keeping the knowledge base up to date is already on the National Careers Service list of first line tasks. Treat it as a skill, not a chore. A good article states the symptom in the user's words, the cause, the fix, how to check it worked and when to escalate instead. If you write one for a fault that used to go to second line, you have shown exactly the judgement a second line role needs. KBY's lesson on publishing a knowledge base article safely covers drafting, review and approval.
Getting exposure without overstepping
The aim is to see second line work up close without doing anything you are not authorised to do.
- Follow your escalations. When you pass a ticket on, read the resolution notes when it closes. Ask the engineer what they checked first if the notes do not say.
- Ask to shadow. An hour sitting with a second line engineer during a real fault shows you the order they check things in, which no course can. Ask for a time when the service desk is covered, so the answer is easier to give.
- Take one step further before escalating. Gather the logs, the error message, the time it started and what you already ruled out. A well-prepared escalation is the most visible evidence that you are ready.
- Volunteer for project work. Laptop refreshes, office moves, migrations and new starter process changes all need extra hands, and they put you alongside second and third line engineers.
- Ask for access in stages. Read-only access to a console or a reporting role is an easier yes than full admin rights, and it lets you learn the systems properly.
Keep a record of what you did
Start a simple log now and add to it every week. For each entry, note the ticket or project reference, what was wrong, what you did yourself and what changed as a result. Include the knowledge base articles you wrote, any script you adapted and any repeat fault you spotted and reported. If your ticketing system can show that a fault stopped coming in after your article went live, note the numbers it gives you; do not estimate.
This record is what you will draw on for an internal application, a CV and interview answers. It also makes the next conversation about pay or promotion much easier, which is covered in making the case for a promotion or a pay rise.
Applying, inside or outside
An internal move
Tell your manager you want to move to second line before a vacancy appears, and ask what they would need to see. Then come back in a few months with your record. If your organisation uses the SFIA levels of responsibility, they give you shared language: SFIA describes level 2 as assisting others and using discretion on routine problems, and level 3 as performing varied tasks, sometimes complex and non-routine, under general direction and managing your own work within deadlines. That shift is a fair description of the move from first to second line.
An external move
Second line roles are advertised under several titles, including second line support engineer, 2nd line support analyst, IT support engineer, desktop support engineer and infrastructure support analyst. Include managed service providers in your search: they support many customers at once, so you see a wide range of systems and faults.
A certification can help an external CV get past filters. For Microsoft-heavy environments, the Endpoint Administrator Associate certification (exam MD-102) covers managing devices with Intune, Windows Autopilot, Entra ID and PowerShell, and expects experience with Entra ID and Intune, so it suits someone who has already done some of the work. KBY's certification paths show where it leads. Prepare for technical interviews with the systems administrator interview questions, many of which come up for second line roles too.
On pay, the National Careers Service does not publish a separate figure for second line support. Its IT support technician profile gives an average salary of £24,000 for a starter and £36,000 for someone experienced. Use the adverts for the roles you are applying for to see what each employer is offering.
After second line
The National Careers Service lists senior IT support technician among the next steps from support with experience, and network engineer, database administrator, systems analyst and IT security co-ordinator with further training. Second line is often where people find out which of those they enjoy, because it is the first job where you see the systems behind the tickets. When you are ready to decide, choosing an IT specialism compares the main directions.
Courses and practice tests
Partner links- Pluralsight · PaidPluralsightVideo courses and labs on PowerShell, Active Directory and networking, the skills this guide suggests building while you are on first line.Check partner offer
- MeasureUp · PaidMeasureUp practice testsPractice tests for Microsoft exams such as MD-102, if a certificate is part of your case for moving up.Check partner offer
Partner links are sponsored: KBY may receive a commission at no extra cost to you. Whether a provider pays KBY does not decide what we recommend, and the free official material comes first. Advertising disclosure.
Common questions
- How long should I spend on first line before moving to second line?
- There is no fixed time. What matters is whether you can show second line work you have already done: escalations you took further, knowledge base articles, scripts you can explain and faults you diagnosed. Start collecting that evidence from your first month.
- What is the difference between an incident and a problem?
- In ITIL terms, incident management is about restoring normal service quickly after a disruption, and problem management is about finding and managing the root causes of incidents so they stop happening. Second line engineers usually work on both.
- Do I need a certification to get a second line job?
- Not always. Internal moves usually depend on your record and your manager's support. For external applications, one relevant certification, such as Network+ or Microsoft's Endpoint Administrator Associate, can help a CV get past filters.
Sources
Every figure and rule in this guide comes from these pages, read on 17 November 2026. Pay rates, exams and schemes change: check the source before you rely on one.
- IT support technician: job profile (National Careers Service)
- ITIL 4 Practitioner: Incident Management (PeopleCert)
- ITIL 4 Practitioner: Problem Management (PeopleCert)
- Incident management (SFIA Foundation)
- Levels of responsibility (SFIA Foundation)
- What is PowerShell? (Microsoft)
- Active Directory Domain Services overview (Microsoft)
- What is Microsoft Entra? (Microsoft)
- Get-WinEvent (Microsoft)
- 4740(S): A user account was locked out (Microsoft)
- Network+ certification (CompTIA)
- Microsoft 365 Certified: Endpoint Administrator Associate (Microsoft)
Spotted something wrong or out of date? Tell us and we will correct it.