Where remote engineering still hires, May 2026
May 7, 2026 · Viktor Shcherbakov · 9 min read
- data-analysis
- remote-work
A new piece of conventional wisdom landed in 2025: remote work is over. JLL's Q2 2025 US Office Market Dynamics report had the headline number: 54% of Fortune 100 employees subject to full-week office requirements, up from 11% the year before. 
Microsoft rolled out a 3-day-in-office mandate. 
Amazon went all the way to 5. 
Goldman Sachs and 
JPMorgan Chase & Co. followed. The trade press did the rest.
But the Fortune 100 are 100 employers. We monitor 4,441 of them. Across that index, on the morning of May 7 2026, 4,338 of the 89,517 active engineering postings are tagged remote-eligible. That's 4.8%: a number small enough to confirm the headline ("most jobs are onsite"), big enough to deserve a list of names ("but here are the thousands that aren't"). This is that list.
Who's still hiring
Twenty companies account for about a third of all currently-listed remote-eligible engineering roles in our index.
| Company | Active remote engineering postings |
|---|---|
 NVIDIA | 174 |
 Tether | 117 |
 Sezzle | 106 |
 Disney | 99 |
 ClickHouse | 81 |
 Netflix | 78 |
 Grafana Labs | 77 |
 Affirm | 61 |
 Veeva | 45 |
 Samsara | 43 |
 Oliver Wyman | 43 |
 Instacart | 42 |
 Cresta | 41 |
 GitLab | 39 |
 Kraken | 38 |
 Accenture | 38 |
 Reddit | 36 |
 Clickup | 34 |
 Keeper Security | 34 |
 Twilio | 33 |
A few patterns stand out. Crypto and payments infrastructure is well-represented (Tether, Kraken, Sezzle, Affirm), as are the open-source and devtools shops (ClickHouse, Grafana Labs, GitLab). NVIDIA, Netflix, Reddit, and 
Pinterest (just outside the top 20) are big-tech names whose remote-friendly hiring posture doesn't get the press coverage that Microsoft and Amazon's RTO mandates do. Mid-market SaaS rounds it out: Twilio, Instacart, Clickup, Samsara. One name most candidates wouldn't think to check: Oliver Wyman, a management consultancy with 43 remote engineering roles — a real internal-tech footprint hiding inside a category nobody thinks of as remote-friendly.
What's not on the list is also a story. None of the headline RTO mandators we named in the lede — Microsoft, Amazon, Goldman Sachs, JPMorgan Chase & Co. — carry meaningful remote engineering listings in our index. The mandates and the postings agree.
The geography
Remote isn't location-free. Postings still tag a hiring jurisdiction (timezone bands, work-eligibility, or a payroll entity). Across the 4,338 remote-eligible engineering postings, the distribution of those tags:
| Region | Postings |
|---|---|
| United States | 2,277 |
| Canada | 431 |
| United Kingdom | 259 |
| Spain | 218 |
| India | 189 |
| Poland | 184 |
| Germany | 164 |
| Ireland | 146 |
| Brazil | 132 |
| Mexico | 130 |
| Argentina | 121 |
The top of the table is what you'd expect: the US plus the EU pay-transparency belt. The interesting part is the contrast with the rest of the engineering market.
Our index has an India-heavy gravitational center for engineering. Bengaluru alone has 16,941 active engineering postings, more than New York and San Francisco combined. Of those 16,941, just 67 are remote-eligible. That's 0.4%. Hyderabad, Pune, Chennai are similar. Indian engineering hiring is fundamentally an onsite market: the big global tech employers post heavily there, and they post for desks.
The corollary is that remote-eligible engineering isn't competing with the global engineering labor market. It's competing with the slice that happens to be tagged for North American or Western European hiring.
The seniority skew
Of the 4,338 remote-eligible engineering roles, 1,995 (46%) are tagged Senior, another 11% are Staff, 3% Principal, 2% Lead. About 62% of the sample is gated at senior+ levels. Entry-level roles are 0.7%: 31 listings out of 4,338. Internships are 0.5%.
This snapshot contains 31 postings explicitly tagged Entry-Level. It does not establish that only 31 roles are suitable for candidates with under two years of experience: 36% of remote postings have no seniority tag. Nor can one snapshot establish a trend in access to remote work.
Use the tagged roles as a starting point, then read the requirements of untagged roles too.
What stack is being asked for
The skills profile of remote engineering is recognizable, and a little narrower than overall engineering hiring. The percentage of the 4,338 remote-eligible postings that mention each technology:
| Skill | Share of remote eng postings |
|---|---|
| Python | 49% |
| AWS | 37% |
| Kubernetes | 27% |
| SQL | 24% |
| React | 23% |
| TypeScript | 22% |
| Java | 19% |
| Google Cloud | 18% |
| Docker | 16% |
| PostgreSQL | 16% |
| Terraform | 14% |
This is the cloud-native, Python-and-typed-JavaScript stack: the one that lends itself to async work across timezones. Embedded engineering is sparse, low-level systems are sparse, game development is sparser still. C++ shows up in 10% of postings; Go in 7%; Rust in 6%. Things that need a lab bench, a graphics card on the desk, or a co-located ops team aren't what's getting advertised remote.
If you're optimizing your skills for remote employability, the table above is the one to optimize against.
Salary transparency
31% of remote engineering postings in our index include a parseable salary range. For onsite engineering, that figure is 14%. Remote postings are roughly twice as transparent.
The reason isn't that remote-friendly companies are more virtuous. It's geographic concentration. US states with pay-transparency laws (California, New York, Colorado, Washington, Illinois) and the EU Pay Transparency Directive 2023/970 (member-state transposition due June 7 2026) are exactly where remote engineering is most concentrated. The same reason a posting is remote-tagged is a major reason it's also salary-tagged.
If you want comp upfront, the remote-eligible slice of our index is twice as likely to give it to you on the first read.
What to do with this list
The dataset behind this post is the dataset behind the search. The explore page lets you filter on remote directly and combine with seniority, salary band, and stack — then save the search as your own watchlist. That's the path we'd take if we were the reader.
Methodology
- Snapshot date. All counts come from a single Typesense facet query against our
job_posting_v1collection on May 7 2026 at ~13:00 UTC. Theis_active=trueflag is set by our crawler when a posting was last seen on its source board within delisting tolerances (defined per-ATS in our indexing policy). - Engineering definition. Postings whose normalized occupation lineage includes any of: software-engineer (with children frontend, backend, fullstack, mobile, embedded, game, AI engineer, research engineer), devops-engineer (with SRE, platform, cloud, release variants), qa-engineer, data-engineer, data-scientist, ml-engineer, data-analyst, data-annotator. Electrical, mechanical, and civil engineering are tagged outside the software/data domain and excluded.
- "Remote-eligible". A posting where our normalized
location_typesarray containsremote. About 28% also have anonsitetag. That combination does not establish optional office access or permission to work from any location; check each source posting. These counts describe tags, not verified remote-only arrangements. - Seniority tagging. About 64% of remote engineering postings (2,767 of 4,338) carry a normalized seniority tag. The 31 Entry-Level tags are 0.7% of the full sample. The seniority of the remaining 36% is unknown, so this is a tagged share, not an estimate of all roles accessible to entry-level applicants.
- Coverage caveat. Our index is 4,441 companies. It is not a representative sample of the global labor market: we deliberately track companies in Western Europe, Switzerland, and selected US tech employers, with their global subsidiaries' postings included where the careers page is monitorable. The shape of the data follows that bias.
- The "United States" row. The geography table's US count (2,277) is computed against
location_idsancestors in our location hierarchy — every posting tagged with a US city, state, or "United States" itself rolls up. The other rows in the table are facet counts onlocation_namesdirectly. The difference matters here because remote postings often tag a US state or city rather than the country root. - Snapshot, not trend. Our crawler's earliest
first_seen_atfor a still-active posting is March 9 2026. Postings older than that may exist on source boards but only appear in our index from their first crawl-discovery onwards. We make no trend claims based on this snapshot. During the same 2-month window, 4,233 remote-eligible engineering postings have closed — the market is churning, not stagnant. - Reproducibility. Every count above can be reproduced with a single Typesense
documents/searchrequest against ourjob_posting_v1collection with appropriatefilter_byandfacet_byparameters. The schema lives atapps/crawler/src/typesense_schema.pyin our open-source repository. - What this isn't. This is a snapshot of advertised postings, not a measurement of headcount, fills, or company strategy. A company can post heavy and hire light, post light and grow fast. The picture here is "what do their careers pages currently advertise" — useful for figuring out where to apply, less useful for inferring what's happening inside.
References
External sources cited above:
- JLL. U.S. Office Market Dynamics, Q2 2025. The "54% of Fortune 100 / up from 11%" headline. Report landing page: jll.com/en-us/insights/us-office-market-dynamics. Summary coverage: Bisnow, "Majority of Employees at Fortune 100 Firms Now Have 5-Day Office Mandate".
- Amazon. Andy Jassy, "Update on Amazon return-to-office and manager-team ratio," September 16 2024 — the memo announcing the five-day-in-office mandate. aboutamazon.com.
- Microsoft. Three-day-in-office mandate announced September 2025, phased rollout starting February 23 2026 (Puget Sound first). Coverage with primary-source detail: GeekWire, "Microsoft's new RTO policy starts Feb. 23".
- EU Council. Directive (EU) 2023/970 of the European Parliament and Council on pay transparency, in force June 6 2023; member-state transposition deadline June 7 2026. Article 5 is the salary-in-job-vacancy clause. EUR-Lex official text.
- Goldman Sachs / JPMorgan five-day-office mandates are referenced via JLL's Q2 2025 report (above), which names them among Fortune 100 firms that moved to five-day mandates in the first quarter of 2025.
US state pay-transparency laws referenced collectively (California SB 1162, New York Pay Transparency Law, Colorado Equal Pay for Equal Work Act, Washington SB 5761, Illinois HB 3129) are summarized at the US Department of Labor's Pay Equity resources.