Say you are a senior full stack engineer in Denver, and you apply to a remote US role at LaunchDarkly. Your friend in Seattle applies to the exact same posting. If you both get offers at the bottom of the band, your friend's starts about $28,800 higher.
Nobody is hiding this. It is written in the job post, which is not a given.
Three zones, one job
LaunchDarkly makes feature flagging software, the switches that let a team turn code on for some users and off for others without a deploy. Its "Senior Full Stack Engineer (Multiple Positions)" role is listed as "Remote - US", and the post publishes three pay ranges:
| Zone | Where | Range |
|---|---|---|
| Zone 1 | San Francisco/Bay Area, NYC metro, Boston, Seattle | $191,800 to $263,670 |
| Zone 2 | Irvine, LA, Monterey, Santa Barbara, Santa Rosa, Austin, Portland, Philadelphia, Chicago | $172,600 to $237,270 |
| Zone 3 | All other US locations | $163,000 to $224,070 |
The Staff Engineer posting works the same way, from $182,600 in Zone 3 up to $295,350 at the top of Zone 1.
The steps are tidy. Zone 2 is about 10% below Zone 1, and Zone 3 about 15% below. The post adds the usual line: "Exact compensation may vary based on skills, experience, and location."
What that does to the number you see
Here is the catch for anyone comparing jobs. Our board shows one range per role, and for a zoned post that range is the bottom of Zone 3 to the top of Zone 1. So LaunchDarkly's staff role looks like a $182,600 to $295,350 job, a spread of about $113,000. If you live outside the thirteen named areas, your actual range is $182,600 to $251,020.
That is not LaunchDarkly being sneaky. The full table is right there in the post. It is a reminder to scroll down before you anchor on the big number.
Most of the roles look like this
On October 6, 2026 we had 28 open roles on file for LaunchDarkly, and 26 of them publish pay. That is 93%, against roughly half of the tech roles we track. The two without a range are a sales engineering role in India and a solutions engineering role in EMEA, both hybrid.
Of the 28:
25 are remote, and every one of those is restricted to the US (23 say "US only", one "US East", one "US locations").
1 is onsite: a developer advocate role in Oakland that asks you to attend Bay Area developer events several times a week.
21 are senior, 7 mid-level, none junior.
The engineering roles are mostly backend and platform work: observability, identity and access, flag delivery, billing, experimentation. The stack named most often is Go (17 of the 28), then Python and AWS (14 each), and Rust in 9. A feature flag service sits in the hot path of its customers' apps, so it is not a surprise to see the systems languages near the top.
Zones, or one number?
Location-based pay is a choice, and companies make it in both directions. Supabase, one of our earlier spotlights, pays the same wherever you are. LaunchDarkly pays by where you live, and tells you exactly how.
We do not think one of those is obviously right. Zones mean someone in a cheaper city earns less for the same work. A single number means the company is either paying above local rates in cheaper places or below them in expensive ones. What we do think is that publishing the table is the honest version of zoned pay, and it is not something every company that adjusts pay by location does.
If you are in Zone 3, the practical move is to use the table. You can see the band your Seattle counterpart is hired into, so you know roughly how far you are being asked to discount, and you can decide whether the cost of living gap really covers it.
Who this is for
If you are a senior backend or platform engineer in the US, comfortable in Go, and you want a remote role with the pay written down, LaunchDarkly is one of the clearer options on the board. If you are outside the US, every remote role it has open right now is closed to you.
Open roles, stack and pay are on LaunchDarkly's page on Remoet, and starring it means its next roles come to you.
What we could not confirm
We read two of LaunchDarkly's postings in full (the senior full stack and staff engineer roles) and the zone table above comes from them. The other roles' ranges are from our own extraction, which stores one range per role, so we have not checked that every one of them is zoned the same way. We found no public handbook or description of LaunchDarkly's interview process, so we have not described one. Everything is as of October 6, 2026.
If you work at LaunchDarkly, or interviewed there recently, and something here is off, tell us in Discord.
