Software Development Engineer II
About us
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.
Our people
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.
Our impact
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
About the Role
We’re looking for a Full-stack Software Development Engineer (SDE-2) who brings strong engineering fundamentals, a product mindset, and a bias for action. This role is ideal for someone who takes end-to-end ownership, thrives on building impactful, user-centric features, and is excited by the opportunity to innovate and drive improvements across the stack.You’ll work closely with product, design, and platform teams to deliver features that are data-driven, performant, and scalable. You’ll be expected to contribute ideas, propose solutions, and lead execution—from concept to deployment.
Responsibilities
-
Own the full lifecycle of features: from requirements gathering and UI/UX collaboration to backend API integration and deployment
-
Collaborate closely with product and design to shape features that solve real user problems
-
Implement clean, performant, and accessible UI using React, TypeScript, and modern frontend practices
-
Build and maintain scalable backend services using Node.js/Express, with well-designed APIs and data models
-
Use analytics and product metrics to measure feature success and iterate for improvement
-
Take initiative to improve engineering processes, dev experience, or user experience
-
Maintain code quality through thoughtful architecture, testing, and documentation
-
Proactively address technical debt and participate in refactor or migration efforts
-
Actively contribute to planning and execute reliably under fast-moving product priorities
Requirements
- 3–5 years of fullstack development experience
- Experience in taking features or systems from 0 → 1, and seeing them through to adoption
- Strong command over JavaScript/TypeScript, Vue.js, modern state management, and component-based architecture
- Deep knowledge of Node.js, REST APIs, and databases (MongoDB, PostgreSQL, etc.)
- Product intuition: ability to weigh trade-offs, collaborate with PM/design, and advocate for users
- Passion for metrics and data-driven decisions—you care about impact, not just delivery
- Clear communicator and collaborator, comfortable working across teams
- A track record of taking initiative to solve problems beyond what’s assigned
EEO Statement:
The company is an Equal Opportunity Employer. As an employer subject to affirmative action regulations, we invite you to voluntarily provide the following demographic information. This information is used solely for compliance with government recordkeeping, reporting, and other legal requirements. Providing this information is voluntary and refusal to do so will not affect your application status. This data will be kept separate from your application and will not be used in the hiring decision.
We encourage you to review our Privacy Policy before submitting your application
Skills
As published by lever · 12 questions · 6 written answers
Basics
Resume/CV, Full name, Pronouns, Email, Phone, Current location, Current company, LinkedIn URL, Twitter URL, GitHub URL, Portfolio URL, Other website
Pick from a list (6)
- Are you legally authorised to work in India?
- Will you now or in the future require sponsorship for employment (e.g., work visa, visa transfer) in India?
- Are you an Overseas Citizen of India (OCI) cardholder holding a foreign passport?
- Gender (Select one) optional
- Ethnicity (Select one): optional
- Please mention your official notice period. optional
Written answers (6)
- What is your current CTC (fixed & variable)
- Walk me through the tech stack you work with day-to-day.What languages, frameworks, and databases do you use — and for what purpose? How long have you worked with each, and where would you rate your depth (familiar / proficient / expert)? Have you migrated from one stack to another? What drove that decision? optional
- Describe the most complex backend or frontend problem you've solved — walk me through it. What was the business context and why did it matter? optional
- Tell me about the largest scale system you've worked on — give me the actual numbers. What was the peak load — RPS, DAUs, data volume, message throughput? What was your role — did you design it, inherit it, or scale it up? Where did the system start breaking as load grew, and what were the early warning signs? How did the architecture evolve — what did v1 look like vs. where it is now? What was the most surprising thing that failed at scale that you didn't anticipate? optional
- Walk me through the most impactful performance optimisation you've shipped. How did you first identify the problem — was it user-reported, alerting, or proactive profiling? What tools did you use to diagnose — flamegraphs, query plans, distributed traces? What did you try that didn't work, and why did it fail? What was the measurable before/after — latency p50/p99, throughput, infra cost? optional
- What services or components do you personally own — describe your domain. What does each service do, what are its SLAs, and who are its consumers? How do your services communicate — REST, gRPC, event-driven, message queues? Why that choice? optional