Staff Frontend Engineer, Feature Management

About the Job:

LaunchDarkly is hiring a Staff Frontend Engineer to own the quality and consistency of our core flag surfaces: the flag list, flag targeting, segments, and contexts. These are the pages our customers live in. They grew up across several teams over several years, and bringing them into one coherent experience is the work. Consistency is the mandate here. You will look across every team’s work on these surfaces and you will need to be comfortable telling a team that what they are building already exists, or should not be built the way they are building it, and then making the better path easy enough that they take it. That standing comes from technical depth rather than authority you are given.

You will work from the product backwards, and knowing who you are building for is most of the skill:

• The platform engineer standardizing flag hygiene across two hundred services.
• The product manager checking what is live before a customer call.
• The release manager running a staged rollout under change control.
• The support engineer tracing why a customer saw a variation last Tuesday.
• The developer who delegates flag work to an agent, then reviews it.

These people need different things from the same screens, and you will know their workflows well enough to tell which friction is worth fixing. Your levers are the shared frontend foundations underneath those surfaces: our design system, the interaction primitives whole classes of workflow depend on, and the platform capability we can pull in from upstream. When new capability lands in our component library, you are the person who knows the product well enough to say what it unlocks, which customer complaint it closes, and what it takes to get it into the product.

That last persona is where the role turns forward-looking. An agent makes a change, then a person arrives to verify it and decide whether to trust it. They need it explained, with the blast radius legible before it lands. You will prototype those patterns and build the good ones into the foundations. Design and product are your closest partners in that, alongside the Enterprise and Foundation Feature Management teams who build on what you own.

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 libr…