The Role: You own the frontend of the Convogent platform end to end: the single surface enterprises use to build, run, and understand their AI conversations, across voice calls, chat, live assist, in-app assist, and post-call analytics.
-
Own the graph-authoring canvases. Drag-drop authoring, per-node config schemas, validation, graph state, undo, versioning, and keeping it all fast as customer graphs grow large.
-
Extend the platform across modalities. We are growing from voice into chat, live assist, in-app assist, and analytics. The frontend is where that expansion is most visible, and you decide what generalises across modalities and what stays specific.
-
Design it, then build it. There is no designer here and no mockup queue. You take a problem, prototype your way to an answer, and ship it. If you have wanted a job where the design decisions are actually yours, this is that job.
-
Own the design system. Component architecture and typed API contracts that make every routine screen cheap and consistent. Aivar builds a family of accelerators, and we want them to feel like one product family, so there is real scope here to shape a system beyond a single app.
-
Own real-time surfaces. Live dashboards, streaming transcripts, and in-browser test conversations over WebSockets, at high update frequency without affecting render performance.
-
Own data-dense views. Conversation history, post-call analytics, evals, and conversation intelligence: filterable, virtualized, and readable at enterprise volume.
-
Own access control on the client. Roles, SSO, and tenant-scoped views, done as UX enforcement over a server-side boundary.
-
Ship into customers' clouds. Keep the build portable across our hosting and theirs, with config injected per environment.
-
Raise the production bar. Establish E2E coverage, error monitoring, and performance budgets.
-
Set the bar. Review, mentor, and define frontend standards for a growing team.
-
4+ years building production frontend applications, with real depth in data-intensive or complex-interaction products.
-
Deep React, hooks, context, component architecture, and render behaviour. You know why something re-renders.
-
Strong TypeScript across components, API contracts, and shared libraries.
-
You have built a genuinely hard interactive surface - a canvas, graph editor, builder, timeline, or equivalent. Tell us about it; it is the thing we most want to hear.
-
You design, you don't just build. We have no UX designer. You will get a problem, not a mockup, and you decide what the screen should be. You will also shape the design system itself: what an Aivar product looks and feels like as that system spreads across our accelerators.
-
Real-time state fluency: WebSockets or SSE, and complex async state.
-
Design-system ownership, You have owned a component system other engineers built on. A strong plus if you have shared one across more than one product or team - tokens and theming, versioning and adoption, and the governance of keeping products consistent without blocking them.
-
You have introduced production discipline. You have stood up an E2E suite, a CI pipeline, error monitoring, or a performance budget somewhere it did not exist.
-
Fluency with agentic coding tools. We expect AI to carry routine frontend work so that you can carry the
This role may not be the best match if.
-
You prefer working from predefined ticket queues and design handoffs. We're looking for someone who owns problems, drives solutions, and shapes the product.
-
Your expertise is primarily in marketing websites or conventional CRUD applications. This role demands experience building scalable, user-centric products with technical depth.
React.js, TypeScript, Vite/Next.js, Zustand/Redux Toolkit, React Query, TailwindCSS, Radix UI / shadcn, WebSockets/SSE, REST/GraphQL, Jest, Cypress/Playwright, GitHub Actions, AWS (CloudFront, S3, Amplify), Docker
