SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 172,600 - 263,670 / annual
LaunchDarkly's Enterprise team builds feature management infrastructure for the world's largest organizations—global banks, national health systems, Fortune 100 manufacturers—running thousands of engineers and tens of thousands of feature flags within strict audit and change control processes.
As a Senior Full Stack Engineer on the Enterprise team, you will own features end-to-end: from problem framing with product and design, through technical architecture, implementation across Go backend and TypeScript/React frontend, rollout, and ongoing operations. You'll tackle problems that emerge only at massive scale—permissions models that break at thousands of users, flag payloads that become expensive across large service fleets, and resilience requirements under real-world constraints.
Key focus areas include governance and access control (roles, permissions, approvals, audit trails for regulators), scale and performance (finding limits before customers do and redesigning rather than tuning), programmatic control (public APIs, Terraform providers, configuration surfaces for platform teams), and resilience under constraints (data residency, regional isolation, graceful degradation).
You will work directly with named customers on roughly half the roadmap, understanding their needs and translating specific problems into general solutions. The other half involves forward-looking capability work for anticipated enterprise needs. You'll drive alignment across dependent teams, mentor engineers, participate in on-call rotations, and maintain high observability and operability standards.
Required: 6+ years professional software engineering with shipped features; genuine full-stack ability in statically typed backend languages and frontend work; production experience building for enterprise (multi-tenancy, permissions, SSO, audit logging, compliance); demonstrated work on scale and performance problems; API design judgment; comfort with customer conversations; ability to collaborate across time zones (EMEA stakeholders); and clear technical writing for design documents.
