Software Engineering Salaries in Non-Tech Cities: The Remote Premium Is Real

If you're an engineer in Austin, Denver, or Columbus working remotely for a Bay Area company, you're likely earning substantially more than your neighbors doing similar work for local employers. That gap is real, it's wide, and most engineers either don't know it exists — or don't know how to capture it when negotiating.

Secondary tech cities have lower local comp benchmarks — but remote positions at top-tier companies pay to a different standard.

The Gap Is Wider Than You Think

Local tech hiring in Austin or Denver pays real salaries — strong ones, especially compared to a decade ago. But the local benchmark in those markets still sits well below what SF-headquartered companies pay their engineers at home. When a company like Stripe or Cloudflare posts a remote senior engineer role, they're drawing from their headquarters comp band with a location adjustment, not from whatever Austin's market rate happens to be. That's also why the salary transparency laws on posted pay ranges can be misleading if you compare only local listings.

1. 1
   Install Ambitology Cortex
2. 2
   Read as usual
3. 3
   Turn skills to jobs in realtime

CHROME EXTENSIONDownload Ambitology Cortex↗

The result: an engineer in Raleigh earning $175K base from a remote-first Bay Area employer may be $40–$50K above the prevailing local rate for an equivalent role. That gap compounds — in base salary negotiations, in equity refreshes, and in the career positioning that comes from working at a recognizable company. It compounds even more when you factor in cost of living.

This isn't a loophole. It's how remote comp actually works when your employer anchors to their headquarters market rather than yours.

“Your city doesn't write your code. Price your skills against the role, not your zip code.”

How Location-Based Pay Actually Works

Companies fall into two camps, and the difference matters enormously for your take-home.

• Location-adjusted pay bands — the company applies explicit multipliers by metro. SF/NYC get 1.0x; Austin and Denver might get 0.85x; a truly rural address might get 0.75x or lower. Most large tech companies use some version of this model.
• Location-agnostic pay — everyone at a given level earns the same regardless of where they live. GitLab popularized this; Buffer and a growing number of remote-native companies follow it. You get the top-of-market comp no matter where you are.

The critical thing: companies almost never disclose their policy in the job listing. “Remote” in a JD tells you nothing about which camp they're in.

Signs a company leans location-agnostic: their culture documentation explicitly says “remote-first” (not just “remote-friendly”), the team is genuinely distributed across time zones, and their job descriptions discuss comp in terms of role level rather than market rates. Signs of location-adjusted: they ask for your city early in the process, the offer letter explicitly references “location-based comp bands,” or their careers page shows different salary ranges by metro.

Remote-first and remote-friendly are not the same thing — especially when it comes to salary.

The Negotiation Moves That Actually Work

The biggest mistake engineers make here is treating their location as a market signal. It isn't. Your city affects cost of living — it doesn't define what the role is worth. Here's the approach that holds up in practice: Read the posting the way a hiring manager reads a job description to see whether the role is truly remote or quietly location-tiered.

• Anchor to role-level comp, not city comp. Research what the role pays at comparable companies nationally — Levels.fyi, Glassdoor, and Blind give you reasonable benchmarks. Open with a number anchored to those, not to what a local startup is paying.
• Don't volunteer your location until you have to. If a recruiter asks where you're located as a salary-scoping question, you can defer: “I'm flexible on location — I'd prefer to focus on the role's budget first.” That's not evasive; it's appropriate sequencing.
• When the location discount comes, counter with equity. A company that adjusts base salary by location often grants equity at full value. Understand the equity component before you accept any base reduction as a given. Then make the case that your specific skills justify the top of their remote band.
• Ask explicitly about the comp band for the role. Some companies will tell you the range for the role before asking your location. If the band is narrow and the adjustment would put you below your target, now you know — before you've invested weeks in their process.

There are times when accepting a location-adjusted offer is right — when the company has other compelling attributes, the equity upside is real, or the role itself accelerates your career in ways that outweigh the salary delta. But do the math first. Don't accept the adjustment as inevitable just because the recruiter framed it that way.

For a deeper look at negotiating the full compensation package — not just base — see how to negotiate equity in a tech offer and the real salary impact of remote vs. RTO.

The Cities Where the Arbitrage Is Strongest

The widest gap tends to appear in cities with a real tech scene but no dominant Big Tech headquarters effect pulling local salaries up. Austin and Denver have grown, but they're still not San Francisco. Raleigh, Salt Lake City, Pittsburgh, and Columbus follow the same pattern. Strong engineering communities, livable cities, good universities nearby — but no FAANG office setting the local floor.

These cities benefit from lower cost of living without sacrificing amenities. An engineer making $180K remotely from one of these cities has meaningfully more purchasing power than the same $180K in SF — sometimes dramatically more when you factor in housing.

That's the actual play here. Target high-comp remote employers, negotiate toward their headquarters market rate, and live somewhere your dollar goes further. It requires knowing which companies are genuinely remote-friendly on comp, asking the right questions early, and refusing to let your zip code define your market value.

If you want to know which companies are actively negotiable on remote arrangements at the offer stage, the framing matters as much as the timing.

Frequently Asked Questions

What's the difference between location-adjusted and location-agnostic pay?

Location-adjusted pay applies geographic multipliers — your salary reflects your city's cost-of-labor index rather than just the role's market rate. Location-agnostic pay sets compensation by role level, period. The same job pays the same everywhere in the company. Most large tech companies use adjustment bands; genuinely remote-first companies more often go agnostic.

Should I tell a recruiter where I live before getting an offer?

Not until you have to. Disclosing early can hand the recruiter a floor. Keep the conversation on your experience, the role's scope, and the comp range until you have something concrete in hand. Once you have an offer, your location is much easier to navigate strategically — because you already know the number they started with.

Do companies track where remote employees actually live?

For tax withholding and employment law compliance, yes — most do, and you have legal obligations to report your actual work location. Some companies have restrictions on which states or countries they can employ in. Don't misrepresent where you live. The salary arbitrage strategy works within those constraints; you don't need to hide anything to benefit from it.

Is the remote salary premium disappearing with RTO pressure?

For companies requiring in-office attendance, the arbitrage effectively collapses — you're competing on a local market and paying local housing costs. But genuinely remote-first companies are still hiring distributed teams and paying competitively to attract talent from anywhere. The opportunity is narrowing at some companies and holding firm at others. Knowing which is which — before you apply — is the whole game.