Software Engineer 2 - Frontend, Opportunities

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

Write clear design docs for the features you own, and participate actively in design and code review

What You will Need:

3+ years building and shipping production frontend applications

Strong JavaScript/TypeScript fundamentals, and depth in a component framework — Vue preferred, React fine if you are willing to work in Vue

Real experience with complex, stateful interfaces — not just forms and CRUD screens

Practical grasp of frontend performance: rendering cost, long lists, network waterfalls, bundle size, and how to profile rather than guess

Comfortable consuming and debugging REST APIs, and confident enough in a backend codebase (Node.js/NestJS or similar) to make the change your feature needs

Solid CSS and layout skills, and an eye for whether a build matches the design

Experience shipping and supporting features you wrote — design through deploy

Comfort working with a degree of ambiguity, asking good questions, and driving a task to done

Preferred Qualifications:

• Built a board, kanban, table, grid, or calendar interface with drag-and-drop and large data volumes

• Exposure to CRM, sales, pipeline, or workflow products

• Experience with dynamic or schema-driven UI — rendering interfaces from customer-defined configuration

• Worked on real-time or collaborative interfaces (WebSockets, polling, optimistic concurrency)

• Experience with multi-tenant SaaS, including white-labelled or themeable products

• Familiarity with Vue 3, Pinia, Vite, and end-to-end testing (Playwright or Cypress)

• Backend experience with Node.js/NestJS and MongoDB

• Product instincts and a portfolio or GitHub of shipped work — we will want to look at interfaces you have built

Tech Skill Set:

Vue.js (Vue 3, Pinia, Vite), TypeScript, modern CSS — backed by Node.js (NestJS) APIs, MongoDB, and Redis, running on a distributed microservices architecture over Istio service mesh.

What Success Looks Like:

• Ships Opportunities frontend features to production reliably, with steadily less guidance over time

• Builds interfaces that stay fast and predictable as workspaces grow from hundreds to millions of deals

• Turns fiddly interaction problems into implementations that hold up in real customer use, not just in a demo

• Leaves the component layer better composed and more reusable than they found it

• Makes the backend change their feature needs instead of waiting on someone else

• Debugs production issues independently and leaves behind better instrumentation than they found

• Grows into owning larger, more ambiguous pieces of the product