You'll be responsible for the reliability, performance, and developer experience of a React-based platform that includes a visual flow builder (React Flow), a real-time agent dashboard, analytics views, and SDK-driven chat widgets.
What You'll Work On
Platform UI & Flow Builder: Our clients use a visual drag-and-drop flow builder (built on React Flow) to design complex conversational journeys — branching logic, API integrations, multilingual nodes, voice-specific configurations. You'll own this critical piece, improving usability, performance (some flows have 200+ nodes), and extensibility.
Component Architecture: We have a growing library of React components powering the dashboard, analytics, and configuration screens. You'll drive standardization, reusability, and consistent design system adoption across the product.
API Integration Layer: Our backend APIs are in Go and use Protobuf for data exchange. You'll work with generated client stubs, handle serialization/deserialization, manage API state (caching, optimistic updates, error handling), and collaborate with backend engineers on contract design.
Build & CI/CD Pipeline: Our build tooling runs on Vite, with package management via Yarn, and CI/CD through Argo. You'll own build performance, deployment reliability, and help evolve our pipeline — feature flags, preview deployments, bundle analysis, etc.
Performance & Observability: As our platform scales (more clients, more complex flows, real-time data), you'll be responsible for frontend performance — bundle size, rendering performance, memory leaks in long-lived sessions, and setting up frontend observability (error tracking, performance monitoring).
Cross-functional Collaboration: You'll work closely with the backend team on API contracts, with QA on test coverage strategy, with DevOps/SRE on deployment processes, and directly with product and design on UX decisions.
Must-Have Non-Technical Qualities:
Ownership mindset — this is the most important trait. When something breaks, you don't wait to be told. When a technical decision needs to be made, you make it (and can justify it). When a deadline is at risk, you flag it early with options, not excuses
Ability to work independently with minimal supervision. You should be comfortable being the only senior frontend person in the room, making architecture calls, and defending them
Clear communication — you'll be interfacing with backend engineers (Go), QA, product, and sometimes directly with clients' technical teams. You need to explain frontend constraints and tradeoffs clearly
Production-first thinking — you care about what happens after the PR is merged. Error handling, edge cases, monitoring, graceful degradation
Good-to-Have:
Experience building real-time UIs — WebSocket-based dashboards, live agent consoles, streaming data
Familiarity with WebRTC or SIP-based browser integrations (we're a voice-first platform — browser-based agent tooling may involve these)
Experience with micro-frontend architectures or module federation
Exposure to design systems — building or maintaining a shared component library with Storybook or similar
Experience with frontend testing at scale — not just unit tests, but integration tests (Cypress, Playwright), visual regression testing
Familiarity with Kubernetes-based deployment environments — understanding how frontend assets are served, CDN caching, container-based builds
Prior experience in B2B SaaS or enterprise product development where you've dealt with role-based access, multi-tenant UIs, and complex configuration screens