Remote-friendly tech companies, by how they actually work

What remote jobs pay — and is it in dollars?

For US-based remote software roles, pay tracks the wider market: roughly $90k–$130k for junior, $130k–$185k for mid-level, and $175k–$240k for senior engineers, with the average landing around $147k. The more interesting question is how a company sets that number across locations, because it decides what you actually take home and in what currency. There are two models:

• Location-agnostic (one global rate). The same pay wherever you live. Automattic and Basecamp pay everyone the same for a given level — a senior engineer earns roughly $130k–$180k whether they're in Manhattan, a small town, or abroad. This is the best deal if you live somewhere cheaper, and the rate is usually set in US dollars.
• Location-based / tiered. Pay adjusts to where you live. GitLab, Stripe and Google define geographic tiers and pay within them, so moving from San Francisco to a lower-cost city can cut 15–25%. GitLab's public formula even multiplies an SF benchmark by a location factor and an exchange rate. Tier-1 (US, Canada, UK) senior engineers run roughly $155k–$215k base; lower-cost countries earn proportionally less.

So “is it paid in dollars?” depends on the model. Location-agnostic companies often quote and anchor pay in US dollars regardless of where you are; location-based ones adjust to your market. Either way, international hires are usually paid in their local currency through an employer-of-record (Deel, Remote, Oyster), even when the band itself is set in dollars. The practical takeaway: a remote-first, location-agnostic company is the strongest deal if you live somewhere with lower costs, since you can earn close to US pay on a local cost base.

How remote changes the way you work

Good remote companies don't just let you work from home; they work differently. The shifts that actually matter:

• Written and async by default. Decisions, updates and docs are written down so people in different time zones can catch up without a meeting. GitLab's public 2,000-page handbook is the extreme example.
• Fewer meetings, more documents. Status happens in writing, not stand-ups; live meetings are reserved for things that genuinely need real-time discussion.
• Judged on output, not hours. Without a desk to sit at, you're measured on what you ship. That suits self-starters and frustrates people who need structure.
• Time zones shape your day. Teams set overlap windows, and the more global the company, the more async the work. Some roles still need a few hours of overlap with a core zone.
• High autonomy, deliberate connection. You manage your own time, and good companies replace hallway chat with intentional rituals — virtual socials, written threads, the occasional in-person offsite.

If you've only ever worked in an office, the adjustment is real: more writing, more self-direction, and less of the ambient social contact you might be used to. The best remote-first companies are built around all this; “work-from-anywhere” policies at office-origin firms can be more of a hybrid muddle.

How to use this list

Sources & method