About the role
We are building a multi-tenant platform that Fortune 1000 L&D teams use to procure, configure, and deliver premium executive education inside the tools their people already use.
What you'll own
Front-end architecture
- Next.js application architecture across multiple product surfaces in a single monorepo — routing, rendering strategy, server versus client boundaries, and the shared package structure.
- The component library and design-token layer, built with the product designer, so that brand precision is enforced by the system rather than by review.
- State, caching, and data-fetching conventions, including the real-time model that keeps multiple personas in sync when one of them acts.
- Type safety across the API boundary — shared types, generated clients, and a contract that breaks loudly in CI rather than quietly in production.
Product delivery
- Ship customer-facing surfaces end to end, from configuration and approval workflows through cohort management and the embedded learner experience.
- Translate high-fidelity, brand-precise design into a performant, accessible production front end.
- Build AI-assisted interfaces against the Anthropic Claude API — streaming responses, intermediate states, and graceful failure when a model call does not return what you hoped.
Standards and craft
- Set the accessibility bar (WCAG 2.1 AA as a floor — enterprise procurement will ask) and the performance budget, and enforce both in CI.
- Front-end testing strategy: component, integration, and the small number of end-to-end tests that actually earn their maintenance cost.
- Instrument every surface against the platform's canonical event contract — the product analytics asset depends on it and cannot be backfilled.
- Mentor the front-end engineers who join after you, and review their work to a consistent standard.
What we're looking for
Must-have
- 5+ years production front-end engineering, with 2+ on a complex, data-dense B2B or enterprise application.
- React 18+ and TypeScript 5+ at depth — hooks, context, concurrent rendering, memoisation — and the judgment to explain when each is the wrong tool.
- A modern React meta-framework in production — our front end is Next.js 14 with the App Router — server and client components, streaming and Suspense, route handlers, caching and revalidation. Remix or Vite + React Router are accepted backgrounds; App Router experience is strongly preferred, because its caching model is where teams lose weeks.
- A design system or component library you built or substantially owned — design tokens, composition API, variant modelling, and versioned release to other engineers. We use shadcn/ui and Radix primitives; Headless UI, MUI, or your own primitives are accepted backgrounds.
- Modern CSS at a high standard — we use Tailwind. CSS-in-JS or CSS Modules are accepted backgrounds, but we expect real fluency in flexbox, grid, container queries, and responsive typography regardless of the tool.
- State and data-fetching architecture — TanStack Query, SWR, or RTK Query in production, and a considered position on server state versus client state.
- Accessibility to WCAG 2.1 AA — semantic HTML, ARIA only where genuinely needed, keyboard navigation, focus management, and automated testing with axe or equivalent. Enterprise procurement audits this.
- Front-end testing — Vitest or Jest with React Testing Library, plus Playwright or Cypress for the small number of end-to-end tests that earn their maintenance cost.
- Agentic AI development tooling in daily use — we use Claude Code; Cursor or equivalent is fine.
Nice-to-have
- L&D, EdTech, or HR-Tech background.
- Real-time UI experience — WebSockets, server-sent events, or optimistic update models.
- Streaming LLM interfaces, or other UIs where responses arrive progressively and can fail midway.
- Multi-tenant theming, white-labelling, or embedded/iframe rendering inside a third-party host application.
Front-end performance work with measured outcomes, not just Lighthouse screenshots
What success looks like — first 90 days
- Days 1–30 — Front-end architecture and conventions documented and in place; component library scaffolded; first product surface shipping.
- Days 31–60 — Design system consumed across surfaces; accessibility and performance budgets enforced in CI; real-time state model live.
- Days 61–90 — Second and third surfaces shipping against shared components; front-end testing strategy in place; first front-end hire onboarded.
Our stack
Frontend: Next.js 14, TypeScript. Backend: FastAPI, Python 3.12. Data: PostgreSQL with TimescaleDB, Pub/Sub, dbt. Infra: GCP (Cloud Run, Cloud SQL, Pub/Sub, Memorystore Redis, Vertex AI Vector Search), Terraform, Workload Identity Federation. Intelligence layer: Anthropic Claude API. Tooling: Claude Code as a first-class part of our development workflow.
A note on scope. This is a hands-on senior IC role with architectural scope, not an engineering-management role. Visual and interaction design is owned by a product designer you will work with daily — you are their closest partner, not their replacement. Backend services, identity, and the integration layer are owned by separate hires.
