How to evaluate a remote-first company before you accept
Five concrete signals that separate genuinely remote-first companies from co-located teams that hired you remote by accident.
"Remote-first" is the new "we have great culture" — every company claims it, almost none of them can prove it. Before you sign, run a 30-minute audit. Five signals tell you everything.
1. Where does meaningful work happen?
Ask: "If you described the last big architectural decision your team made, where and how did it happen?" If the answer is "we got in a room together for two days", that's a co-located company that hired some remote people. In a remote-first company, decisions happen in writing — design docs, async PRs, recorded videos — and the room is just a synthesis step, if it happens at all.
2. The handbook test
Ask for the public-facing handbook (companies like GitLab and Posthog publish theirs). If they don't have one, ask for the internal version. A 6-page Notion page isn't a handbook. A real remote-first company has 100+ pages because anything that isn't written down can't scale across timezones.
3. Salary bands, in writing
Remote-first companies have salary bands you can read. Co-located companies "evaluate per candidate". The second version always favors the company. Cross-check published ranges against the salary explorer before the interview, then ask the recruiter where their band sits relative to market median.
4. Async-by-default vs. async-when-convenient
Look at the calendar of a senior IC. Ask: "How many recurring meetings does someone in this role have per week?" If the answer is more than 4, the team is sync-first wearing a remote costume. Real remote-first IC roles run on 2–3 standing meetings/week and a heavy doc/PR review load.
5. What happens when someone in Asia ships a PR at 2 AM Pacific?
This is the diagnostic question. In a real remote-first company, the PR gets reviewed within their next working day — by someone in their region or whoever's awake — without anyone losing sleep. In a co-located company with remote employees, that PR sits for 12 hours until the US team wakes up. Ask explicitly: "What's the median time-to-review on PRs from your non-US engineers?"
Where to look first
If you're at the top of the funnel, start with companies hiring remote talent on RemoteTalent — most of them publish stack, location policy and salary upfront, which is itself a strong filter. The companies that won't write down those three things on a job ad won't write them down in your contract either.
You're not just evaluating a job. You're evaluating whether the next 18 months of your career happen in a system that's designed to work without you in the room.
More from the blog
- May 26, 2026 · 7 min read
Remote engineering salaries in 2026 — what the data actually says
A grounded look at remote engineering pay across EU, Americas and EMEA in 2026, broken down by stack and seniority, with notes on how to read the ranges.
- May 22, 2026 · 7 min read
Async-first hiring: run a remote interview loop in 10 days
A tested 10-day loop for hiring a senior remote engineer without 7 calls and three weeks of back-and-forth.
- May 15, 2026 · 6 min read
How to negotiate a remote offer — without burning the relationship
A practical playbook for negotiating salary, equity and benefits in a remote job — from first conversation to signed contract.