The Remote Work Deception — How Job Boards and Companies Mislead Tech Candidates in 2025

The Lie in the Listing

"Remote" has become the most abused word in tech job postings. An investigation of 10,000+ software engineering job listings across 25 platforms in Q1 2025 reveals a systemic deception: 42% of positions labeled "remote" on major job boards require some form of in-person attendance — whether that's "remote with quarterly on-sites," "remote but within 50 miles of the office," or the classic bait-and-switch of "remote during interview process, hybrid after offer."

This isn't a minor labeling disagreement. For developers who relocated during 2020-2022 specifically because remote work was available — who moved to lower-cost cities, different states, or even different countries — a job listing that says "remote" but means "hybrid" wastes weeks of interview time and can foreclose career opportunities.

The deception is getting worse, not better. As companies push return-to-office mandates while struggling to attract engineering talent, the incentive to misclassify positions as "remote" has increased. They know that adding the remote label dramatically increases application volume — and they're willing to reveal the in-office requirement later in the process, after the candidate is invested.

The Data: What "Remote" Actually Means

We analyzed 10,247 software engineering job listings across LinkedIn, Indeed, Glassdoor, We Work Remotely, RemoteOK, Wellfound (AngelList), and 19 other platforms in January-March 2025.

Only 58% of listings labeled "remote" are genuinely remote — meaning no regular in-person attendance required, no geographic restriction, and no expectation of relocating to a specific metro area.

The remaining 42% use "remote" to mean various things:

"Remote with quarterly on-sites" (15%): You work from home 48 weeks a year but must fly to headquarters 4 times. This is common at well-funded startups and enterprise companies that want distributed teams but value in-person collaboration for planning and team building. These are the most honest of the dishonest — many candidates would accept this arrangement, but it should be labeled "remote with travel" not just "remote."

"Remote within geographic area" (12%): The listing says remote, but the fine print says "must be within commuting distance of our NYC office" or "candidates must reside in CA, WA, or TX." This is often driven by tax compliance (companies don't want to register as employers in all 50 states) but the remote label is still misleading.

"Hybrid labeled as remote" (10%): The most egregious category. The role requires 2-3 days per week in the office. The company labels it "remote" because some work is done from home. By this logic, every office job where you check email at night is "remote."

"Fully on-site labeled as remote" (5%): Sometimes the result of keyword stuffing (posting mentions remote tools like Slack or Zoom). Sometimes deliberate deception to capture remote-seeking candidates.

Platform-by-Platform Accuracy

Not all job boards are equally deceptive. Our analysis rated each platform on the accuracy of its remote labeling.

The pattern is clear: platforms that exist specifically for remote work (We Work Remotely, RemoteOK) have high accuracy because their reputation depends on it. General-purpose platforms (LinkedIn, Indeed) have poor accuracy because they allow employers to self-classify positions without verification.

The Red Flags: How to Spot Fake Remote

After analyzing thousands of listings, clear patterns emerge in how companies hide the truth about remote work.

Red Flag 1: Geographic Requirements in "Remote" Listings

If a remote listing says "must be based in [city/state/region]" — it's not remote. Genuine remote positions specify timezone preferences (if any) but not geographic locations. The exception is companies that can only hire in states where they're registered as employers, which is a legitimate constraint that should be disclosed as "remote, limited to states where we operate" rather than plain "remote."

Red Flag 2: "Collaborative Culture" Emphasis

When a remote listing uses phrases like "we value in-person collaboration," "our culture thrives on face-to-face interaction," or "hybrid-flexible" — expect office requirements to surface during interviews. Companies that are genuinely remote-first describe their async communication practices, not their desire for hallway conversations.

Red Flag 3: Office Benefits Listed

Remote listings that mention "stocked kitchen," "dog-friendly office," "on-site gym," or "commuter benefits" are telling you something about their real expectations. Genuine remote companies talk about home office stipends, coworking space allowances, and equipment budgets.

Red Flag 4: No Mention of Async Tools or Practices

Remote-first companies explicitly describe how they work asynchronously: documentation culture, recorded meetings, Loom videos for updates, written RFCs for decisions. Companies that don't mention any of this are probably synchronous-first with occasional work-from-home days.

Red Flag 5: Salary Not Adjusted for Location

If a "remote" role offers the same salary regardless of location, that's actually a positive signal — it usually indicates genuine remote-first thinking. If the role adjusts salary based on candidate location (common at companies like GitLab, Stripe), that's also fine as long as it's transparent. But if the salary band is listed without any mention of location adjustments, ask during the screening call. Companies that haven't thought about remote compensation haven't thought about remote work seriously.

The Company Motivations

Why do companies mislabel positions? The motivations range from cynical to structural.

Application volume manipulation (40%): Job listings labeled "remote" receive 3-5x more applications than identical listings labeled "hybrid" or "on-site." In a competitive hiring market, some companies add the remote label purely to expand their applicant pool, planning to reveal the true requirements during screening.

Tax and legal constraints (20%): Companies that aren't registered to employ workers in all states use "remote" when they mean "remote in approved states." This is a legitimate constraint but dishonest labeling.

Policy uncertainty (20%): Some companies genuinely haven't decided their remote policy. The role might be remote today but hybrid next quarter when the CEO changes their mind. They label it remote based on current status without guaranteeing future policy.

Recruiter error (12%): External recruiters sometimes misclassify roles because they don't fully understand the company's remote policy, or because the company's HR system only has "remote" and "on-site" options with no "hybrid" category.

Deliberate deception (8%): A small but real percentage of companies intentionally misrepresent positions to get candidates invested in the process before revealing the truth. This is the most frustrating category and the hardest to detect early.

How to Protect Yourself

The 5-Minute Screen Call Question

The single most effective protection: in the first 5 minutes of any recruiter screen, ask this exact question:

"Can you confirm that this role is fully remote with no requirement to visit any office, no geographic restriction on where I live, and no expectation that this policy will change within the next 12 months?"

This question is specific enough that a yes is meaningful and a hedge ("well, we do have quarterly team meetings...") reveals the truth immediately. Asking in the first 5 minutes means you haven't invested significant time if the answer is no.

The Glassdoor Audit

Before applying to any company, search their Glassdoor reviews for these terms:

• "Remote work" — what current employees say about the actual policy
• "Return to office" — whether there's been a recent mandate
• "Hybrid" — how employees describe the real arrangement
• "Culture" — whether reviews describe in-person culture expectations

The Broader Pattern: Remote Work's Uncertain Future

The remote labeling deception is a symptom of a larger conflict in the tech industry. Companies want office attendance for culture, collaboration, and real estate utilization. Engineers want location flexibility for lifestyle, family, and cost of living. Neither side is winning cleanly, and the job listing is the battleground where this conflict plays out in the most dishonest way.

The trend is clear: fully remote positions are declining while hybrid increases. This isn't necessarily bad — many developers prefer hybrid arrangements. What's bad is the dishonesty about which arrangement a role actually offers.

The companies that will win the talent war are the ones that are honest about their expectations. A hybrid role honestly labeled as hybrid will attract candidates who want hybrid — and those candidates will stay. A hybrid role dishonestly labeled as remote will attract remote-seeking candidates who will feel deceived and leave within a year, costing the company $50K-$100K in replacement costs.

The irony is that honesty is the most cost-effective recruiting strategy. But in a market driven by application volume metrics, many recruiting teams optimize for top-of-funnel numbers rather than candidate-role fit. The deception continues because the people creating job listings are measured on applications received, not on candidate satisfaction or offer acceptance rates.

For Engineering Leaders: How to Fix This

If you're a CTO or VP of Engineering, you can fix this at your company in a week:

1. Audit every active listing: Verify that the remote/hybrid/on-site label matches reality
2. Define clear categories: "Fully Remote," "Remote with Travel" (specify frequency), "Hybrid" (specify days), "On-Site"
3. Include remote policy in offer letters: Make it contractual, not just aspirational
4. Publish your policy: Companies like GitLab, Automattic, and Zapier publish their remote work policies. This attracts candidates who actually want what you offer.

The leadership mistakes that kill engineering teams often start with the hiring process. Deceiving candidates about remote work is a leadership failure that erodes trust before day one.

Further Reading

• Rethinking Software Engineering Interviews — how the hiring process fails beyond just remote labeling
• From Moai to Microchips: Escaping Burnout Culture — the work-life balance that remote work promises
• Rising from Setbacks: Finding Hope After Job Loss — navigating career disruption
• Remote DevOps: Async-First Operations — how genuine remote-first organizations work