A complete application in a minute — tailored resume and cover letter, ready to send.
HighLevel is hiring a backend engineer to design and build platform components powering Workflows and Conversations. You will own architecture, storage layers, caching, and production health, ensuring scalable performance as the system grows.
We seek 4+ years in backend engineering with Node.js or Go, strong systems knowledge, and experience with asynchronous processing and distributed messaging. This is a remote-first role supporting international teams and customers.
HighLevel is an AI-powered business operating system that gives agencies, entrepreneurs and SMBs the infrastructure to build, automate and scale.
Today, HighLevel supports SMBs across 150+ countries, fueling community-driven growth rooted in real customer outcomes.
To date, businesses operating on HighLevel have generated over $7 billion in ecosystem value, demonstrating the impact of shared infrastructure at scale.
By centralizing conversations, automation and intelligence into one system, we help businesses move faster, reduce complexity and execute efficiently.
Behind the platform, HighLevel powers more than 4 billion API hits and 2.5 billion message events daily.
With 250 terabytes of distributed data, 250+ microservices and over 1 million domain names supported, our architecture is built for performance, resilience and long-term scalability.
With over 2,000 team members across 10+ countries, HighLevel operates as a global, remote-first organization built for speed and ownership. We value initiative, clarity and execution, creating space for ambitious people to build systems that support millions of businesses worldwide. Here, innovation thrives, ideas are celebrated and people come first, no matter where they call home.
Every month, HighLevel enables more than 1.5 billion messages, 200 million leads and 20 million conversations for the more than 1 million businesses we support. Behind those numbers are real people building independence, expanding opportunity and creating measurable impact. We’re proud to be a part of that.
Learn more about us on our YouTube Channel or Blog Posts
The platform underneath our two biggest systems.
Workflows executes 21.5 billion automation actions a month from 3.1 billion enrollments. Conversations moves 2.6 billion messages in the same window. Together they run on thousands of pods, across 50+ kinds of deployments, on top of multiple database engines, GCP Pub/Sub, Cloud Tasks, and Redis, with traffic peaking above 28,000 requests per second and growing double-digit percent every month.
Product engineers build the features. This role owns what the features stand on, the queues, the storage layers, the caching, the infrastructure, and makes sure it holds when the growth curve does what our growth curve does.
We're not looking for someone who knows one layer. We're looking for the engineer who understands the whole vertical: how a query plan behaves at 1.5 TB of indexes, why a pod eviction turned into a message backlog, what a Redis failover actually does to the request path. Databases, infra, cloud, you see through all of it.
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. You’ll 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.
Design and build the platform components Workflows and Conversations run on, queueing pipelines, storage access layers, caching strategies, rate limiters, schedulers
Own your components end to end: architecture, design docs, code, tests, rollout, dashboards, and production health
Go deep on data stores at scale, schema and index design, sharding strategies, replication behavior, and migrations on live systems with billions of records
Work close to the infrastructure: GKE autoscaling, resource tuning, Pub/Sub and Cloud Tasks topologies, and the capacity planning that keeps headroom ahead of growth
Spot gaps in your systems before production does, missing idempotency, unbounded queues, cache stampedes, hot shards, and drive the fixes
Debug the incidents that cross layers, where the answer isn't in one service's logs but in how the pieces interact
Write design docs and RCAs that make the platform's behavior legible to 80+ engineers building on it
…
…
Runtime: Node.js (TypeScript), Go, on GKE
Messaging & async: GCP Pub/Sub, Cloud Tasks, Redis
Storage: MongoDB, Firestore, ClickHouse, ElasticSearch
Observability: metrics, tracing, and alerting you'll help make sharper
4+ years of backend engineering experience, with deep hands-on work in Node.js and/or Go