What "remote-first" actually means at different companies

"Remote-first" is the most overloaded phrase in tech hiring. The same two words mean completely different things at different companies. If you don't disambiguate during the screen, you'll end up surprised — usually unpleasantly. Here are the five common flavors and what to ask.

1. Truly remote-first (you can live anywhere within 4 timezones)

The team is distributed by design. There's no headquarters, or HQ is a small office that nobody works from. Decisions are made async (in writing, in long-form docs). All-hands meetings are recorded. New hires onboard from wherever they are.

Tells:

• They publish their hiring time-zone band ("we hire within Americas TZs", "anywhere in EMEA").
• The interview loop includes a written exercise in addition to live calls.
• Your interviewers are themselves in different cities/countries.

Ask:

• "How often does the team meet synchronously, and at what time of day?"
• "Where are my closest two teammates today?"

2. Distributed in name, US-coastal in practice

The team has remote in its branding but 80%+ of the engineering org lives within 1 hour of the SF or NYC office. Decisions are made in person at lunch, then "documented" in Slack the next day. Promotion velocity correlates with office attendance.

Tells:

• The hiring page says "remote (US)" but the team page on LinkedIn shows people clustered in SF.
• The recruiter mentions "we like to bring people together for kickoff/QBR/offsites" with notable enthusiasm.
• Your interviewers are mostly in one city.

Ask:

• "How many people on the team I'd join live within commute distance of an office?"
• "When was the last time a non-collocated person on this team got promoted to senior or above?"

3. Hybrid that's gradually becoming RTO

The job listing says "remote-flexible" or "hybrid". Internally, the company has been increasing required-in-office days every quarter. The role you're applying for might be 1 day/week now and 3 days/week in six months.

Tells:

• The recruiter is vague about the in-office requirement when asked directly.
• Recent posts on Blind/Reddit/Glassdoor about "creep" in office requirements.
• The CEO has talked publicly about valuing in-person collaboration in the last quarter.

Ask:

• "What was the in-office expectation 6 months ago, and what is it now?"
• "Is there a written policy I can see?"

4. Remote within one country only

You can work from anywhere within, say, the US. Not Canada, not Mexico, not the UK. This is usually a tax/payroll constraint, not a culture statement.

Tells:

• The job listing says "remote (US only)" or "must be authorized to work in [country] without sponsorship".
• The recruiter asks early in the screen where you're located.

Ask:

• "If I move within the country during my time at the company, is that automatic, or does it require approval?"
• (If you might move abroad later) "What's the policy on temporarily working from another country?"

5. Remote-friendly for some roles, not others

Engineering can be remote. Product/design must be in-office. Or: ICs can be remote, managers must be in-office. This often goes unstated.

Tells:

• The leadership team page shows everyone in one location.
• The roles labeled "remote" are skewed to specific functions.

Ask:

• "If I get promoted to a senior or staff level, does my work location need to change?"
• "Are there roles or career paths that aren't available to remote employees?"

The one question that disambiguates

If you only ask one question on the screen: "Where do my future direct teammates physically work, today?"

A truly remote-first team will answer with a list of cities/countries. A nominally-remote team will pause, then say something like "well, most of them are in the [HQ city] office." The pause is the answer.

Companies don't lie about being remote-first; they're using the same phrase to describe different setups. Knowing which flavor you're walking into is the difference between a great year and a year of feeling like the second-class hire.