Tide is a London-based fintech platform that offers SMEs digital business accounts, payments, invoicing, accounting integrations, expense management and embedded lending products through a single interface.
<div class="content-intro"><h3><strong>A</strong><strong>BOUT TIDE</strong></h3> <p>At Tide, we help SMEs save time and money in the running of their businesses by not only offering business accounts and related banking services, but also a comprehensive set of highly usable and connected administrative solutions, from invoicing to accounting.</p> <p>Tide is transforming the small business banking market and now supports over 2 million members globally across the UK, India, Germany and France.</p> <p>Using advanced technology, all solutions are designed with SMEs in mind. With quick onboarding, low fees and innovative features, we thrive on making data driven decisions to serve our mission: to help SMEs save time and money so they can get back to doing what they love.</p> <p><strong>Tide facts:</strong></p> <ul> <li>Tide is available for UK, Indian, German and French SMEs</li> <li>Over 2 million members: 900,000 UK and 1,100,000 in India and growing rapidly</li> <li>Over $300 million raised in funding</li> <li>Over 2,800 Tideans globally</li> <li>Recognised with Great Place to Work certification three years in a row, and among India’s Top 50 Best Workplaces in Banking, Financial Services, and Insurance in 2026</li> <li>We have offices in Central London, with a member support and technology centre in Sofia, Bulgaria, technology centres in Serbia, Romania, Lithuania and Hyderabad and offices in Gurugram, New Delhi, Berlin, Paris and Luxembourg</li> </ul></div><p></p> <h3>ABOUT THE TEAM:</h3> <p>The Accounts team is the platform layer at the centre of Tide's financial infrastructure. It owns the core financial ledger, the single source of truth for every member's money, alongside account opening, regulatory compliance, statements, and account lifecycle management. Every payment, every balance, every downstream service in Banking depends on this team getting it right. The team operates across the UK, India, and EU, working across a landscape of different banking partners, regulatory regimes, and account structures, all underpinned by one ledger that needs to be fast, accurate, and always available.</p> <h3><br>ABOUT THE ROLE:</h3> <p>The Accounts team is about to split. The ledger is being carved out into its own dedicated team (the Ledger Team), with a mandate to treat it as the high-volume, high-criticality system it is: low latency, high availability, rigorous consistency guarantees. Today the ledger shares a team with account opening, lifecycle management, and compliance. As Tide has scaled across more markets and more complexity, the ledger needs dedicated engineering focus: its own team, its own SLOs, its own on-call practice, its own technical roadmap.</p> <p>The EM we hire now will join to lead the full Accounts team through that transition. Working alongside the existing team, which includes strong staff-level IC experience, you will help design the seam between the two teams, work out where engineers land, and build the organisational and technical foundation for both. When the split lands, you will move across to lead the Ledger Team. A new EM will be hired to run the remaining Accounts team.</p> <p>The ledger underpins every payment, every balance check, every statement across all markets. It needs to be engineered to the same standard as any large-scale financial system: fault tolerant, highly available, operationally rigorous. You will own the technical direction of that system alongside experienced ICs who know it deeply. This is hands-on work, not process management.</p> <p>As an Engineering Manager:</p> <ul> <li>Leading the Accounts team (9 engineers: backend, mobile, web) through the ledger split, including helping shape how engineers map to each team and sequencing the transition</li> <li>Working with the existing team to define the technical seam: ledger writes, consistency guarantees, schema ownership versus account opening, lifecycle, statements</li> <li>Setting the engineering direction for the Ledger Team post-split: performance, availability, consistency, long-term architecture</li> <li>Owning system stability and operational reliability: SLOs, observability, on-call practice</li> <li>Partnering with product, compliance, and internal operations teams to make sure what gets built is accurate, supportable, and compliant across all markets</li> <li>Growing engineers at every level. The team spans early-career through senior</li> <li>Aligning with other EMs across Banking on cross-cutting infrastructure decisions</li> </ul> <h3><br>WHAT WE ARE LOOKING FOR: </h3> <p><strong>Experience and background</strong></p> <ul> <li>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</li> <li>A solid backend engineering foundation before moving into management, enough to earn credibility with the team and get into the detail when it matters</li> <li>Experience leading distributed, remote-first teams across time zones</li> <li>Proven experience leading technical teams, aligning with senior leadership on deliveries, and partnering with product</li> <li>Fintech or banking domain experience: you know the regulatory surface and what it means to run systems where correctness is not optional. High-volume transaction processing experience is a plus, whether in payments, FX, or similar domains</li> <li>Strong grasp of high-volume distributed systems: consistency models, fault tolerance, reliability patterns, SLOs and SLAs, observability tooling</li> </ul> <p><strong>Technical depth</strong></p> <ul> <li>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</li> <li>Backend engineering in a strongly-typed language (our stack is Java/Spring Boot; we want s