Senior Engineering Manager

Why we feel you'll like the role of Senior Engineering Manager

You’lllead a domain of 6-10 teams (roughly 60-90 engineers), manage the Engineering Managers who run those teams day to day, and report to the Director of Engineering. It’s a manager-of-managers role, working alongside Product and commercial leadership as a peer, not just a bigger single team and not a purely internal-facing management job.

It’s a step up from an Engineering Manager role, not a bigger version of one. An EM owns a team. A Senior EM owns the system of teams: how they’re structured, how work flows between them, how the EMs leading them grow, and how the domain shows up to Product and the wider business.

You’llspend less time in any one team’s backlog and more time on the conditions that let several teams deliver well at once: resourcing, coaching, architectural alignment, andrepresentingengineering credibly outside engineering.

The domain has real history and real constraints, not a green field: a mix of established and modernising systems, some legacy platforms alongside newer stacks, and teams at different levelsof technical and operational maturity.

You’llbe expected to form your own view of what's working, what isn't, and what needs to change, and to build the trust needed to act on it.

You’llmake decisions based ondata, andhelp build a culture of measurement and continuous improvement.

• Coaching and developing the Engineering Managers (and senior/lead engineers) who report to you: their technical judgement, their people leadership,their career growth.
• Structuring and re-structuring teams as the work demands it, closing skill or capacity gaps and avoiding key-person dependencies rather than treating team shape as fixed.
• Holding a consistent, visible bar for what a high-performing team looks like across your domain, and addressing sustained under-performance directly rather than leaving it to individual EMs.
• Building a hiring and retention engine for the domain: enabling your EMs to hire well, and finding growth and mobility paths for strong engineers.

• Being the first line of escalation for delivery and technical issues across yourteams, arriving with context and a proposed path forward rather than just the problem.
• Coordinating effort across work streams and delegating decisions to EMs with clear boundaries, then following through rather than disappearing after handoff.
• Partnering with Product and commercial stakeholders to define shared metrics, challenge scope andtrade-offs, and keep teams aligned to a durable mission rather than reactive requests.
• Applying team-topology thinking (Conway’s Law and similar) to keep team boundaries and interaction patterns deliberate rather than accidental.

• Staying close enough to the technical detail to ask good questions andspot drift, without being hands-on: your leverage is through your EMs and senior engineers,not your own commits.
• Protecting space for quality against deadline pressure, and coaching your EMs to do the same with their teams.
• Driving the domain’s operational maturity (testing, observability, incident response) in partnership with teams rather than mandating from above.
• Building credible cases for structural or technical investment (replatforming,team re-formation, headcount) grounded in business need.

• Representing your domain to peers, Product, commercial stakeholders, andsenior leadership, andrepresentingthe wider engineering organisation’s priorities backinto your domain.
• Operating as a genuine partner to senior stakeholders outside engineering, not just an escalation point they go through.
• Challenging the status quo constructively, including with more senior colleagues, and forming clear, evidence-basedviewsyou’rewilling to be challenged on.
• Connecting your teams’ technical work to userand business outcomes.

• A track record of managing managers: you’ve led other Engineering Managers or equivalent senior technical leads, not just individual engineers, across a multi-team domain of comparable scale.
• Strong technical grounding: not hands-on day to day, but deep enough to hold a real technical conversation, sense-check…