Staff Engineer - Distributed Systems
HighLevel (company site, opens in a new tab)10+ yrsRemoteDirect career pageEst. 35–60 LPA
Posted on 25 Sept
Reach people at HighLevel
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at HighLevel you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Lead architecture and health of an extremely large-scale distributed messaging system handling billions of messages monthly, ensuring reliability and scalability at high growth rates.
- Own and approve critical system designs, proactively identify and resolve architectural vulnerabilities and single points of failure before they cause incidents.
- Contribute hands-on to complex codebases (Node.js, Go, microservices) about 25-33% of the time, driving resilience, backpressure, and capacity model improvements while mentoring engineering teams.
Minimum Requirements
- 10+ years engineering experience owning large-scale distributed systems with billions of daily events.
- Deep expertise in queueing/async architectures, failure modes, and multiple storage engines (SQL + NoSQL), with production Kubernetes experience at scale.
- Proficiency in Node.js and/or Go for prototyping and shipping critical fixes.
- Work Experience Required: 10+ years of engineering experience
Ideal Candidate Profile
- Has owned critical distributed systems in production through outages, migrations, and scaling challenges, evolving design practices from those experiences.
- Operates at a staff-level scope with recognized authority for difficult system design questions and cross-team influence based on rigor rather than title.
- Exceptional at anticipating failure modes, writing influential design docs and RCAs that shape long-term architecture, and improving team technical decisions through data-driven critiques.