Head of Engineering

O projekcie: Meniga builds financial intelligence for the world's leading banks - 100M+ users, 30+ countries. We're not the brand on the app. We're the layer underneath it - the one that makes the data meaningful, the experience personal, and the bank worth opening. Meniga’s offices are in London, Reykjavik and Warsaw. THE WORK You run Meniga’s engineering organisation - 27 engineers across five teams, each with real ownership and real clients. You report directly to the CTO. You are accountable end-to-end - from operation and execution to what lands at the client. The outcome reaches production at the bank, or it didn’t ship. The first months are hands-on. You’ll carry individual contributor weight alongside your team leads - shipping, reviewing, making calls - while you learn the services, the clients, and what the organisation actually needs. The context is a real-scale transformation running in parallel with active client delivery at European-scale banks. On-premises licensing to cloud. MSSQL to PostgreSQL at scale. Core product rewritten from the ground up. A fragmented portfolio being standardised and platformised. AI embedded across the entire SDLC — tooling, testing, workflows. This isn’t greenfield. There’s real legacy, and the goal is strangler fig — not a rewrite. The role is for someone who can lead through real constraints, not around them. WHAT YOU'LL GET - Competitive salary + meaningful equity: B2B, 28-37k PLN + VAT, + ESOPs - Hybrid - 2 days in office, 3 remote days - Private healthcare, fitness, meal & phone allowance - A seat at the leadership table and a direct line to the CTO - The mandate to build the engineering organisation you’d want to join - Software that runs inside real banks, used by 100M+ people every day Wymagania: WHAT WE'RE LOOKING FOR - Run engineering at this scale before - real product in production, with clients that hold you to it. You can point to what changed under your leadership - End-to-end accountable - you own operation and execution from roadmap to what the client experiences in production. Not “my team delivered their part.” The outcome reaches the client, or it didn’t ship - Still technically credible - you don’t need to write the code, but you can read a PR, smell a bad architectural decision, and ask the question that exposes it. Your team leads can’t bullshit you technically, and they know it - Outcome over activity - you measure the organisation on what shipped and how it performed - not on how busy it looked - Comfortable with commercial reality - you can sit in a client escalation, a board review, and a post-incident retro in the same week and bring the same clarity to each - AI-native - you have a real position on how AI changes engineering - tooling, headcount, skill mix - and you’re already acting on it Codzienne zadania: - Own engineering delivery end-to-end - from roadmap commitment to what lands in production at the bank. No handoffs, no diffusion of accountability - Targets are real commitments - you take them seriously, you find a way, and when something is blocking delivery you remove it - you don’t escalate it into a slide deck - Make the transformation happen - not as a programme manager, not as a coordinator - as someone who understands what needs to happen technically, removes what blocks it, and is accountable for the result - Build an engineering organisation that can handle this - regulated clients, on-premises constraints, high-stakes delivery. You hire for that reality, grow people into it, and don’t accept a team that could only survive in easier conditions - Partner with CTO, Product, and Commercial - translate business commitments into engineering execution, represent engineering in client escalations and board reviews - Embed AI across the SDLC - coding, testing, workflows. Full automation is the goal, not the aspiration