Engineering Manager

About the Role:

The engineering challenge here is correctness and reliability at scale. Direct debit mandates involve scheme rules, dispute handling, and indemnity claims. Standing orders and sweep rules are time-based, rule-driven systems where there is no margin for error. A recurring instruction either runs exactly as configured or it does not. Holding that standard across multiple markets, multiple banking partners, and growing member volume is the core of this role.

You will own the technical direction of the team, work closely with product to shape what gets built, and set a high bar for reliability and engineering quality. This is a team with clear ownership and engineers who know their domain well. The work is to push that further: better observability, sharper SLOs, cleaner architecture, and a higher standard of practice across the team.

What You Will Be Doing:

• Leading a team of 7 engineers (backend and mobile) across Lithuania and Bulgaria
• Getting deep into the systems: mandate management, scheduling, sweep logic, internal transfer flows
• Setting engineering direction: reliability, correctness, observability, long-term architecture for systems that run on schedule with no human in the loop
• Owning system stability and operational reliability: SLOs, on-call practice, incident response
• Partnering with product to make sure what the team builds is right for members and compliant with scheme rules across all markets
• Growing engineers at every level. The team spans early-career through senior
• Aligning with other EMs across Banking on shared infrastructure and cross-cutting decisions

What We Are Looking For:

Experience and background

• Meaningful engineering management experience. You have led teams through real delivery, not just been a strong tech lead. What matters is the quality of that experience, not the number of years
• A solid backend engineering foundation before moving into management, enough to earn credibility with the team and get into the detail when it matters
• Experience leading distributed, remote-first teams across time zones
• Experience working cross-functionally: partnering with product, aligning with senior leadership on delivery, and building trust with non-engineering stakeholders
• Fintech or banking domain experience: you understand what it means to run systems where correctness is not optional. Experience with payment schemes (direct debits, standing orders, or similar scheduled/recurring payment infrastructure) is a strong plus
• Strong grasp of reliability engineering: SLOs, observability, scheduled and event-driven systems, and what happens when things go wrong at the wrong time

Technical depth

• Technically fluent: you can read the code, follow the architecture, and engage with design decisions and production problems. You do not need to be shipping features regularly, but you need to understand what your team is building and why
• Backend engineering in a strongly-typed language (our stack is Java/Spring Boot; we want someone confident in a similar language and willing to engage with ours)
• Event-driven and async systems experience
• Relational database engineering at scale: transactions, consistency guarantees, and correctness at volume
• Experience with microservices in a cloud-native environment (we are AWS-heavy)
• Some exposure to agentic or AI-integrated systems is a plus

How you work

• You set technical direction and hold others to it. You are the person the team turns to when something is hard
• You understand that building reliable systems is the job, not a nice-to-have
• You communicate clearly with non-technical stakeholders (compliance, finance operations, risk) without losing precision
• You develop engineers at every level, with a plan for each person

Our tech stack

Java and Spring Boot microservices running on AWS, with PostgreSQL as our primary datastore. We use SNS/SQS for async and event-driven messaging. Observability is DataDog, with a migration to Coralogix underway. CI/CD runs through GitHub with automated testing and security scanning. New joiners typically have something in production within their first two weeks. Mobile is Flutter, web is Angular.