Staff Frontend Engineer, Feature Management New Remote - US

LaunchDarkly Group; Northern (KY); Remote; USD 180,000 - 240,000; Full time

Job summary

LaunchDarkly is hiring a Staff Frontend Engineer to own the quality and consistency of our core flag surfaces—flag list, targeting, segments, and contexts—across teams. This role requires deep technical depth to guide teams toward common, better paths.

You will work from product backwards, understand user workflows for platform engineers, PMs, release managers, and support engineers, and leverage our design system and component library to unlock new capabilities for customers.

Job description

Staff Frontend Engineer, Feature Management

Remote - US

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