Senior Full Stack Engineer, Enterprise, Feature Management

About the Job:

The Enterprise team builds LaunchDarkly for the customers who push it hardest. Global banks, national health systems, and Fortune 100 manufacturers run us across thousands of engineers and tens of thousands of flags, inside audit and change control processes most software never meets.

That scale breaks things that work fine everywhere else. A permissions model designed for a hundred users can be the reason a rollout to twenty thousand stalls. Volume creates a different class of problem, where a flag payload that costs nothing to deliver once gets expensive across a large service fleet. Your work is to find where a current design stops holding and build what replaces it. You will own that end to end, in Go on the backend and TypeScript and React on the frontend.

The problems fall into a few areas:

Governance and access control. Roles, permissions, approvals, and audit trails that satisfy a regulator.

Scale and performance. Finding the limit before the customer does, then changing the design rather than tuning around it.

Programmatic control. Our public API, Terraform provider, and configuration surfaces, so a platform team can run LaunchDarkly as infrastructure.

Resilience under real constraints. Data residency, regional isolation, and sane behavior when a dependency is degraded.

Enterprise runs closer to its own business than most product teams. Roughly half the roadmap traces back to requests from named customers, so you will often know who is waiting on your work and what it unblocks for them. You will speak with those customers directly. The other half is larger forward-looking work, where the brief is a capability our biggest customers will need rather than one they have already asked for.

Responsibilities:

Own features end to end: problem framing with your PM and designer, technical design, implementation across backend and frontend, rollout, and the operational life of the thing after it ships.

Design for enterprise constraints from the start. Permissions and access control, approval and audit requirements, data residency and regional isolation, and the behavior of the system when a region or dependency is degraded.

Find and fix scalability and performance limits before customers do. Identify where a current design stops holding at the top end of our customer base, quantify it, and lead the work to change it.

Make LaunchDarkly manageable at fleet scale. Extend our public API, Terraform provider, and configuration surfaces so a platform team can operate LaunchDarkly as infrastructure rather than click through it.

Work directly with customers. Join escalations and discovery calls, read the support and account signal, and turn a specific customer's problem into something that serves the whole segment rather than a one-off.

Raise operability of what the team owns. Observability, runbooks, and participation in the on-call rotation, plus the follow-through after an incident.

Drive alignment beyond your own team. Enterprise depends on and is depended on by several other teams, so surfacing a misalignment early and getting the right people in a room is a real part of the job at this level.

Mentor and review. Give substantive review on specifications and pull requests, including for engineers on neighboring teams, and help newer engineers get faster.

Qualifications:

6+ years of professional software engineering experience, with a track record of features you drove from design through production.

Genuine full stack ability. Strong in a statically typed backend language and comfortable owning frontend work rather than handing it off. Our stack is Go on the backend and TypeScript and React on the frontend.

Experience building for enterprise customers. Multi-tenancy, roles and permissions, SSO and identity, audit logging, approval workflows, or compliance requirements in a production product.

Demonstrated work on scale and performance problems: finding a bottleneck, measuring it, and changing the design rather than tuning around it.

API design judgment. You have built interfaces other engineers depend on and have dealt with the consequences of getting one wrong.