Staff Frontend Engineer, Feature Management

Responsibilities:
Own the consistency and quality of the core flag surfaces across teams. Set the direction for how shared interactions work, review what teams build on these surfaces, and be accountable for whether the experience hangs together.

Set the agenda from customer evidence. Know the personas who operate these surfaces and what each is trying to finish, work from support, sales, and usage signal rather than from taste, and turn that into a prioritized plan other people find convincing.

Own LaunchPad, our design system, as a lever on the product rather than a destination. Components, tokens, and the pattern layer above them, plus the part that matters: adoption, migration of call sites, lint enforcement, and a measurable adoption baseline.

Track library and platform capability upstream and translate it into product improvement you then drive. Targeting at enterprise scale is a good example, where the interaction patterns available to us now are well ahead of what the product uses. Finding and closing that kind of gap repeatedly is the core loop of this job.

Build the interaction primitives whole classes of workflow depend on: tables, filtering, sorting, comparison, and bulk change as shared capabilities rather than many divergent implementations. Then migrate the product onto them.

Prototype and land the interaction patterns for hybrid human and agent workflows: how a change an agent made is explained, reviewed, and trusted in the product. Build them into shared foundations so teams inherit them.

Be the first line of defense on frontend performance for our highest-traffic surfaces, where the bar is set by our largest customers' scale.

Qualifications:
10+ years of software engineering experience with deep frontend expertise, including a surface or system you owned across multiple teams you did not manage.

Strong with TypeScript and React. Our stack is TypeScript and React on the frontend and Go on the backend, and you should be able to work across the API boundary rather than stop at it.

Experience owning a design system that was genuinely adopted. We will ask about migration, enforcement, and what you did when teams did not adopt it, and we care about those answers more than the component library itself.

Product and UX judgment on top of engineering depth. You start from who the user is and what they are trying to finish, you can trace a workflow end to end across a product, and you can tell real friction apart from your own preferences. You hold that view in a room with designers and PMs as a peer.

A track record of cross-team influence without authority. Point to a standard you set, the coalition you built to get it adopted, and what actually changed in the product.

Judgment about leverage. The defining skill here is picking the few things that unlock the most, out of a backlog that will always be larger than one person.

Real experience with data-dense enterprise product UI: large collections, filtering, permissions, environments, bulk operations, and the performance work that comes with them at customer scale.

A point of view on agents in developer tooling. You have built with LLM tool use, MCP, or agent frameworks in production and have an argument about how agent-driven use changes product design rather than just adding a chat box.

Excellent written communication. Most of your influence will travel as documents, prototypes, and code

Pay:

Target pay ranges based on Geographic Zones* for Level 5:

Zone 1: San Francisco/Bay Area or NYC Metropolitan Area, Boston, Seattle - $214,800 - $295,350*
Zone 2: Irvine, LA, Monterey, Santa Barbara, Santa Rosa, Austin, Portland, Philadelphia, Chicago - $193,400 - $265,870**
Zone 3: All other US locations - $182,600 - $251,020**