Software Development Engineer II - Conversations

Job Summary

The systems that run millions of businesses.

Every month, 2.6 billion messages flow through our platform. Our automation engine enrolls 3.1 billion contacts and executes 21.5 billion workflow actions in the same window - with API traffic peaking at 28,000+ requests per second. If these systems lag, businesses lose leads. If they go down, people lose income.

You havent built at this scale yet. Thats fine - almost nobody has.

What were hiring for is the engineer who reads those numbers and feels pulled toward them. Who wants to know what a queue looks like when its absorbing a 10x burst, what an index does at 1.5 TB, what "eventually consistent" actually means when a customer is staring at the screen. Youll work on real production paths from week one - with senior engineers around you whove broken and fixed these systems before. Youll build. Youll break things. Youll learn faster here than anywhere else.

Team and System Overview

The Conversations organization powers multi-channel communication across SMS, Email, WhatsApp, and DMs - handling over 2B messages each month. The Threads & Composer team owns the inbox and composer surfaces, and the backend services that deliver and store those interactions. Youll work across Node.js microservices, GCP-based infra (GKE, Pub/Sub, Cloud Tasks), and MongoDB/Firestore storage layers, ensuring every message and UI state stays consistent, fast, and recoverable.

Responsibilities

• Build and ship features in Node.js / Go services that sit on real production paths - your code handles live traffic, not toy problems
• Own well-scoped services and components end to end: code, tests, rollout, and monitoring
• Work with SQL and NoSQL data stores - writing queries, adding indexes, and learning why the schema looks the way it does
• Get hands-on with queues, caches, and rate limiters - the building blocks of every system here
• Ship Vue 3 UIs that consume your own APIs - clean components, sane state management, and realtime updates that dont flicker or drift
• Write design docs for your features and defend them in review - clear thinking, honest trade-offs
• Join the on-call rotation with backup from senior engineers - incidents are where the deepest learning happens
• Ask questions relentlessly, absorb feedback from code reviews, and level up fast

Requirements

• 2+ years of backend engineering experience with strong fundamentals in Node.js, Go, or a comparable language - and the drive to go deep in ours
• Working knowledge of queues or async processing - youve used Pub/Sub, Kafka, RabbitMQ, or similar, and want to master delivery semantics, ordering, and backpressure
• Genuine interest in distributed systems - you understand the basics (idempotency, retries, consistency trade-offs) and are hungry to learn the rest by building
• Hands-on with Redis or another cache/in-memory store, even at small scale
• Comfortable with SQL or NoSQL databases - you can model data, write efficient queries, and reason about indexes
• Proficient in Vue 3 or a similar modern frontend framework - solid component design and real experience with state management (Pinia, Vuex, or equivalent)
• You write tests as a habit and can put your design thinking into a clear doc
• AI-native builder - you code with agents daily and are pushing to get accurate, production-quality output from them

Technical Environment

• Languages: Node.js (TypeScript), Go
• Frontend: Vue 3, TypeScript, Pinia, Vite, Tailwind
• Storage: MongoDB, Firestore, Redis, ElasticSearch, ClickHouse
• Infra: GCP - GKE, Pub/Sub, Cloud Tasks
• CI/CD: GitHub Actions, Docker, Kubernetes

Why This Role

Most engineers spend years at companies where "scale" means a few hundred requests per second - and never find out what theyre capable of.

Here, the systems are the teacher. Every design decision has a visible consequence at billions of events a month. Every incident is a masterclass. Youll sit in architecture reviews with staff engineers debating storage engines and consistency models - and within a year, youll be contributing to those debates, not just watching them.

If you optimize your career for learning velocity, there is no faster track than this.

On AI

Were past the debate. AI is part of how we build - and we expect you to be hungry