UK

United Kingdom · Technology and data · Mid-Level (2-5 years of management experience, 8-10 years total)

Engineering Manager

Here is the whole job, in plain words. What it is, what you decide, how you're judged, how people get here and where they go next. Then the part no course gives you: twelve AI tutors who learn your work.

Start my Engineering Manager plan, free

Free to start: a plan built for this role, and a Future Fluency module to try first. No card.

Keep this job description

Where should we send it?

One email: what AI is changing in this job, and where to start free. With a link back here. Nothing else follows unless you confirm your address.

Also at another level: the Lead Engineering Manager job description.

Upskilling a team in this role? Talk to us

  • Experience bandMid-Level (2-5 years of management experience, 8-10 years total)
  • Direct reports5-8 reports
  • Reports toSenior Engineering Manager or Director of Engineering
  • UK framework levelUsually a professional owning their own work, or leading a small team

Also advertised as Software Engineering Manager · Development Manager · Team Lead (Engineering, post-coding)

Built on 43,079 real UK job descriptions we analysed · grounded in qualifications employers recognise

Two short quizzes about you

1From this job to a course

The qualifications matched to this job

EAL Level 2 Certificate In Engineering Technologies Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 8 standards
EAL Level 2 Diploma In Engineering Technologies Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 8 standards
EAL Level 2 Certificate in Engineering Operations (Knowledge) Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 8 standards
EAL Level 2 First Certificate in Engineering Technology Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 8 standards
EAL Level 2 Diploma in Engineering Operations (Knowledge) Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 8 standards
EAL Level 2 First Diploma in Engineering Technology Excellence, Achievement & Learning Limited · Level 2 · covers 1 of 8 standards

Matched from the standards this job is measured against: a suggestion, not an official ruling.

The units you would start with

Leading a team in Engineering EAL Level 2 Certificate In Engineering Technologies

The future skills this job leans on

AI Fluency working with AI as a thinking partner
Data Fluency turning numbers into a decision
AI Governance Fluency using AI responsibly
Automation Fluency building AI into how work runs
Systems Fluency seeing the whole picture
Start my Engineering Manager plan, free

2AI and this work

Will AI change your work as an Engineering Manager?

Nobody can say exactly how. Here is what this job is being asked for next, and where to start.

The new skills this role is being asked for

  • AI-Powered Team Insights & Coaching
  • Advanced Prompt Engineering for Management Tasks
Why each one is rising

The future skills this job leans on

We'll only ever tell you what we can actually back up. No hype, no scare tactics.

What happens when you start

Next, a free account. We build your Engineering Manager plan as you set up, starting with a Future Fluency module on using AI in your job. No card.

Your first Future Fluency module is free. After that, your AI tutor is £70 a month.

Start my Engineering Manager plan, free Ready to pay? Subscribe for £70 a month

3What this role really is

An engineering manager leads a single engineering team, making sure engineers can do good work and ship quality code. The role involves little hands on coding. Instead, it means supporting others to do their best work and guiding how the team operates.

4What you'd actually use

The tools this job runs on, and how well you'd need to know each one.

Jira (or similar Project Management tool) Advanced

Managing team backlogs, creating complex JQL queries to track progress, configuring sprint boards, and analysing velocity/burndown charts to understand team performance and predict delivery.

GitHub (or similar Code & CI/CD platform) Advanced

Enforcing PR/merge strategies, reviewing complex pull requests for logic and style (not just code), managing branch permissions, and troubleshooting basic GitHub Actions failures to keep the pipeline flowing.

AWS (or similar Cloud Platform) Intermediate

Understanding core services (EC2, S3, RDS, Lambda) relevant to your team. Navigating the console to check resource status, reviewing basic CloudWatch logs/metrics for your team's services, and understanding cost implications of architectural choices.

Datadog (or similar Observability platform) Advanced

Building team-specific dashboards, setting up monitors and alerts for key Service Level Objectives (SLOs), and using APM traces to identify performance bottlenecks in your team's services during incidents or performance reviews.

Confluence/Notion (or similar Collaboration/Documentation tool) Advanced

Maintaining team documentation, writing clear technical design documents, creating project hubs for cross-functional teams, and ensuring knowledge is shared effectively.

Workday HCM (or similar HRIS) Intermediate

Approving time off requests, initiating compensation changes (e.g., raises, bonuses), and accessing basic team data for reporting or planning purposes.

5What you get to decide, and how that grows

Power in a job isn't your title. It's what you're allowed to decide. Here's how it grows as you move up.

The choiceComing in Where you are nowThe step above
Team Sprint Commitments & Scope Under guidance, execute tasks defined by others. Full authority to commit to sprint scope, negotiate with Product on feature prioritisation, and adjust within sprint if needed. Defines multi-sprint roadmaps, negotiates program-level scope with Product leadership, and allocates resources across multiple teams.
Technical Approach & Architecture (Team-level) Follows established technical patterns and seeks approval for deviations. Decides on technical approaches, tools, and libraries for their team's services, within broader architectural guidelines. Leads team-level design reviews. Defines architectural patterns for a group of teams, leads cross-team architectural decisions, and influences broader engineering strategy.
Performance Management & Career Development Provides feedback to peers, participates in code reviews. Conducts 1:1s, writes performance reviews, creates and monitors Individual Development Plans (IDPs), and makes recommendations for promotions. Oversees performance management across multiple teams, mentors other managers on people development, and contributes to career ladder design.
Budget Allocation (Team Tools/Training) Requests specific tools or training, requires approval. Recommends budget for team-specific tools, training, and conferences up to £10K, requiring manager approval. Manages team's cloud spend within allocated budget. Manages budget for multiple teams or a significant product area (up to £500K), makes vendor decisions, and influences overall engineering budget.
Hiring & Firing Participates in interview loops as an interviewer. Leads interview loops, makes hiring recommendations, and contributes to offer decisions. Initiates performance improvement plans (PIPs) with HR and manager oversight. Owns hiring strategy for a group of teams, makes final offer decisions, and manages involuntary attrition with HR partnership.

6How you'll be judged

The scoreboard, and what is not on it. The hard targets, how often each is actually looked at, and the quiet signals that never reach a dashboard.

Team Delivery Predictability (Say/Do Ratio)
How accurately your team estimates and delivers on sprint commitments.
Target · Consistently above 85%

If your team commits to 10 stories in a sprint and completes 9, that's a 90% say/do ratio. We track this to ensure we're getting better at estimating and managing scope.

Mean Time to Recovery (MTTR) for Team's Services
The average time it takes for your team to restore service after an incident in their owned systems.
Target · Under 1 hour for critical incidents (Sev-1/Sev-2)

After a database connection issue caused a Sev-1 outage, your team identified and resolved it in 45 minutes, bringing down the average MTTR for the month.

Engineer Retention Rate
The percentage of engineers on your team who remain with us over a given period.
Target · Consistently above 90% annually

If you start the year with 7 engineers and retain 6, that's an 85.7% retention rate. We want to see people happy and growing, not looking for the exit.

DORA Metrics (Change Failure Rate)
The percentage of changes to production that result in degraded service or require rollback.
Target · Below 15%

Out of 20 deployments last month, 2 caused a production issue that needed a hotfix or rollback, resulting in a 10% change failure rate. We want this low, obviously.

Team Health & Morale
How engaged, motivated, and supported your engineers feel, and how well they collaborate.
  • High participation in team activities
  • open and honest feedback in 1:1s
  • engineers actively helping each other
  • positive sentiment in internal surveys
  • low levels of 'bike-shedding' in meetings
  • engineers feeling safe to admit mistakes.
Technical Debt Management
Your ability to balance new feature delivery with maintaining the long-term health and stability of your team's codebase.
  • Regular, visible discussions with Product about tech debt prioritisation
  • a clear, agreed-upon plan for paying down critical debt
  • a reduction in 'YOLO merges'
  • fewer recurring bugs caused by legacy code
  • engineers feeling like they have time to improve things, not just build new ones.
Cross-Functional Collaboration
How effectively your team works with Product, Design, QA, and other engineering teams.
  • Product Managers consistently praising your team's communication
  • smooth handovers between design and engineering
  • proactive identification and resolution of cross-team dependencies
  • other EMs seeking your input on shared initiatives.
Engineer Growth & Development
Your effectiveness in coaching and mentoring your direct reports, helping them advance their careers.
  • Individual Development Plans (IDPs) in place for all engineers
  • regular feedback provided and acted upon
  • engineers taking on new challenges and responsibilities
  • successful promotions within your team
  • engineers feeling like they're learning and progressing.

7Would you like it

Both sides. What people enjoy, and what grinds them down.

What people enjoy
Developing People

You'll get a real kick out of seeing your engineers grow, solve harder problems, and get promoted. Your 1:1s aren't just status updates; they're genuine coaching sessions.

Helping a junior engineer debug a tricky issue, not by giving them the answer, but by guiding them to find it themselves. Then seeing them confidently tackle similar problems later.

Building High-Performing Teams

You're driven by the idea of creating a cohesive, efficient, and happy team that consistently delivers value. You love optimising workflows and fostering a positive culture.

Implementing a new team process that significantly reduces friction, leading to faster delivery and happier engineers, and seeing the positive impact on team morale.

Solving Complex Technical & Organisational Problems

While you're not coding, you'll be deeply involved in architectural discussions, technical debt strategies, and figuring out how to unblock your team from tricky dependencies. You enjoy the challenge of making sense of technical chaos.

Architecting a solution with your team that addresses a long-standing performance bottleneck, or mediating a complex technical debate between two senior engineers to reach a pragmatic solution.

What frustrates people
  • The Product-Engineering Tension: Constantly negotiating the balance between shipping new, revenue-generating features (Product's goal) and maintaining system health, paying down tech debt, and improving developer tooling (Engineering's need).
  • The Player-to-Coach Transition: The struggle of letting go of coding and resisting the urge to jump in and solve problems yourself, instead focusing on coaching your engineers to solve them. It's harder than it sounds.
  • Context Switching Overload: A day can consist of a 1:1 about career anxiety, a deep architectural debate on event sourcing, a budget review meeting with Finance, and triaging a live production incident. It's mentally exhausting, honestly.
  • Losing Good People: Investing months or years into mentoring an engineer, only to have them poached by another company for a 30% salary bump that you can't match. It stings.
  • Explaining 'Why it's Hard': Trying to justify to non-technical stakeholders why a seemingly simple UI change requires a multi-sprint effort because of underlying architectural complexities. It's like speaking a different language sometimes.
What this role does not give you
  • Significant hands-on coding (you'll do very little, if any, day-to-day).
  • A predictable, 'heads-down' work environment (expect constant interruptions and shifting priorities).
  • Instant gratification from shipping features (your impact is more indirect, through your team).

8Who you work with

Your team's output directly contributes to the success of a specific product area or core platform service. You're responsible for ensuring that this part of our technology stack is robust, scalable, and delivers real value to our customers. Get it right, and we're faster, more reliable, and build better products. Get it wrong, and we're playing catch-up, fixing bugs, and losing customer trust.

Inside the business
  • Product Managers (for feature delivery and roadmap alignment)
  • other Engineering Managers (for cross-team dependencies)
  • QA/Test Leads (for quality assurance and release processes)
  • UX/UI Designers (for user experience implementation)
  • Site Reliability Engineers (SREs) or Operations (for production stability)
Outside the business
  • Key vendors for specific tools or services (e.g., cloud providers, observability platforms)
  • Occasionally, technical partners for integrations (though this is less common at this level)

9What you need before you start

Not a wish list. The things you would be expected to already have.

  • Proven experience as a Senior Software Engineer or Team Lead (without direct reports) for at least 3-5 years, demonstrating strong technical leadership and mentoring skills.
  • A solid understanding of at least one major programming language (e.g., Python, Java, Go, JavaScript) and its ecosystem, even if you're not coding daily.
  • Experience leading complex technical projects from conception to deployment, including managing dependencies and risks.
  • Demonstrable experience with Agile methodologies in a practical setting, not just theoretical knowledge.
  • Experience with cloud platforms (preferably AWS) and understanding of modern CI/CD pipelines.

10What to practise next

Where the job is going, and what to do about it starting this week.

Cloud Cost Optimisation Strategies

Cloud spend is a significant cost for most technical organisations. EMs are increasingly expected to understand and manage their team's cloud budget, identifying opportunities for efficiency without compromising performance or reliability.

Reserved Instances and Savings Plans · Spot Instances and serverless cost models · Rightsizing compute resources · Tagging strategies for cost allocation · Cost Explorer and billing dashboards

  • This month: Review your team's current cloud spend in AWS Cost Explorer, identifying the top 3 cost drivers.
  • Next month: Research 2-3 cost optimisation strategies relevant to your team's services (e.g., Lambda cost optimisation, EC2 rightsizing).
  • Month 3: Work with your team to implement one quick-win cost optimisation, documenting the savings.
  • Month 4: Present your findings and a longer-term cost strategy to your manager.

Quick win: Ensure all your team's cloud resources are correctly tagged for cost allocation. It's a simple step that makes a huge difference for visibility.

Advanced Observability & Incident Response

As systems become more distributed and complex, effective observability is paramount. EMs need to go beyond basic dashboards to understand distributed tracing, synthetic monitoring, and how to use these tools for faster Mean Time To Resolution (MTTR).

Distributed tracing (e.g., OpenTelemetry) · Synthetic monitoring for critical user journeys · Log aggregation and analysis (e.g., ELK stack, Spl · Chaos engineering principles (basic understanding) · Blameless post-mortem facilitation

  • This month: Deep dive into Datadog's APM and distributed tracing features, understanding how to follow a request across services.
  • Next month: Implement one new synthetic test for a critical user journey owned by your team.
  • Month 3: Lead a blameless post-mortem using advanced incident analysis techniques, focusing on systemic issues.
  • Month 4: Train your team on advanced observability techniques, improving their debugging skills.

Quick win: Review your team's existing Datadog dashboards and alerts. Are they actually useful? Can you improve one to give clearer signals during an incident?

11Staying current once you are in

What people here do to keep up
  • Regularly attending industry conferences (e.g., LeadDev, QCon) to stay current with engineering leadership trends and technical advancements.
  • Participating in online courses or workshops on advanced leadership, coaching, or specific technical domains (e.g., system design, cloud security).
  • Reading books and articles on engineering management, team dynamics, and software architecture.
  • Joining peer groups or mentorship circles with other Engineering Managers to share experiences and best practices.

12The rising capability

The rising capability

Zavmo analysis

What's rising in its place

This is where the work is heading, and the higher pay with it. Get fluent here and the shift stops being a threat and starts being your edge.

AI-Powered Team Insights & Coaching

Tools are rapidly emerging that can analyse communication patterns, code contributions, and project data to provide insights into team dynamics, potential burnout, or areas for individual growth. EMs who use these will have a significant edge in supporting their teams.

  • Ethical AI usage in HR/management
  • Data privacy in team analytics
  • Interpreting AI-generated insights (e.g., sentimen
  • Using AI to identify coaching opportunities (e.g.,
  • Automated feedback aggregation

Advanced Prompt Engineering for Management Tasks

Generative AI is transforming how we draft communications, summarise complex information, and even brainstorm solutions. EMs who master prompt engineering will significantly reduce their administrative burden and improve the quality of their output.

  • Context windows and token limits for complex reque
  • Temperature settings for creative vs. factual gene
  • Role-playing prompts (e.g., 'Act as a seasoned HR
  • Iterative prompting for refinement
  • Using AI for summarisation of technical documents

13What you’ll use

What you’ll use

Skills this role draws on

Technical

  • Agile Methodologies (Scrum/Kanban)
  • System Design & Architecture Principles
  • Technical Debt Management
  • DevOps & CI/CD Principles
  • Performance Management & Coaching

14The pathway

The pathway

How you actually get there, here

How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.

  1. 1

    Senior Software Engineer to Engineering Manager

    3-5 years as a Senior Engineer

    Skills to master

    • Informal mentoring, technical leadership on complex projects, cross-functional collaboration, understanding of the full SDLC, basic project coordination.

    You're ready to move on when

    • You're the 'go-to' person for technical advice on your team.
    • You naturally mentor junior engineers without being asked.
    • You've led significant technical initiatives, not just contributed to them.
    • You find yourself thinking about team dynamics and process improvements more than just coding.
  2. 2

    Technical Lead (Player-Coach) to Engineering Manager

    2-3 years as a Technical Lead

    Skills to master

    • Formal team leadership (without direct reports), project ownership, stakeholder communication, conflict resolution, initial exposure to performance feedback.

    You're ready to move on when

    • You're already leading a squad or small team, even if you're still coding a fair bit.
    • You're comfortable with the tension between technical delivery and people needs.
    • You've started giving structured feedback to team members.
    • You're ready to significantly reduce your coding time to focus on people and process.
  3. 3

    External Hire (Experienced EM)

    Immediate (assuming relevant experience)

    Skills to master

    • Adaptability to new tech stack and culture, rapid relationship building, quick grasp of business domain, ability to assess and build team health quickly.

    You're ready to move on when

    • You have a proven track record of managing high-performing engineering teams.
    • You can quickly assimilate into a new organisational structure and tech environment.
    • You've successfully navigated the challenges of an EM role in previous companies.
    • You're looking for a new challenge where you can apply your leadership skills.

15Where this role leads

The long view: This role can lead further into management, into a senior technical role without direct reports, or into other functions altogether.

16Pay and demand

ONS's coding index maps “Engineering Manager” to more than one occupation, so there is no one median to quote. Rather than pick, here is each one it could be, with its own figure:

  • Production managers and directors in manufacturing £58,640 a year
  • IT managers £56,438 a year
  • Production managers and directors in construction £56,021 a year

ONS Annual Survey of Hours and Earnings, from the April 2025 survey, about six months old when published, as ASHE always is, under the Open Government Licence.

The ten Future Fluencies

Zavmo analysis

The credential is what you can do today. These are what keep you valuable.

A qualification proves you can do the job as it's defined today. These ten are what decide whether you're still the obvious person for it in five years. They're the capabilities employers are now writing into senior roles faster than people are learning them. Zavmo weaves them through whatever you study, so you come out with both: the credential and the fluency.

The highlighted ones are the Fluencies your role leans on hardest, from how Engineering Manager is actually changing.

Where it leads

Roles this leads to

Also named as a next step, with no page in the catalogue yet:

  • Staff Engineer (Individual Contributor)

How you would learn this

One to one, on the work you already do

A tutor sets the task against your own job and marks the reasoning, at your pace. There is no cohort to fall behind.

A lesson from Leading a team in Engineering, worked against Engineering Manager.

Leading a team in Engineering Level 2

Applied to your work in Engineering Manager

The objective of this unit is to equip learners with an understanding of the roles, responsibilities, knowledge, and skills required to effectively lead a team in an engineering environment. Learners will explore how to manage team workloads, allocate tasks, and contribute to achieving team goals through effective leadership practices.

How the thinking builds
  1. 1 Remember
  2. 2 Understand
  3. 3 Apply
  4. 4 Analyse
  5. 5 Evaluate
  6. 6 Create
An illustration of a Zavmo lesson, built from this role’s own route. The unit, its objective and every criterion above are the awarding body’s own words, not an example.

It is £70 a month, billed monthly. Your free first module is Future Fluency, and you can cancel any time.

Start my Engineering Manager plan, free
See Your Progress Grow Illustration
Engineering Manager
  • Agile Methodologies (Scrum/Kanban)
  • System Design & Architecture Principles
  • Technical Debt Management
  • DevOps & CI/CD Principles
  • Performance Management & Coaching
This is your Mind Palace on learn.zavmo.ai. Every skill above comes from this role's own record, not an example borrowed from another job. A node lights up when you evidence it, and what you build stays yours between jobs. That is the part a course cannot do.

17The detail, folded away

Everything else the record holds

The career branches in full, how AI is already showing up in the day-to-day, and the questions people ask about this job. Here when you want them, out of the way while you decide.

Where it leads next, rung by rung

Where it leads

The career path, and where it branches

Engineering Manager is a start, not a ceiling. Each step below asks for new skills and hands back more autonomy.

  1. Senior Engineering Manager

    3-5 years in this EM role

    L3

    • Leading complex, cross-team technical initiatives
    • Defining technical strategy for a specific domain or product area
    • Managing larger teams or multiple smaller, related teams
    • Deeper understanding of financial implications of technical decisions

  2. Staff Engineer (Individual Contributor)

    3-5 years in this EM role

    L4 (IC track)

    • Designing and implementing large-scale, complex systems
    • Solving the hardest technical challenges that span multiple teams
    • Evaluating and introducing new technologies to the organisation
    • Providing technical guidance and unblocking multiple teams
Working with AI on the job

Working with AI

Where AI is starting to help

Let's be honest, managing an engineering team is a lot of work. You're juggling people, projects, and production issues. What if you could offload some of the tedious bits and focus on what truly matters: your team and their impact? That's where AI comes in.

We're not talking about AI replacing you; we're talking about AI making you a more effective, less stressed Engineering Manager. Think of it as having a super-smart assistant who handles the grunt work, leaving you free to lead, coach, and strategise. You'll be surprised how much time you can claw back.

Automated Code Review Assistant

Use tools like GitHub Copilot for Pull Requests or other AI code analyzers to automatically comment on PRs. This catches common bugs, style violations, and security vulnerabilities before a human reviewer even sees it. It's like having another pair of eyes, but faster.

1:1 Preparation & Insight Generator

Imagine an AI agent that synthesises a direct report's recent activity – GitHub commits, Jira tickets, Slack messages, even public praise – into a summary dashboard. It can highlight potential burnout risks (e.g., high PR comments, late-night activity) or achievements to discuss, making your 1:1s far more impactful.

Performance & Feedback Drafter

Use a generative AI tool to create first drafts of performance reviews or project feedback. By feeding it a list of bullet points and examples (based on those 1:1 insights), it can structure them into a coherent, well-written narrative aligned with our career ladder. It's a huge time saver during review cycles.

Incident Post-Mortem Scribe

During a post-mortem meeting, an AI transcription and summarisation tool can capture the entire conversation, identify key decisions, and automatically generate a draft Root Cause Analysis (RCA) document. This includes a clear timeline of events and actionable items. No more frantic note-taking while trying to lead a critical discussion.

Common questions

Common questions

How do you become an Engineering Manager?

Common routes in include Senior Software Engineer to Engineering Manager (3-5 years as a Senior Engineer), Technical Lead (Player-Coach) to Engineering Manager (2-3 years as a Technical Lead) and External Hire (Experienced EM) (Immediate (assuming relevant experience)). Times vary with prior experience.

Where can an Engineering Manager progress to?

This role can lead on to Senior Engineering Manager (3-5 years in this EM role) and Staff Engineer (Individual Contributor) (3-5 years in this EM role), depending on the skills you build.

What new skills matter most for an Engineering Manager?

Increasingly, AI-Powered Team Insights & Coaching and Advanced Prompt Engineering for Management Tasks. These are the skills our record of this role lists as growing.

Free tools

Want a read on where you stand?

Three free tools, no account needed. Each one ends with a role, a level and a way in.

Read the Zavmo manifesto to understand how you will be taught Meet your tutors

Or try another one

18Where to go from here

Other roles at Level 4

Same depth of qualification, different job. Useful if the work appeals but this particular role does not.
This job at other levels
More jobs in technology and data

Stay in the field you know and move sideways rather than up.
If you leave this industry

The skills built as an engineering manager transfer across industries. Leading teams, solving complex problems and working through technical detail are useful in product management or technical consulting roles, among others.

This role profile is © 2026 Growth Engineering Technologies Ltd. Built from UK occupational standards and regulated qualification data, and written for Zavmo.

You're not behind. You're right on time. The shift is only just beginning. Your role won't look the same in two years. Be the one who leads the change, not the one it happens to. Start my Engineering Manager plan, free What happens next: a free account, then we build your plan as you set up. No card. Build your plan, see your roadmap and meet the twelve tutors matched to you. All free. When you're ready to start learning, it's £70 a month, billed monthly. Cancel any time and billing stops.