Software Development Engineer II (Frontend) - Opportunities

About HighLevel:
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 are looking for an SDE-2 Frontend-leaning Full-Stack Engineer to build the interface of CRM Opportunities, the deal and pipeline engine at the heart of our CRM. Opportunities is the system of record for every revenue motion our customers run, from lead conversion to closed-won, and the pipeline board is where our customers spend their working day.

This role is frontend-first. The hard problems here are interface problems: a drag-and-drop pipeline board that stays smooth with thousands of cards on screen, optimistic updates that roll back cleanly when a write fails, deal detail views assembled from arbitrary customer-defined custom fields, filters and saved views that hold up under real use, and keeping all of it coherent as several people move deals in the same pipeline at once. Getting this right is the difference between a CRM customers tolerate and one they trust.

You will own frontend features end-to-end in Vue.js, and you will go into the backend as the work requires — extending an API, shaping a response so the client does not have to over-fetch, adding an endpoint that serves the view you are building. You do not need to be a backend specialist; you do need to be unafraid of the server side and happy to work in it rather than filing a ticket. Senior engineers own the broader architecture and are there for design guidance and review.

What You Will Do:

- Own frontend features across Opportunities in Vue.js — the pipeline board, deal detail views, stage and pipeline configuration, filters and saved views, bulk actions, and reporting surfaces
- Build interactions that have to feel instant: drag-and-drop stage moves, inline edits, optimistic updates with clean rollback and clear error states when a write fails
- Make large pipelines fast in the browser — virtualized and windowed lists, pagination and lazy loading, render and re-render cost, bundle size, and time to first meaningful paint on a board with thousands of deals
- Design and maintain client-side state and data-fetching patterns (Pinia/Vuex, caching, invalidation) so the UI stays consistent without redundant round-trips
- Handle concurrency in the interface: live updates when a teammate moves a deal, stale-data detection, and sensible conflict resolution
- Render dynamic, customer-defined schemas — custom fields, custom objects, and per-workspace configuration — without special-casing every variation
- Build reusable, well-composed components, and contribute to the shared design system rather than growing one-off UI
- Work directly from designs, and push back with product and design where an interaction will not hold up in practice
- Extend the backend where your feature needs it: adding or reshaping NestJS API endpoints, trimming over-fetching, and adjusting payloads for the view you are building
- Write tests that matter — component and unit tests, plus end-to-end coverage of the flows customers cannot afford to have broken
- Instrument the frontend: error tracking, real-user performance monitoring, and the event data needed to see how a feature is actually used
- Care about accessibility, keyboard support, responsive layout, and cross-browser behavior as part of shipping, not as a follow-up
- Take part in on-call for the surfaces you own, debug production issues, and contribute to postmortems
-…