Engineering Manager - Cross-Functional Team

What will you be doing?

• Lead a cross-functional team spanning frontend, mobile and backend, helping engineers grow beyond their original specialism and supporting them as they pick up unfamiliar parts of the stack

• Own a defined area of software architecture, taking responsibility for delivery, quality, and technical direction

• Run an effective development process: sprint health, delivery cadence, incident response, postmortems, and a sustainable on-call rotation that doesn't burn people out

• Grow the engineers on your team through regular feedback, performance conversations, and stretch assignments that actually move people forward

• Work closely with product to scope initiatives, identify risks, and prioritise deliverables, giving clear heads-up when capacity is constrained

• Stay close enough to your team's technical work to ask the right questions, spot risks early, and contribute meaningfully to design discussions without becoming a bottleneck

• Define the right metrics for your team's systems, use them to explain performance, catch variance, and drive improvements before they become incidents

• Handle the difficult conversations, whether that's performance issues, interpersonal friction, or delivery risk, before they become problems that need escalating

What we're looking for

• Comfortable leading a cross-functional team. Either you've managed engineers across frontend, mobile and backend before, or you're genuinely open to it and to ramping up on the parts of the stack you know less well

• A background as a software engineer, with hands-on experience building and shipping production systems. This is a hard requirement.

• Experience managing a team of engineers, with a track record of building effective development processes and growing individual contributors

• Technically credible enough to evaluate design decisions, challenge assumptions, and be taken seriously by strong engineers, without needing to be the most technical person in the room

• Comfortable with operational ownership: on-call culture, incident management, postmortems, and the unglamorous work of keeping systems healthy

• Clear, direct communication with stakeholders and leadership, including knowing when and how to escalate and when not to

• Able to operate with meaningful autonomy: you don't need a playbook for every situation, but you know when to ask for one

Nice to have:

• Direct experience managing full-stack or cross-functional teams. However this team is backend leaning (Python).

• Experience in fintech, payments, or a similarly regulated and high-stakes technical domain

• Familiarity with distributed systems and the trade-offs that come with high-throughput, high-availability infrastructure