Senior Software Engineer

Builder at Famly Raising a young child takes a village - families, educators, and everyone else in a child's early life. But too often those grown-ups work in isolation from each other, and from the information that would help them nurture a child together. Famly is the early childhood platform that closes that gap: one place for the adults around a child to connect, share the workload, and learn - so they can focus on the early interactions that count. All of it in service of a better start for every child. We're looking for experienced engineers - we call them Builders - to help us make it better. We have open spots in several of our teams right now, so below find a short intro to each team currently hiring, and what being a Builder at Famly actually means, so you can see where you'd fit. The teams currently hiring Famly is organised into small, autonomous teams, each owning a meaningful slice of the product end-to-end. The following have an open position right now: ACE - Aid, Connect & Educate ACE owns the connective tissue between a nursery and the families it serves, mapped onto three parts of Famly's mission - keep children safe, communicate, and help every child learn and grow: Aid - keeping children safe and settings compliant: accident forms, medication records, immunizations, headcounts, and the daily logs (meals, naps, nappies) that keep a room accountable and audit-ready.Connect - parent and staff communication: Newsfeed, Messaging, live translation, meal booking, photos, permissions, and the staff documents and handover notes the team relies on. The daily thread between nursery, home, and colleagues.Educate - helping every child learn and grow: the activity library, activity planner, curriculum builder, and child development records educators use to track and nurture progress.ACE is a team of 9 - five Builders (plus the one we're hiring), working alongside a Product Manager, a Designer, and a Head of Product. This role is based in our Copenhagen office. STAT - Staffing, Attendance & Capacity Every day, nursery and school managers lose hours to rotas, ratios, staff absence, and the time tracking admin that follows — time they'd rather spend with their staff and the children in their care. Staffing is a nursery's single biggest cost line, and one of the most tightly regulated parts of running one — ratios, qualifications, overtime and time-off rules all vary market by market. What the team takes care of: Staffing - staff schedules, time tracking, absence, contract, and hours for payrollCompliance - staff-ratio calculations, special care rules, ratio reportsCapacity - occupancy, room move scenario automation, future availability, leaversRoom management - expected attendance, live attendance, compliance oversight, settingsAttendance - child attendance, the sign-in app, child holiday managementSTAT is a team of 8 - four Builders (plus the one we're hiring), working alongside a Product Manager, a Designer, and a Head of Product. This role is based in our Copenhagen office. Finance - Billing, Payments & Funding Fees are where a nursery's goodwill gets tested. Parents want a bill they can understand, owners want the money actually in the bank, and the person in the office wants an evening back instead of a spreadsheet reconciling government funding against 200 children's attendance. What the team takes care of: Plans and pricing - pricing structures and pricing bands, session and product catalogues, term dates and attendance schedules, discounts, deposits, surcharges, and the plans that turn a child's schedule into a billInvoicing - 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 balancesPayments - card and direct debit through Stripe, autopay, parent bookings and ad hoc purchases, UK Tax-Free Childcare, and payment methods that differ market by marketGetting paid - debt collection with overdue buckets, payment reminders, bank statement imports, and the revenue and debt reports owners run every monthPublic funding - UK funded hours, entitlements and eligibility codes, US state subsidies with parent copay, German parental contributions, and the reports that claim the money backAccounting exports - the chart of accounts and exports into DATEV, Sage, Xero, and QuickBooks, so the numbers land where a finance team already worksFinance is a team of 14 - 8 Builders (plus the one we're hiring), working alongside two Product Managers, two Designers, and a Head of Product. This role could be based in our Berlin office or Copenhagen office. About the role At Famly a builder owns work end-to-end. You'll work full-stack, with a lean toward the backend, across a genuinely large and mature codebase. The frontend is React and TypeScript. Most of the backend is Scala (we've just upgraded to Scala 3) - and there's also some PHP that we're actively migrating away from, so you'd spend time in it, but the direction of travel is clear. It all runs on AWS and Kubernetes, backed by MySQL, and at real scale: over a million users and around 15.000 requests per second at peak. Enough load that the hard problems are genuinely hard. How we actually work This is where Famly differs from a lot of engineering teams, so we'll be straight about it - because it suits some people brilliantly and isn't for everyone. High autonomy, high ownership. There's no one handing you a ticket with the answer already in it. We prioritise speed over predictability: Kanban, no sprints, no story-point estimates. We size work by appetite (how much time it's worth), not by guessing effort. You shape your own work. For most tasks that means writing the problem statement and scope yourself; for bigger projects, breaking them into shippable slices with the designer and PM. Refinement is Builder-owned.We think together, not just alongside each other. Autonomy doesn't mean alone. A short daily keeps us aligned, and Linear is our shared source of truth - but the real work happens in the sparring: bouncing an approach off a colleague, pairing on something gnarly, reviewing each other's work, and talking problems through before and while we build. You own your work, but you're never stuck on it by yourself.Chapters and guilds connect us across teams. Beyond your team, Builders come together in cross-team chapters and guilds to share craft, align on how we build, and learn from each other - so good ideas and hard-won lessons don't stay trapped in one team.We look after the codebase together. A weekly "hero" rotation covers production errors (via Sentry, our error-monitoring tool) and flaky tests, so quality is a shared habit rather than someone's afterthought. AI is genuinely part of how we build We actively experiment with AI and agentic coding to work faster and better, and we share openly across the team: when someone finds a workflow that helps, they pass it on - and when something flops, we say that too. One current experiment is auto-generating PRs from our error monitoring, it's early, and more useful in some areas than others. That honest, try-it-and-see approach is the point. If you're excited to help figure out what AI can actually do for a real engineering team - not just talk about it - you'll be among people doing the same. You'll thrive here if You care that the software does real good for the people using it. We call it sitting in the tiny chair.You've owned features end-to-end before - not just implemented tickets, but shaped the problem and shipped the answer.You've worked in a large, mature codebase and know how to be effective in one without a guided tour.You're comfortable with autonomy and ambiguity - you can shape a vague problem into a shippable plan without a spec handed to you.You can mentor and raise the people around you - seniority here is partly about lifting the team, not just your own output.You're a strong full-stack engineer with backend depth, and technology-agnostic - you learn new stacks rather than fear them.You communicate clearly and keep your work visible, because that's what makes a self-directed team function.You're curious about AI as a craft multiplier, not just a buzzword - and senior enough to help a team build good judgement about when and how to use it. What's in it for you? Competitive pension, private health insurance, and paid maternity/paternity leave.A clear career framework and coaching to make sure you're growing, a 10.000 DKK personal development budget and a 'We'll buy you any book you want' policy.We believe collaboration happens best in person, so we have the default of four days a week in office - but with plenty of flexibility for when life happens outside the office too. The inside scoop on Famly Wanna get to know Famly even better? Then have a look at our website to learn more about: our product and our missionour values and beliefsWhat it's like working at Famly and have a look at some of the fun stuff we do Want to get know more about how we work in Famly? One of our builders, Matthew Fitzsimmons talking about how he, and the other builders are working with AI. Our CEO, Anders Laustsen talking about embracing AI Famly is committed to creating a more diverse, equal, and inclusive workforce, building teams that represent a variety of backgrounds, perspectives and experiences. It is a fundamental policy at Famly not to discriminate on any basis or characteristics and celebrate diversity. Everyone is welcome and encouraged to apply.