Not every company that says “remote” in a job posting is actually remote. Some are remote-tolerant. Some are office-first companies that added a remote option and never built the infrastructure for it. Working for one of these companies is a genuinely different experience from working for a company built around remote from day one — and not a good one. Here are the red flags that matter.
Red flag 1: “Remote for now”
If a job description says “currently remote,” “remote during COVID,” or “remote for the foreseeable future,” the company is telling you exactly what they think of remote work: it's a temporary accommodation, not a design principle. These companies will return to office the moment they can justify it. You will be expected to follow.
What to look for instead: companies that describe remote work as a core part of how they operate, not a benefit they offer. “We're a distributed team” or “we've been remote-first since founding” are much stronger signals than “remote OK” or “flexible remote policy.”
Red flag 2: All their meetings are video calls
Counterintuitive, but: a company that runs everything as a Zoom meeting hasn't actually figured out remote work. They've taken their in-person meeting culture and moved it to video. This means your day is fragmented into 30- and 60-minute calls, you have no deep work time, and the async skills that make remote workers valuable are never developed.
Ask in your interview: “What percentage of decisions are made asynchronously versus in real-time meetings?” and “Do you have a culture of written documentation?” Companies that do remote well have Notion or Confluence wikis that are genuinely maintained, make decisions in GitHub comments or Slack threads, and reserve meetings for the things that genuinely need them.
Red flag 3: No async communication norms
If you ask “What's the expected response time for Slack messages?” and the answer is “we try to respond within a few hours” — that's fine. If the answer is a vague “as soon as possible” or a confused pause, the company is running remote work as a permanent on-call arrangement. You'll be expected to be available at all times, which is the worst of both worlds.
Remote-first companies have written norms: “Non-urgent messages should get a response within one business day. Urgent questions should be flagged as such in the message. Meetings should have an agenda in the invite.” These sound like obvious rules, but most companies don't have them — and the absence causes real problems.
Red flag 4: Vague about time zone requirements
“Must be available during core business hours” in a remote job listing almost always means US time zones, but without specifying which ones or how much overlap is required. You find out during onboarding that “core hours” means 9am–5pm Pacific and you're in Berlin.
Ask directly: “What time zone is the majority of the team in, and what overlap hours are expected?” A clear answer (“we have a 10am–2pm EST overlap window, and we need people to be available in that window”) is fine. Vagueness is a sign they haven't thought it through.
Red flag 5: No remote-specific onboarding
How a company onboards you tells you everything about how remote they actually are. If the onboarding plan is “shadow your manager on calls for two weeks,” you're joining an office company that happens to let you work from home. If there's a written onboarding document, a 30-60-90 day plan, an assigned buddy, and structured check-ins — the company has done this before and built a system.
Ask: “Can you walk me through what onboarding looks like for this role? Is there a written guide?” The quality of the answer is a strong proxy for how seriously the company has invested in remote infrastructure.
Red flag 6: Senior leadership is always in the office
If the CEO, CTO, and VP Engineering are all in the same city and go into an office every day, the remote employees at that company are second-class citizens — no matter what the job posting says. The most important conversations, decisions, and relationships happen in the room. People in the room get promoted. People on video get managed.
Look at the leadership page on the company website. Check where executives are based on LinkedIn. If everyone is in San Francisco or New York, that's not a remote-first company — it's a company that allows remote work for some roles.
Red flag 7: They call it a “remote perk”
Benefits pages that list “remote work” alongside ping pong tables and free lunches are signalling that remote is an employee benefit they offer, not a core part of how the company operates. When remote work is treated as a perk, it can be taken away. When it's how the company works, it's structural.
What a genuinely remote-first company looks like
The companies that are actually built for remote work share common traits: they have a public handbook or wiki (Notion, GitBook, or internal docs) that explains how everything works; they hire globally without hesitation; they measure output, not hours; they have explicit written communication norms; and their leadership team is distributed across time zones.
Gitlab has published their entire company handbook publicly. Basecamp wrote a book about it. Doist, Zapier, Automattic, Loom — these companies don't offer remote work, they were built on it. The difference is tangible from day one.
Every company on Remotato is vetted to confirm they are genuinely remote-first — not office-first companies with a remote option. That single filter removes most of the noise.