Engineering Director, Software Development

Role Overview

• Own delivery across multiple engineering squads, setting a high bar for quality, predictability, and speed
• Drive engineering planning, milestone scoping, and release readiness across product domains
• Establish and maintain engineering standards across code quality, testing, incident response, and post-mortems
• Lead planning and execution of complex programmes such as major platform or processor migrations, sequencing dependencies and keeping stakeholders aligned across the full lifecycle
• Proactively identify risks to delivery and act on them before they escalate
• Build and scale a group high-performing engineering managers and engineers, raising the leadership bar across the organisation as headcount and product complexity grow
• Own engineering hiring from sourcing strategy to bar-raising in interviews
• Measure delivery performance with meaningful metrics and use that data to differentiate strong performers, identify gaps, and make deliberate decisions on who to grow, stretch, or transition
• Build a team culture that is direct, collaborative, and outcome-oriented
• Maintain enough technical depth to credibly review architectural decisions, challenge tradeoffs, and guide the team toward scalable, maintainable systems
• Champion the adoption of AI-assisted development practices as a genuine force multiplier across the engineering organisation
• Work closely with Product, Design, Compliance, and Operations to ensure engineering is a reliable partner in delivering business outcomes
• Engage with external technology vendors and partners with clarity and commercial awareness
• Represent engineering in leadership forums and communicate technical context in business terms

Requirements

• Delivery-focused leader. You have a track record of shipping in high-stakes, fast-moving environments.
• People builder. You invest in your Engineering Managers as seriously as you invest in product delivery. You assess talent honestly and know that the quality of your team three years from now is something you are shaping today.
• Technically credible. You have built or scaled complex backend systems. You can walk into an architecture conversation and add value without needing to write production code daily.
• Fintech-native. You have worked in payments, lending, or banking. You understand the operational stakes and build engineering culture accordingly.
• Clear communicator. You write and speak directly. You can brief the C-Suite on an incident, a roadmap, or a hiring decision without hiding behind process language