Engineering Manager, Payment Services

Job Summary

As an Engineering Manager at Tide, you will lead the Accounts team. You will set its technical direction, own its delivery and reliability, and grow its engineers across backend, mobile, and web. This is a product-facing platform team. A large share of the work shows up directly in the app, so you will work closely with product and design. It is also a financial system: a transaction that renders wrongly, a statement that does not reconcile, or an export that misses a record is a correctness problem, not a cosmetic one.

Responsibilities

• Leading the Accounts team across backend, Flutter mobile, and Angular web, setting its technical direction and holding it to delivery.
• Defining and maintaining the interface with the ledger: what the ledger guarantees, how Accounts services consume it, and who owns which data and schemas.
• Owning account opening, account management, and account switching (CASS), including the regulatory compliance that comes with them.
• Owning the member-facing transaction experience end to end: the timeline, transaction details, counterparty information, transaction history, statements, and exports.
• Setting technical direction for services that are read-heavy, data-rich, and tightly coupled to the app: performance, pagination and search at scale, data consistency with the ledger, and long-term architecture.
• Owning system stability and operational reliability for your services: SLOs, observability, on-call practice.
• Partnering with product, design, compliance, and operations to make sure what we ship is accurate, supportable, and compliant across all markets.
• Growing engineers at every level, across backend, mobile, and web. The team spans early-career through senior.
• Partnering with other teams at Tide that build on the Accounts platform, such as investment accounts and savings accounts, so the platform meets their needs.
• Aligning with other EMs across Banking on shared platform and infrastructure 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
• Experience leading product-driven teams. You have worked closely with product and design and been accountable for customer outcomes, not just output
• 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
• Proven experience aligning with senior leadership on deliveries and managing dependencies with neighbouring teams
• Strong grasp of distributed systems: data consistency across services, reliability patterns, SLOs and SLAs, observability tooling

Technical depth

• Technically fluent: you can read the code, follow the architecture, and engage meaningfully 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, but Java experience is not a requirement. We want someone who can learn and work in our stack with confidence.
• Experience with microservices in a cloud-native environment (we are AWS heavy).
• Designing and operating APIs and data services that feed mobile and web clients: latency, pagination, caching, and backwards compatibility with released app versions.
• Relational database engineering, including data modelling and query performance for read-heavy workloads over large transaction histories.
• Event-driven and async systems experience.
• Familiarity with mobile and web delivery (Flutter and Angular, or similar), enough to make good trade-offs with client engineers.
• Exposure to agentic or AI-integrated systems, and engineering practises.

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 care about the member experience and about correctness in equal measure, and you do not let one erode the other.
• You are a good neighbour to other teams. You make interfaces explicit, agree expectations early, and treat partner teams across Banking as close collaborators.
• You communicate clearly with non-technical stakeholders (product, design, compliance, operations) without losing precision.
• You develop engineers at every level, with a plan for each person.

Our tech stack

• Java, Spring Boot and JOOQ to build the RESTful APIs of our microservices (but we welcome people who are used to any strongly typed general purpose programming language!)
• Event-driven architecture with messages over SNS+SQS and Kafka to make them reliable
• Primary datastores are PostgreSQL via RDS or Aurora (we are heavy AWS users)
• Docker, Terraform, ArgoCD and, EKS provided by the Cloud team to run the platform
• DataDog for monitoring, observability and automated SLOs
• GitHub, Semgrep and solid testing to power the CI/CD pipelines - new joiners are encouraged to have something deployed to production in their first week

Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.