Remote work used to be one of the main ways tech companies widened their talent pool. In the latest data, it has become rare. Fewer open tech roles offer a remote option than at any point on record, and jobs are concentrating in a small number of hubs.
This article reads the location data in Lenny Rachitsky's State of the tech job market: late 2026 from the employer side. It is written for talent acquisition leaders, heads of engineering and people teams at tech companies. Our view: when most employers pull back from remote work, a company-wide policy is the wrong tool. Location should be decided role by role, and a targeted remote or flexible option can become a real advantage for the roles that are hardest to fill. It expands one part of our guide to the tech job market in 2027.
What the data shows
All figures below describe global job openings at tech companies.
| Signal | Number |
|---|---|
| Open tech roles offering a remote option | 14%, the lowest on record, down from 21% in late 2022 |
| Remote engineering roles | 14%, down from 25% in late 2022 |
| Remote design roles | 19%, down from 34% |
| Remote PM roles | About 21%, steady for two years but near record lows |
| Share of open tech roles in the Bay Area | 15%, about one in seven, a record |
| Change in open Bay Area jobs | Up 43% in a year |
| Bay Area share by role | One in four open PM and design roles, one in five engineering roles; each has nearly doubled its share since 2022 |
The report adds a milestone: there are now more open PM, engineering and design roles in the Bay Area than remote roles globally. Four years ago, remote led by almost two to one.
What is behind the shift
The report does not explain why remote roles are declining, and we will not guess at a single cause. What the data does show is a clear direction across functions, with PM as the partial exception. Location is now part of how most tech employers define a role, and the default has moved back to the office or a hub.
We expect office-centred hiring to remain the norm through 2027. That does not mean every company should follow it for every role.
Why remote can become an advantage
When 86% of open tech roles do not offer a remote option, the candidates who want remote work have fewer options. For employers, that creates an opportunity on specific roles:
- Scarce skills. For roles where qualified candidates are few, such as senior AI engineers or security specialists, a remote or flexible option widens the pool beyond one city.
- Experienced people with constraints. Strong candidates who cannot relocate, for family or other reasons, have fewer alternatives than they did in 2022.
- Competing without matching big-company pay. A mid-sized company that offers flexibility on a hard-to-fill role competes on something other than salary.
The trade-off is real: remote roles need clear ways of working, management that does not depend on proximity and a deliberate effort to include remote people. Offer it where the benefit to hiring outweighs that cost.
Decide location role by role
A simple framework for each requisition:
| Question | If yes | If no |
|---|---|---|
| Is the local pool for this role large enough to fill it within your target time? | Hire in the office or hub | Consider hybrid with fewer office days, or remote |
| Does the work depend on daily in-person collaboration or physical access? | Office or hub | Remote is possible |
| Can the team manage and include a remote member well today? | Remote is viable | Fix that first, or hire locally |
| Can you legally employ someone in the candidate's location? | Remote is viable | Limit to locations where you can employ |
Write the result into the job description. Candidates should see the work location and arrangement in the first lines, not discover it at the offer stage. Record the decision in your ATS too, so you can later compare how each arrangement performed.
If you choose the office, make it count
Most tech companies will keep most roles office-based or hybrid in 2027. Candidates know this, so the question they ask shifts from "is it remote?" to "is the office worth it?" Three things make an office requirement easier to accept:
- A clear reason. Explain in the job description why the role is in person, for example close work with customers or a hardware lab. "Our culture" without detail persuades few people.
- Predictable days. Set which days the team is together, so people can plan commutes and family time. Hybrid without a pattern can mean coming in to an empty floor.
- Time used for collaboration. Keep office days for planning, design reviews and pairing. Work that needs focus can happen anywhere.
Ask candidates who decline offers what would have changed their decision. If the office requirement comes up repeatedly, you have evidence to revisit the policy for that role family.
What this means for APAC tech companies
The report's location data covers tech companies globally, and its Bay Area figures say nothing direct about Asia. For tech companies hiring across Singapore, Kuala Lumpur, Jakarta and Hong Kong, three points matter.
Employment rules shape what "remote" means. Hiring someone in another country usually needs a local employing entity or an employer of record, and a work pass for anyone who relocates. A "remote" role in APAC rarely means you can hire in any country. State the work location and the country of the employing entity in each requisition.
Regional hubs work like the Bay Area on a smaller scale. Many tech companies in the region concentrate product and engineering roles in one or two cities. The same logic applies: the hub gives you collaboration, but limits the pool to people who live there or will move.
Fewer global remote roles may change who applies. One possibility is that fewer overseas remote roles are open to people in APAC, and more experienced professionals look to local and regional employers. This is our inference: the report has no data on remote workers in the region. To check, review applicants for your technical roles over the past two quarters and see whether the share whose last job was remote for an overseas employer is rising.
Measure the effect of your location choices
Location policy is easy to set and hard to evaluate. Track three things for each role family:
- Time to fill by work arrangement. Do hybrid or remote roles fill faster than office roles of the same type?
- Applicant pool size and quality. How many qualified applicants reach the first interview under each arrangement?
- Offer acceptance. How often do candidates decline because of the location requirement? Record the reason when they do.
Review these every quarter. If a role family fills slowly and candidates often cite location, test a more flexible arrangement on the next requisition and compare. Keep the test small and time-bound, so it gives you evidence rather than a new policy that nobody chose on purpose.
Common mistakes
- One policy for every role. A blanket rule ignores that some roles have deep local pools and others do not.
- Hiding the arrangement. Candidates who find out about office requirements late withdraw late, which costs everyone time.
- Offering remote without the support. A remote hire who is left out of decisions will not stay long.
- Assuming remote means anywhere. Employment, tax and work pass rules decide where you can hire, not the job title.
Next step
For each role in your 2027 plan, answer the four questions in the framework and write the work arrangement into the requisition. Then pick one hard-to-fill role and test a more flexible arrangement. For the full picture of the 2027 tech job market, read our guide to the tech job market in 2027.

Author
Moka AI Editorial Team
The Moka AI Editorial Team creates insightful, practical, and engaging content on HR, recruitment, and AI innovation. We explore emerging trends, share industry insights, and turn complex ideas into actionable knowledge to help HR professionals navigate the evolving world of work.



