Sequence - Senior Software Engineer
Requirements
• We hire for ability, not a specific tech stack. Most of the team learned our stack here: • Backend: Kotlin (modular monolith using Http4k, Spring Boot, Exposed, Result4k) • Storage: Postgres, BigQuery • Async messaging: Google Cloud Pub/Sub • Infrastructure: Google Cloud, Terraform • Frontend: TypeScript, React • Monitoring: Google Cloud Monitoring, Sentry • Tools: GitHub, Slack, Notion, Linear • Read our engineering principles • We’re based in London and New York and love spending as much time with our colleagues as possible. We spend three days together in the office, with team lunch on Wednesdays. • We get together twice a year for company offsites.
Responsibilities
• Own revenue-critical event infrastructure. You'll 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 optimization 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'll 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'll 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. • This is a great fit if you... • ✅ Love building systems that scale. You've worked on backends that handle significant load and understand the tradeoffs in designing for throughput, latency, and cost. You know when to optimize 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, backpressure, 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 optimization 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 understand how to model and optimize costs as systems scale. • ✅ Write backend code in strongly-typed languages. Our services run on Kotlin, though you don't need prior experience - many of our engineers learned it here and loved the challenge. What matters is that you're comfortable with type systems and backend development. • ✅ Want to work on something new. The biggest technical decisions still lie ahead. You'll help define our infrastructure strategy, not just implement someone else's vision. • ✅ Thrive in uncertainty. We're an early-stage company. Priorities shift as we learn from customers. Requirements evolve as we understand the problem space. You find this energizing, not frustrating. • ✅ Care about customers and their problems. You'll work directly with customer data and build systems that power their revenue. You'll need to understand not just how to build things, but why they matter. • This might not be the right role if you… • 👎 Prefer staying in your lane. We're small and fast-moving. Engineers here work across different parts of the system and adapt as needs change. • 👎 Want a predictable roadmap. We don't have a year-long backlog of perfectly scoped tickets. We figure out what to build based on customer needs and technical priorities. • 👎 Prefer a slower pace. We're solving real problems for customers today, which means we need to move quickly and make pragmatic tradeoffs. • 👎 Want startup perks with big company stability. We're early stage - that comes with excitement and opportunity, but not the benefits package of an established tech company. • We’re based in London and New York and love spending as much time with our colleagues as possible. We spend three days together in the office, with team lunch on Wednesdays. • We get together twice a year for company offsites.
Benefits
• The salary range for this role is £115,000 - £130,000 + share options • Early ownership of critical infrastructure at a fast-growing company • Real architectural influence - your decisions will shape how we build for years • A collaborative team that values deep technical work and continuous learning • We move fast - typically 1-2 weeks start to finish: • Initial interview (30 mins) • Technical interview (60 mins) • Product interview (30 mins) • System design interview (45 mins) • Founder interview (30 mins) • We've written a detailed blog post about the process with tips about how to prepare.
Apply in one click
Upload My Resume
Drop here or click to browse · Tap to choose · PDF, DOCX, DOC, RTF, TXT