Aivar Innovations is an AI-native services company and AWS Preferred Partner building governed, production-grade agentic AI systems. We partner with enterprises to deploy intelligent agents that automate complex business processes—from intelligent customer interactions to enterprise knowledge systems.
Experience: 4–8 years | 4+ years building complex, data-intensive or enterprise-grade frontend applications
The Role: You own major parts of the Kubogent frontend end to end: the control surface platform teams, M
L engineers, and application teams use to manage Kubernetes infrastructure, build AI/ML workloads, inspect experiments, operate models,
and understand what is happening across their environments.
What you’ll do
- Own complex product surfaces. Build and evolve dashboards, resource explorers, workflow editors, experiment views, model-serving interfaces, project workspaces, and administrative consoles used across the Kubogent platform.
- Design it, then build it. There is no requirement that every feature arrives as a finished mockup. You take a product problem, understand the workflow, prototype an interaction model, and turn it into a polished production experience.
- Own data-dense infrastructure views. Make clusters, nodes, GPUs, workloads, logs, events, quotas, experiments, and deployments understandable even when customers operate at significant scale.
- Build real-time surfaces. Work with WebSockets, SSE, streaming logs, live status transitions, long-runningoperations, and high-frequency telemetry without compromising responsiveness or rendering performance.
- Own frontend state architecture. Define patterns for server state, local state, optimistic updates, background refresh, async operations, error handling, and long-running workflow state.
- Own the design system. Build reusable components, layout primitives, tokens, interaction patterns, and typedcontracts that keep the platform consistent as the product surface expands.
- Shape multi-tenant UX. Make projects, organizations, clusters, permissions, roles, and resource boundaries clear to users without treating client-side checks as the security boundary.
- Partner directly with backend and platform engineers. Influence API contracts, event models, pagination, filtering, workflow state machines, and product semantics rather than treating APIs as fixed inputs.
- Keep the product fast. Establish performance budgets, profiling practices, virtualization strategies, bundlediscipline, and rendering patterns for large enterprise datasets.
- Raise the production bar. Establish E2E coverage, frontend observability, error monitoring, test strategy, andrelease discipline.
- Set the bar. Review code, mentor engineers, establish frontend standards, and help define what high-quality product engineering looks like at Aivar.
What we’re looking for
- 4+ years building production frontend applications, with real depth in complex, data-intensive, infrastructure,developer-tooling, analytics, or enterprise products.
- Deep React knowledge. Hooks, component architecture, rendering behaviour, memoization, state ownership, performance profiling, and the ability to explain why a component re‑renders.
- Strong TypeScript across UI components, API contracts, shared libraries, schemas, and application state.
- You have built a genuinely hard product surface. Examples could include an IDE‑like interface, workflow builder, graph editor, terminal, monitoring product, analytics console, infrastructure dashboard, collaborative editor, or another interaction‑heavy application.
- You design, you don't just implement. You are comfortable starting from a workflow or product problem instead ofwaiting for final mocks.
- Strong async‑state fluency. WebSockets, SSE, polling, background jobs, live status updates, cancellation, retries, reconnects, and partial failure.
- reconnects, and partial failure.
- Experience with data‑dense interfaces. Filtering, sorting, pagination, virtualization, large tables, timelines, charts, logs, or event streams.
- Design‑system ownership. You have built or significantly evolved a component system other engineers relied on.
- Strong API instincts. You can identify when an awkward frontend experience is actually caused by the wrong backend contract and work with backend engineers to fix it.
- Production discipline. You have introduced or meaningfully improved E2E testing, CI, monitoring, performance measurement, or frontend reliability practices.
- Comfort with cloud‑native concepts. You do not need to be a Kubernetes expert, but concepts such as clusters, pods, deployments, namespaces, GPUs, jobs, logs, metrics, and RBAC should not intimidate you.
- Fluency with agentic coding tools. We expect AI to carry routine implementation work so that you can spend moretime on architecture, interaction design, debugging, performance, and product decisions.
- Experience building developer tools, cloud consoles, observability products, infrastruor internal developer platforms.
- Monaco Editor, xterm.js, React Flow or similar graph/canvas libraries.
- High-frequency charts, log viewers, terminal emulators, or workflow editors.
- Experience with accessibility and keyboard-heavy power-user interfaces.
- Familiarity with Kubernetes, MLflow, Argo Workflows, Ray, Prometheus, or similar infrastructure.
This role may not be the best match if:
- Youprefer working primarily from predefined tickets and pixel-complete design handoffs. We're looking for someone who owns problems, drives solutions, and shapes the product.
- Your experience is primarily marketing sites or straightforward CRUD applications. Kubogent has many highlystateful, real-time, infrastructure-heavy product surfaces.
- You think frontend architecture ends at component structure. State models, API semantics, performance,workflows, failure states, and product interaction design are central to this role.