In early 2023, Microsoft announced that remote work for its employees would shift to a hybrid-required model for most teams. Amazon followed with a full return-to-office mandate in late 2024. Meta, Google, and Salesforce all tightened their remote policies in similar windows. If you’ve been tracking this, none of it was subtle.
And yet. The number of fully remote tech job postings in 2026 is still meaningfully higher than it was in 2019. The floor shifted upward during the pandemic and didn’t fully come back down. The question isn’t whether remote tech jobs exist. It’s where they are, which companies are genuine about it, and what you’re trading off when you optimize for remote over everything else.
Where the remote roles actually are
The geography of remote tech work in 2026 breaks roughly into three categories.
First, startups under about 47 employees. This is still the most reliable source of genuinely remote-first roles. Companies this size often don’t have a real office, or have a small headquarters where the founding team sits while the rest of the team is distributed. They’re not tolerating remote, they’re built around it.
Second, mid-market B2B SaaS companies. These companies (think: $30M-$300M ARR, 100-500 employees) often have strong remote cultures because they were built or scaled during 2020-2022 and structured around asynchronous work. Customer success, engineering, sales, and data roles at these companies are frequently remote.
Third, specific roles at larger companies. Even organizations that have mandated office attendance for most employees often carve out exceptions for specialized technical roles where the candidate pool is thin. Senior security engineers, ML researchers, certain platform engineering specialties. If the role is hard to fill locally, the company often makes exceptions.
The LinkedIn Economic Graph research team has tracked remote job postings as a percentage of total listings since 2020. Their data shows the share peaked in 2022 and has declined since, but stabilized in 2024 at roughly 2-3x the pre-pandemic baseline. That stabilization is the thing worth noting: this isn’t a fad that fully reversed.
The roles where remote is genuinely common
Not all tech roles have equal remote availability. Some honest data points:
- Software engineering (especially backend and platform): still the most remote-friendly discipline. The work is inherently asynchronous and doesn’t require physical presence.
- Data engineering and analytics: similar story. Most of the work happens in notebooks and SQL editors. Async-friendly.
- DevOps and SRE: strong remote availability, particularly at companies with infrastructure on public cloud.
- Technical writing and developer relations: very commonly remote. Often explicitly remote-first.
- Product management: more mixed. PMs who work closely with on-site engineering or design teams often have office requirements. PMs at distributed product companies are often fine remote.
- Sales and customer success: heavily dependent on company culture and deal size. Enterprise sales is often hybrid or in-office. SMB-focused sales is more commonly remote.
What “remote” actually means at most companies
This is worth slowing down on, because the word gets used imprecisely.
Some companies are remote-friendly: they’ll let you work remote, but the culture assumes you can come into an office on short notice for team weeks, onboarding, and key meetings. You might travel 4-8 times per year. Some people find this a good balance. Others find the travel requirements don’t fit their life.
Some companies are remote-first: processes, documentation, and communication are designed for asynchronous distributed work. These are rarer but they exist and they’re worth finding.
Some companies are remote-tolerant: they allow it reluctantly for specific hires and the culture doesn’t really support it. These are the jobs where you end up feeling like you’re missing things, getting passed over for projects, and eventually either moving closer or leaving.
The question to ask in interviews isn’t “are you remote-friendly?” It’s “what percentage of your leadership team is fully remote?” and “how do you run your all-hands and planning meetings?” The answers reveal a lot more than the official policy.
The salary question
Remote tech jobs used to come with a geographic pay adjustment at some companies, meaning a San Francisco-based company would pay a remote engineer in Ohio less than an on-site engineer in SF. This practice is still around but it’s become less common as companies that tried it found it created retention problems.
The more common current approach is market-based pay tied to your local or regional market, or national banding where everyone in a role gets paid the same regardless of location. If geographic pay adjustment is a dealbreaker for you, it’s a reasonable thing to ask about early in the process before you’ve invested time in multiple interview rounds.
The Bureau of Labor Statistics 2024 occupational data puts median software developer pay at $132,270 annually. Remote roles in competitive markets often exceed this, though the range is wide. Asking about comp in the first recruiter call is now much more normal than it was 5 years ago. Do it.
Finding the real remote jobs in a noisy market
Job boards list a lot of roles as “remote” that are not actually remote. “Remote in [specific state]” with a list of 3 states. “Remote with quarterly travel” meaning 8 weeks per year. “Hybrid remote” meaning 3 days in-office. The labeling is inconsistent.
A few things that help: filter for companies you know are remote-first by reputation (Automattic, GitLab, Zapier, Basecamp, 37signals, Buffer, Remote.com, Doist). Check where their job postings are concentrated. If a company is posting 40 roles and they’re all listed for “New York” or “San Francisco” with remote as an afterthought, that tells you something. If their roles are listed as “anywhere” or “global,” that’s a different signal.
Remote.co, We Work Remotely, and the AngelList Talent remote filter are still better than LinkedIn for finding genuinely remote roles, even in 2026, because the bar for listing there is higher.
The remote tech job market is real. It’s just less forgiving about the word than it used to be.