Senior Software Engineer, Backoffice Platform

Our everyday digital experiences are in the middle of a realtime revolution: chatting alongside a livestream, getting realtime financial updates, or working with colleagues in a shared online space. Consumers now expect realtime as standard, and Ably powers a large part of it. We put developers first. Our products help teams build, extend, and deliver realtime digital experiences, delivering over 700 billion messages to more than 2 billion devices every month. Teams at HubSpot, Fin, Dialpad, NASCAR, Sportsbet, and General Motors all build on Ably. Working at Ably means helping build the infrastructure that will shape the next generation of the internet. More of what people do online is becoming live, shared and interactive, which only makes what we build more relevant and more necessary. AI is the latest place that shows up. There's still so much to build, and we'd like your help with it. About this role Ably's back office platform is where every customer account is managed. It holds the packages, entitlements and limits that determine what each of our customers can do, and it runs the tooling our Finance, Customer Success and Support teams rely on every day. This is an opportunity to take ownership of a platform the whole business depends on, with the scope to decide how it should work rather than maintain someone else's decisions. You'll be hands-on across entitlements, administration tooling and billing, working closely with our Head of Infrastructure and our Developer Experience team, and directly with the teams who use what you build. We work in an AI-first engineering culture: AI tools are part of how we plan, prototype, and iterate, though engineers own every technical decision, and human judgment is the quality bar that everything is measured against. Day to day you will • Run the back office platform. You'll look after the systems holding every customer's packages, entitlements, limits and billing, along with the tooling Finance, Customer Success and Support use daily. • Solve problems, not tickets. You'll be handed a problem, usually described by the people living with it rather than specified in advance, and you'll own the design as well as the delivery. • Make admin work for the people who use it. Staff should be able to see what a customer has bought, how they're billed and what limits they have, make a change, and trust the result, without needing to understand our internal models. • Partner across the company. Finance, Customer Success, Support and Engineering are all your users. You'll learn their processes well enough to question a requirement rather than just build it. • Champion AI-assisted development. You'll use LLMs and AI tools for planning, spikes, code and docs to accelerate velocity, while owning correctness and architectural quality yourself. • Make the systems explain themselves. Why a customer has the limits they have, and what produced an invoice, should be answerable without an engineer digging through code. • Set the testing bar. You'll decide what good looks like where mistakes cost money, build the harness to match, and hold the line on production readiness. We'd love to talk if you have • Experience working in large, established codebases, and the judgement to tell when a system should be extended, reworked, or replaced outright, including the confidence to say so unprompted. Ruby on Rails will help you get to grips with what we have today, though we care more about your range than any one language, and what you build here may well not be Rails. • A track record of shaping architecture inside a system you inherited, including the data ownership decisions that come with drawing a boundary. • The ability to self-start, work through ambiguity, and make good decisions without a lot