Skip to main content
Careers · Getting ahead

What changes when a senior engineer becomes a team lead

A team lead gets work done through other people: priorities, one-to-ones, hiring, absence and protecting the team's time, while answering for results they did not personally deliver. The specialist or architect route reaches the same level of responsibility without line management. Try the parts of both you can before you choose.

9 min read Sources checked 17 November 2026 UK

Employment guidance here is from Acas, which advises employers and employees in England, Scotland and Wales.

A team lead's job is getting work done through other people. You stop being judged on the problems you solve and start being judged on what the team delivers, and the week fills up with priorities, one-to-ones, hiring, absence, the occasional hard conversation and keeping the team's time from being eaten by everyone else's requests. If the part of your current job you would miss most is the hardest technical work, there is a second route that goes just as far: the specialist or architect track, where you lead through expertise rather than line management. Most of both can be tried before you commit, and that is the best way to decide.

Two routes from the same level

The Skills Framework for the Information Age (SFIA) is a framework organisations and professional bodies use to map IT roles and career paths. It describes seven levels of responsibility, and reading two of them side by side shows what the move to lead involves.

At level 4, Enable, someone performs diverse, complex work, supports and guides others, delegates when appropriate and, when required, plans, schedules and delegates work, typically within their own team. Many strong senior engineers will recognise themselves there. At level 5, Ensure, advise, they are accountable for delivering significant work outcomes "from analysis through execution to evaluation", work under broad direction, and define tasks and delegate work to teams and individuals in their area.

What matters for this decision is that SFIA describes skills separately from levels. Performance management, the skill of developing people and workgroups to meet agreed objectives, is defined at levels 4, 5 and 6. So is solution architecture. A manager and an architect can reach the same level of responsibility. They get there through different skills.

What a lead's week is made of

SFIA's description of performance management at level 5 reads like a team lead's job description: delegating objectives and responsibilities, including people management tasks; setting quality, performance and capability targets; monitoring performance and working relationships and giving feedback; adjusting workload and team capacity; and taking part in recruitment, reward, promotion and disciplinary procedures.

One-to-ones and objectives

Acas's guidance on performance reviews says that alongside formal reviews, which it suggests holding at least once a year, managers should talk to people about their performance informally and regularly: through feedback, coaching and regular check-ins, "sometimes known as one-to-ones". It asks for a written record of what a review covers, shared with the employee afterwards, and objectives that are fair, reflect the person's usual work and can stretch them. It suggests making them SMART: specific, measurable, achievable, relevant and time-bound.

Treat the one-to-one as the other person's meeting. Status belongs in the ticket system. The half hour is for what is blocking them, what they want to learn and how the work is going for them. When the week is busy it is the easiest meeting to cancel, and cancelling it tells the person where they rank.

Absence, performance and hard conversations

The Acas guide to challenging conversations is written for line managers. It says most problems to do with performance, conduct, absence or personal issues are the line manager's to deal with, although sometimes a more senior manager or HR will talk to the employee first. It advises a quiet word at the first sign that something is wrong rather than waiting, and preparation before the conversation: establish the facts, think about what you know about the person, get support, check your policies and plan the meeting.

When someone performs below what the job needs, Acas's advice on performance problems starts with trying to understand why. It separates capability, whether someone can do the job, from conduct, how they behave, because they are handled differently. A capability problem calls first for support such as coaching, mentoring or training. If you have spent years diagnosing systems, the habit is the right one: find the cause before deciding what to do, with a great deal more care than you would give a server.

When someone comes back after time off, Acas says a return to work meeting is not a legal requirement but is a good chance to check they are ready, tell them what changed while they were away, see what support they need and agree what they would like colleagues to know. It also asks managers to look out for underlying causes such as work-related stress or a disability.

Read your organisation's absence, capability and disciplinary policies in your first week as a lead, before you need any of them.

Hiring

Interviewing changes from something you help with to something you are responsible for. Acas's guidance on interviewing job applicants says to prepare a set of questions, to have more than one interviewer where possible to reduce the risk of discriminating, and to ask each applicant the same questions where possible. By law, you must ask anyone coming to an interview to tell you if they need reasonable adjustments. The decision should rest on how each applicant met each point in the job description and person specification. For a technical role, the engineer in you will want to design a clever exercise. The lead has to make sure it tests what the job needs, the same way for everyone.

Protecting the team's time

Requests arrive from everywhere: project managers, other teams, senior managers and users who know someone's mobile number. Part of the lead's job is to be the one place they land, to agree with your own manager which matter most, and to say plainly which will wait. SFIA expects someone at level 4 to escalate "when scope is impacted" and someone at level 5 to raise issues "when objectives are at risk". A lead who says yes to everything has not removed the overload. They have handed it to the team.

Answering for work you did not do

This is the change people find hardest. When a change your team made causes an outage, you explain it to the service owner, whether or not you were on the call. When the team ships something good, the credit is theirs. The pull is to take the hardest tickets yourself, because it feels productive and keeps you current. It also leaves the work only you can do undone, and stops anyone else learning the difficult parts. Keep some technical work, but keep it off the critical path.

The specialist and architect route

Leading without line management is a real career, not a consolation prize. The National Careers Service describes a solutions architect as someone who designs technical blueprints for new digital products and services and solves existing IT problems: understanding what clients need, proposing solutions, assessing the strengths, weaknesses and costs of the options and presenting recommendations. With experience, it says, you could become a senior or lead solutions architect and then an enterprise architect, developing overall IT strategy for the business. It puts the average salary at £36,000 for a starter and £85,000 for someone experienced.

Its technical architect profile (also called IT systems architect) gives £42,000 and £90,000. The tasks include acting as a link between technical teams and project delivery managers and advising senior managers on future IT needs, and the profile says employers want strengths in non-technical areas such as client management, communication and leadership.

So the specialist route is not a way to avoid people. It swaps managing people for influencing decisions: you persuade other teams, write the design everyone works from and explain to managers why one option is safer than another.

For comparison, the IT project manager profile, the nearest one on the management side, lists assessing tasks and risks, allocating work, managing budget and timescales, reporting on progress and leading and motivating the team, at £35,000 for a starter and £60,000 experienced. None of these profiles is "team lead", so treat the figures as a guide to the two directions rather than a pay scale for your employer.

If your organisation has a senior technical grade that does not manage people, ask how high it goes. Where the career framework is mapped to SFIA, the levels show whether the technical path reaches as far as the management one.

Try it before you commit

Most of a lead's work can be tried while you are still a senior engineer. Ask your manager for one or two of these and give each a few months:

  1. Lead a small project. Assessing tasks and risks, allocating work, reporting progress and dealing with changes or delays are the project manager tasks above, on a scale you can handle alongside your own work.
  2. Mentor a newer engineer. SFIA's performance management skill at level 4 includes coaching colleagues in the skills they are working towards. Regular sessions show you whether someone else's progress gives you the satisfaction a fix does.
  3. Run an incident call instead of the fix. Keep the record, assign the work, update the people waiting, and let someone else type. KBY's Daily Triage exercises are a low-stakes way to practise reasoning through an incident first.
  4. Sit on an interview panel, and help write the questions.
  5. Represent the team at a planning or prioritisation meeting and come back with a decision.

The architect route has its own trial: write the design for the next significant change, present the options with their costs to someone non-technical who has to choose, and review other people's designs.

Afterwards, be honest about which of these you looked forward to and which you put off.

How to decide

These questions help more than a list of pros and cons:

  • Would you be content if a quarter went by without you shipping anything yourself?
  • Does half an hour helping someone with their career feel as worthwhile as half an hour of debugging?
  • When an incident starts, do you want the keyboard or the call?
  • Are you considering management because you want it, or because it is the only promotion on offer?

If the honest answer to the last one is the second, raise it with your manager before you apply. A lead who did not want the job is hard on a team. Leading is also not a one-way door. If you go back to a technical role after a spell of it, you take with you a working knowledge of how priorities are set and people are managed, which helps in any senior job.

Making the move

Inside your organisation

Ask what the lead role is measured on where you work, and whether an acting or trial period is possible. Collect evidence from the trials above: the project you ran, the person you mentored, the incident you coordinated. If your employer uses SFIA, describe that evidence in the language of the level you are aiming for. KBY's guide to promotion and pay rises in IT covers how to make the case.

Applying elsewhere

Look under team lead, IT manager, infrastructure manager, service delivery manager and engineering manager, and read each advert for how much hands-on work it expects. Expect interview questions about times you led without authority, handled disagreement, prioritised competing requests and dealt with someone who was struggling. The STAR method helps you answer those with real examples rather than opinions.

The first three months

Keep the one-to-ones, even when the week is on fire. Read the people policies. Learn the formal parts with help rather than alone: Acas offers free e-learning on performance management and training on having difficult conversations. And keep working on the skills that made you good at the job you are leaving, because the team will still bring you their hardest problems. The skills around them, writing, explaining risk and running incidents, are covered in IT skills beyond the technical.

Common questions

Does the architect route pay less than management?
The National Careers Service profiles do not suggest so. They give £36,000 to £85,000 for a solutions architect, £42,000 to £90,000 for a technical architect and £35,000 to £60,000 for an IT project manager, from starter to experienced. Your employer's own grades matter more than any average.
What SFIA level is a team lead?
SFIA describes levels, not job titles, and each organisation maps its own roles to them. Guiding team members and delegating within your own team appear at level 4; accountability for significant outcomes, and people management tasks such as recruitment and disciplinary procedures, appear at level 5.
Can I go back to engineering if I do not like managing?
Yes, if a technical role is open to you, and it is a reasonable move rather than a failure. Trying the parts of the job first, by leading a project or running incident calls, makes it less likely you will need to.

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.

Spotted something wrong or out of date? Tell us and we will correct it.

All careers guides