“Remote-first” is everywhere in job descriptions. So is “remote-friendly,” “hybrid remote,” “flexible remote,” and “distributed team.” These terms sound similar. They are not. Before you accept an offer or uproot your life, you need to know the difference — because the phrase in the job description is often the kindest version of the reality.
Remote-first vs. remote-friendly: the actual difference
A remote-first company is built assuming that employees are not in the same room. Meetings are recorded or async by default. Documentation lives in writing, not in someone's head. Decisions happen in shared documents, not hallway conversations. The office, if there is one, exists for optional gatherings — not because work requires it.
A remote-friendly company tolerates remote work. There's usually a headquarters where most employees are. Remote employees are accommodated, not centered. Meetings happen in a conference room with one camera pointing at a table. The people who are there in person move faster: they're the ones who have lunch with leadership, hear about the new project before it's announced, get pulled into the whiteboard session.
Both companies will say “we're open to remote.” Only one of them built their processes around it.
The five questions to ask before you accept
1. Where is the leadership team located?
If the CEO, CPO, and most VPs are in San Francisco and you're in Berlin, you will never be in the room where decisions happen. The informal network that drives careers — the after-meeting conversation, the opinion volunteered at lunch — is geographically concentrated. That's not malicious. It's human. But you'll feel it.
2. What's the primary communication tool — Slack or email?
Real-time tools (Slack, Teams) can work asynchronously, but they're often used to recreate the office in digital form: people expect immediate replies, decisions get made in threads that expire, and anyone offline misses context. Companies that use longer-form, async-first writing — Notion, Linear, written RFCs — have usually thought harder about distributed work.
3. How are performance reviews done?
“We value outcomes, not hours” sounds great. Ask how they actually measure it. If the answer is vague, or involves “being visible,” or relies heavily on manager perception, that's a signal the company hasn't solved remote performance management. The best remote companies have explicit goal systems (OKRs, JIRA velocity, shipped features) and manager training in remote feedback.
4. What's the core hours policy?
Some companies require everyone to be online from 9am–3pm in a specific timezone. That's not fully remote — that's an office schedule without commute. True remote-first companies either have no required hours or have a small overlap window (e.g., 2 hours/day) that covers multiple timezones. Find out before you commit.
5. Has leadership ever worked fully remotely themselves?
Founders and executives who have never personally been a remote employee often underestimate how much of work culture is tacit and proximity-dependent. They'll say the right things. But the company will slowly drift toward “just come in a few days a week” when business pressures mount — and it always happens after you've already moved.
The hybrid trap
Hybrid means the company hasn't decided. That's not always bad — some teams genuinely split well. But “hybrid” as a permanent policy is often “we don't want to lose our office but we also want remote talent.” The outcome for remote employees in a hybrid org usually depends entirely on their direct manager: you might have a great experience, or you might feel like a second-class citizen every quarter review.
Ask hybrid companies: what's the expected in-office frequency? Is it written policy or informal? What happens if I move 3 time zones away?
Red flags in job descriptions
- “Remote with quarterly travel” — how much quarterly travel? Some companies mean 4 days a year. Others mean 3 weeks per quarter. Ask for the number of days expected on-site per year.
- “Prefer candidates in [City] area” — this job is not remote. This job is hybrid and will become office-required within 18 months.
- “Flexible remote” — this is not a standard term. It usually means the company hasn't formalized policy yet. Proceed with caution.
- “Remote work possible for the right candidate” — translation: we'll make an exception but you will always feel like an exception.
Companies that have built remote correctly
The companies that do remote well share a few traits: they were founded remote (not converted), they have strong writing cultures, their tools default to async, and they have explicit promotion and compensation frameworks that don't rely on visibility. GitLab has published their entire remote handbook publicly. Automattic (WordPress) has operated fully distributed for over a decade. These are useful references for what intentional remote culture looks like.
When you find a job you're excited about, ask the recruiter to point you to their remote work documentation. A company that has thought about it will have some. A company that hasn't will tell you to ask your hiring manager.
Start with a cleaner source
One thing that makes this research harder than it should be: most job boards are full of listings that misclassify remote type entirely. A role gets flagged “remote” by an automated scraper, it's actually hybrid, and you spend 20 minutes on a recruiter screen before learning the real policy.
Remotato pulls jobs directly from company ATS systems — Greenhouse, Lever, Ashby, Workable, SmartRecruiters — and parses the remote classification from the source data rather than relying on how a scraper categorized it. Every listing is labeled fully remote, remote within a specific region, or hybrid. No scraped duplicates, no recruiter postings, no ghost listings that were filled 6 weeks ago.
You still need to do the due diligence above. But starting with a board that only shows real, classified remote jobs from real companies means you spend your research time on the right questions — not on filtering out noise that shouldn't have been there in the first place.