How a remote company runs its interview is the single most honest preview of how the team actually works. Hiring is the longest sustained conversation an employer has with a stranger, and they can't fake what they don't practice. A company that genuinely operates async-first will interview that way. A company that's "remote" in label but synchronous in habit will interview through five back-to-back video calls — because that's how their workday is built.
This guide is the framework we've seen distributed teams use to evaluate prospective employers. It works in both directions: if you're a candidate, it tells you what you're actually signing up for. If you're a hiring manager, the inverse list is the simplest checklist for making your process credible to senior remote candidates.
The five signals of a genuinely async-friendly remote employer
1. There's a written, async component before any synchronous round. A scoping doc, a take-home with a clear time-box, a design review, or a written response to a real product question. The format matters less than the fact that the company is willing to evaluate written thinking — that means they evaluate written thinking inside the company too. Teams that only do live whiteboarding tend to be teams that only do live whiteboarding for their actual work.
2. The full process is three to four rounds, mixed async and sync — not five video calls.A reasonable pipeline: recruiter screen (30 min sync), async written/take-home round, hiring-manager conversation (45–60 min sync), one or two team interviews. If the company needs five separate hour-long video meetings to evaluate someone they could have evaluated with a take-home and two conversations, they don't actually trust written work as a signal — and that affects every project decision they'll make after you join.
3. Interviewers volunteer their time zone and propose specific slots up front."I'm in CET, I have 10–12 my time Tuesday or 15–17 Wednesday — both work for you?" is the marker of a company that operates across time zones every day. "What times work for you?" with no constraint stated usually means everyone is in the same time zone and assumes you are too.
4. Decisions arrive in writing, with reasoning. After each round, the response is an email with the next step, timing, and (for senior roles) a sentence or two of what the interviewers thought. Companies that only deliver decisions verbally on calls are companies where written documentation isn't the default. You will feel this every day once you join: design decisions made in meetings you weren't in, tickets that say nothing useful, context lost as soon as the person who knew it leaves.
5. Salary and compensation surface early. Either in the listing itself or in the recruiter screen. The reason this matters is not (only) that you save time on mis-aligned opportunities — it's that companies that withhold salary until late are companies that negotiate individually rather than band-by-band, which means salary inequity inside the team. Transparent compensation is a core async-friendly habit because it removes one whole class of DMs and one-off "quick chats" about pay.
The five red flags that mean "office, just at home"
1. Four or more synchronous rounds for a non-leadership role. Senior IC and management roles can warrant deeper evaluation — but a mid-level engineer or designer being asked for five separate video interviews is a process designed for an in-office team where calendars sync naturally. Expect the workday to look the same.
2. "Available 9–5 your time" in the job description.Genuinely remote-first companies measure outcomes; office-first companies that went remote measure presence. "Always-on", "available during business hours", and "quick response time expected on Slack" mean the company is trying to recreate the office attendance signal via your status indicator.
3. Every interviewer is in the same time zone. Pull up the LinkedIn profiles of the interviewers after each round. If all six of them are in the same metro area, the team is geographically concentrated even if the company allows remote work. You'll be the exception, not the norm — and decisions will get made in the office hallway you're not in.
4. The process is all talking, no doing.Five rounds of conversation about your past experience, with no opportunity to demonstrate the work, is a soft skill assessment wearing a job-interview costume. Async-first teams want to see you produce something on your own time at your own pace, then discuss it. Sync-first teams want to see you in real time because that's how they work.
5. Salary withheld until after the final round. This is a negotiation tactic that only works when the company can dramatically narrow the candidate's alternatives by running them through hours of process first. It's also very common at companies where comp is negotiated individually — which means peers doing the same work earn different amounts.
What to ask in your screening call
Three questions, in order of how much they reveal. None of these are confrontational; they're open-ended enough that the recruiter will answer honestly.
- "What does a typical week on this team look like — how much of it is meetings versus heads-down work?" The honest answer is the answer. Async-first teams will say "maybe one or two meetings a week beyond standup." Sync-first teams will say "daily standup, twice-weekly team sync, a planning meeting, and...".
- "How does the team handle decisions that involve people in different time zones?" A real async-first team has a concrete answer: an RFC doc, a Linear ticket, a Notion page, a written decision log. A sync-first team will say "we usually just get on a call."
- "When was the team's last all-hands or offsite, and what does the next 12 months of travel look like for this role?" This is the cleanest test for "remote-first with required onsite" (category 3 in our taxonomy of remote). The recruiter will tell you the truth because they need to.
The meta-signal
The single highest-signal question — if you have to pick one — is: "Can you share a recent written artifact your team produced, with confidential details redacted?" A real async-first team has design docs, RFCs, post-mortems, and decision logs that are the actual substrate of how work gets done. They'll happily share a sanitized one. A team that runs on meetings and Slack threads will struggle to find anything to send, and the artifact they eventually send will be sparse. That's diagnostic.
None of these signals are 100% predictive — every company has exceptions, and a great team can sit inside an otherwise sync-heavy organization. But interview process and team output are signals you actually have access to as a candidate, before you sign. Most other signals about a company's culture you can only learn after you've been there a quarter.