Senior Software Engineer

About Sequence

Backed by a16z and Salesforce Ventures, Sequence is reinventing the accounts receivable category, building a flexible toolkit to help B2B finance teams to scale their revenue collection infrastructure.

The team behind Sequence has decades of experience building and operating category‑defining marketplace, machine learning, fintech, and enterprise software companies. We are no ordinary start‑up; the maturity of our leadership and technology means we are operating at a lightning fast pace. This is a fantastic opportunity to be a part of the next wave of innovation for the CFO office, doing your best work with talented, ambitious and creative teammates.

Sequence is the ultimate billing and revenue stack for B2B companies. We help our customers design and iterate on their pricing and revenue flows, so they can stay completely focused on their mission without worrying about billing.

At the end of your career, we want you to look back at your time with Sequence and say it was the best job you ever had.

We're looking for software engineers with strong backend and cloud infrastructure experience to build the systems that power billing for modern B2B companies.

You'll own revenue‑critical infrastructure—the kind where correctness isn't negotiable and downtime isn't an option. Our usage events platform processes every merchant action that determines how their customers get billed, making it one of the most critical systems we run. You'll work on the evolution of this platform to handle exponential growth while maintaining perfect accuracy.

This is a rare opportunity: you're joining early enough to make fundamental architectural decisions, but late enough that real customers depend on what you build. You'll design systems that process high‑velocity event streams, make technical decisions that balance cost and performance at scale, and build infrastructure that never compromises on reliability.

• Own revenue‑critical event infrastructure. You will work on systems that process customer usage data on which billing and invoicing depend. Design event streaming pipelines that handle high throughput with low latency. Build robust systems where data accuracy is non‑negotiable and uptime is measured in nines.

• Design scalable data systems. You'll work with event streaming architectures, building sophisticated ingestion pipelines and query optimisation strategies. Our event volumes grow with every new customer, so you'll architect systems that scale efficiently while keeping costs reasonable.

• Shape our backend architecture. You will tackle our most complex technical challenges and set the standards for how we solve them. Our services run on Kotlin with Spring Boot, and you'll have significant influence over architectural patterns and how we approach infrastructure problems.

• Build for the next phase of growth. You will design systems that work beautifully today and scale to 10x the load tomorrow. This means thinking about data storage strategies, horizontal scalability, and how your architectural decisions affect performance as volume increases.

• Drive impact on a small team
  . We've built an engineering culture around collaboration, learning, and shipping. You'll have significant influence on what we build, how we build it, and how we work together.

• ✅ Love building systems that scale. You've worked on backends that handle significant load and understand the trade‑offs in designing for throughput, latency, and cost. You know when to optimise and when good enough is actually good enough.

• ✅ Have strong experience in event‑driven architectures. You've built pub/sub systems, worked with event streaming platforms, and understand the nuances of event delivery semantics, back pressure, and ordering guarantees.

• ✅ Think deeply about data systems. You've worked with analytical databases or OLAP systems. You can reason about columnar storage, indexing strategies, and query optimisation without needing a whiteboard.

• ✅ Own your infrastructure. You've provisioned cloud resources, written infrastructure‑as‑code, and made architectural decisions that balance competing constraints. You…