- Plans and pricing – pricing structures and bands, session and product catalogues, term dates and attendance schedules, discounts, deposits, surcharges, and the plans that turn a child's schedule into a bill
- Invoicing – invoice runs and batch reissues, billing schemes from actuals to annualised, bill payers and how one child's bill splits between them, credit notes, and balances
- Payments – card and direct debit through Stripe, autopay, parent bookings and ad hoc purchases, UK Tax-Free Childcare, and payment methods that differ market by market
- Getting paid – debt collection with overdue buckets, payment reminders, bank statement imports, and the revenue and debt reports owners run every month
- Public funding – UK funded hours, entitlements and eligibility codes, US state subsidies with parent copay, German parental contributions, and the reports that claim the money back
- Accounting exports – the chart of accounts and exports into DATEV, Sage, Xero, and QuickBooks, so the numbers land where a finance team already works
Every number here is someone's money, and a rounding error is a phone call from a parent. Precision matters, though it rarely means one right answer. Where regulation is exact (funded hours, tax rules, what a direct debit mandate allows) the code has to match it to the decimal. Everywhere else, a nursery in Berlin prices care nothing like a nursery in Ohio, so the work is giving each of them room to do it their way without handing them a blank spreadsheet. Drawing that line well, over and over, across markets, is most of the craft here.
One honest note for a backend engineer: Finance carries more of our remaining PHP than most teams, alongside a lot of Scala. Moving it across is part of the job, and it comes with the kind of ownership that only old, critical code gives you.
Finance is a team of 14. Eight Builders (plus the one we're hiring), two Product Managers, two Designers, and a Head of Product.
Frameworks – the ground every other team builds on
Some problems don't belong to any one team. They turn up on every screen, no single team owns them, and each one quietly decides how fast the rest of Famly can move. That's Frameworks. You build the foundations other Builders build on, and when they're done right, the teams using them barely have to think about them.