Staff Engineer - Platform Frontend

About the Role:

We're looking for a Staff Front-End Engineer to own the architecture of our platform UI. This is a core platform role, not a feature role — you'll own the layer every other team builds on: the application shell, our module federation topology, the shared component library, build tooling, and the performance bar that applies across every surface of the product. You'll stay hands-on with code and architecture while setting technical direction across multiple teams and leading multi-quarter migrations without stalling feature delivery. Our stack is primarily Vue 3; strong engineers from React, Angular, or Svelte backgrounds are welcome, and existing Vue experience is a plus.

Responsibilities:

Failure Isolation: Design so a broken or slow remote degrades one surface, not the whole application — with fallbacks, timeouts, and the observability to identify which remote caused an incident.
Release Strategy: Own the deployment and versioning story for independent releases, including contract testing across host/remote boundaries, staged rollout, and fast rollback of a single remote.
Load Performance: Attack bundle size and dependency-graph bloat through code splitting, shared-chunk strategy across federated remotes, preloading/prefetching, and caching/CDN strategy.
Runtime Performance: Attack main-thread cost through long-task analysis, reactivity and re-render cost, list virtualization, and memory leak diagnosis in long-lived sessions. You're the person engineers escalate production-only regressions and render thrash to.
Performance Measurement: Define the metrics that matter (Core Web Vitals, INP, route transition time), instrument them in real-user monitoring, and enforce budgets in CI so regressions are caught before they ship.
Quality Bar: Set and enforce accessibility (WCAG 2.2 AA), internationalization, and cross-browser support through automated checks, not documentation alone.
Technical Leadership: Write proposals that build genuine consensus, review designs and code where decisions are expensive to reverse, and mentor senior and mid-level engineers across the org.

Requirements:

9+ years of front-end development experience. 
Expert-level JavaScript, TypeScript, HTML, and CSS, with a first-principles understanding of the browser — rendering/layout, the event loop, network/caching, and memory.
Deep production experience with a modern component framework. Primarily Vue 3 (Composition API); strong React, Angular, or Svelte experience is welcome if you're willing to go deep on Vue.
Demonstrated architectural ownership — you've defined a front-end architecture and moved a real codebase from one state to another without freezing feature work.
Hands-on production experience with micro-frontends or module federation, including the failure modes. Equivalent experience decomposing a large monolith by other means also considered.
Proven track record optimizing large-scale, complex web applications. Be ready to walk through a specific example with numbers.
Experience with modern build tooling at scale (Vite, Webpack, Rspack, Turborepo, or Nx), with enough depth to debug the build when it breaks.
Working knowledge of accessibility as an engineering discipline — semantics, focus/keyboard behavior, ARIA where genuinely needed, screen reader testing.
Strong written communication. On a remote-first, async team, most of your influence travels as design docs, RFCs, and PR descriptions.
A track record of mentoring engineers and driving change across teams you don't manage.
Nice to have: familiarity with Node.js, server-side rendering, and open-source contributions.

What You'll Lead:

• The target architecture for our front-end, and the migrations that get us there — sequenced into reversible steps, driven with codemods and adoption metrics, agreed across teams rather than imposed on them.
• The application shell and its contracts: bootstrapping, routing, auth-aware navigation, error and loading boundaries, and cross-application state.
• Our module federation topology: host and remote boundaries, shared dependency and singleton management, and version skew between independently deployed remotes.
• The shared component library and design system implementation, with APIs that are hard to misuse and safe to version.