Senior Engineering Manager

United Kingdom·LondonFull-timesenior

EngineeringEngineering Manager

0 views0 saves0 applied

Key Responsibilities

she owns the plan and the stakeholder conversation, you own the engineering behind it, including dependencies,

Requirements Summary

what was promised, what landed, and what you did when it went wrong You have taken an underperforming team up a level, and can say ex

Technical Tools

EngineeringEngineering Manager

~2 min read

You have run engineering delivery before

→At least four years leading software engineers in a technical delivery capacity, accountable for what shipped and when, not only for technical direction
→You have led a team of five to ten engineers on a live SaaS product
→A record of shipping committed work to agreed dates that you can talk through in specifics: what was promised, what landed, and what you did when it went wrong
→You have taken an underperforming team up a level, and can say exactly what you changed and how

You estimate and plan seriously

→You have built estimates other people relied on, and you can explain your method: decomposition, ranges, confidence and contingency
→You measure how accurate your estimates turn out to be, and you improve them
→You tell stakeholders bad news early, with a plan attached

You are hands-on in our stack

→Current, hands-on skill with Next.js, React and TypeScript, and with Laravel and PHP. You can pick up a ticket yourself, not just review one
→You already work AI-first: tools such as Claude Code are part of how you build every day, and you know where they help and where they hurt
→Comfortable reading code, reviewing pull requests and challenging an estimate or a design on its technical merits
→A working understanding of CI/CD, environments, releases and running production on AWS

You lead people well

→Direct, fair and comfortable having hard conversations about performance
→You have run formal performance processes properly, from the first conversation to the outcome
→You build accountability in a team without micromanaging it
→You have made engineers responsible for their work in production, not just for getting it merged, and can explain how you made that stick

Nice to have

This probably is not for you if

→You see the job as running ceremonies and reporting status
→You consider delivery someone else's problem once the estimate is agreed
→You think production support belongs to a different team from the one that wrote the code
→You would rather not report delivery numbers every week, good or bad
→You want to stop writing code entirely, or to write code full time
→You want a fixed routine and a clean finish at five o'clock whatever state the release is in
→You are looking for a fully remote role