That's a mistake. Remote work requires a different set of skills, and the candidates who excel in an office aren't always the candidates who excel without one. A smart, talented candidate can be a great in-office hire and a poor remote hire. Not because anything's wrong with them, but because the operating environment is genuinely different.

This article gives you a question bank for assessing whether a candidate will thrive in a remote role. Use it in addition to your normal role-specific questions, not instead of them.

Before the questions: what remote work actually requires

Five traits genuinely predict remote performance. Skill in the actual job is a sixth, but it's role-specific and not what this article covers.

Self-management. Remote work removes the structure of an office. Nobody walks by your desk to check in. Strong remote workers build their own structure: routines, calendars, focus blocks, intentional rest. Weak remote workers drift.

Written communication. In a remote environment, most communication is written. Slack, Notion, Linear, GitHub, email. Workers who can communicate clearly in writing are dramatically more effective. Workers who can only communicate verbally create constant friction.

Async judgment. Strong remote workers know when something needs a real-time conversation and when it can be handled async. They don't default to "let's hop on a call" for every question, but they also don't try to handle truly complex issues over Slack.

Proactive communication. In an office, you can see when someone's stuck, frustrated, or off track. Remote, you can't. Workers who proactively share status, raise blockers early, and surface what they don't know are easier to manage and more reliable.

Comfort with ambiguity. Remote work involves more decisions made without confirmation. Strong remote workers can move forward with reasonable judgment and check in later. Weak remote workers freeze without clear direction.

The questions below test for these.

Questions about self-management

These surface whether the candidate can structure their own work without external pressure.

Walk me through what a typical workday looks like for you. When do you start, when do you finish, how do you structure the day?
Tell me about a time you got off track on a project. What pulled you off, and how did you get back?
Describe how you decide what to work on first when you sit down in the morning.
How do you handle days when motivation is low?

What to listen for: Concrete habits. Strong remote workers can describe their actual routines: when they start, what they do first, how they manage focus, when they take breaks. Weak remote workers either describe an idealized day they don't actually live, or admit they let the day shape them.

The fourth question is especially useful. Low-motivation days happen in any role, but remote workers can't rely on the office environment to carry them through. Strong candidates have specific strategies (smaller tasks, environment change, taking a real break). Weak candidates either deny having low days or describe just powering through.

Questions about written communication

These test how clearly and thoughtfully the candidate writes.

Walk me through a recent piece of writing you did at work. What was it for, and what made it work?
Tell me about a time you had to communicate a complex idea in writing. How did you approach it?
Describe how you decide what goes in a Slack message versus a longer document.

What to listen for: Awareness of communication craft. Strong remote workers think about their writing. They know when to use bullet points versus prose, when to write long versus short, when to over-communicate context. Weak remote workers treat writing as utility and put no thought into it.

A useful complement to these questions: review the candidate's written communication during the hiring process itself. How they write emails, take-home submissions, or follow-up messages tells you more than what they say about their writing.

Questions about async work

These test whether the candidate uses async tools well or defaults to meetings.

Tell me about a time you handled a complex problem entirely async. How did it go?
Describe a situation where you suggested switching from a meeting to async (or vice versa). What was the decision?
Walk me through how you decide whether something needs a meeting or a document.
Tell me about a time async communication broke down on a project. What happened, and what did you do?

What to listen for: Practical judgment. Strong remote workers know that some things genuinely need a meeting (high-bandwidth discussions, sensitive topics, brainstorming) and some don't (status updates, decisions with clear options, work that has a document). Weak remote workers either default to meetings (which makes async teams miserable) or refuse to meet ever (which makes complex work impossible).

Questions about proactive communication

These test whether the candidate shares status, blockers, and questions on their own.

Walk me through how you usually check in with your manager. How often, in what format, on what topics?
Tell me about a time you were stuck on something. How long did you stay stuck before raising it?
Describe a time you flagged a problem before it became a real issue.
How do you communicate progress on a long-running project?

What to listen for: Whether they communicate by default or only when asked. Strong remote workers err on the side of over-communicating. They share status updates, flag blockers early, and don't wait for managers to chase. Weak remote workers go quiet when stuck.

The second question is especially predictive. Candidates who stay stuck for days before asking for help are hard to manage remotely. Candidates who ask for help quickly and well are dramatically more productive.

Questions about handling isolation and ambiguity

Remote work can be lonely, and most remote roles involve more ambiguity than in-office equivalents. Test for both.

Tell me about how you stay connected to teammates when working remotely. What works for you?
Describe a time you felt isolated or disconnected at work. What did you do about it?
Tell me about a time you had to make a decision without being able to confirm with anyone. How did you handle it?
Walk me through how you build relationships with new colleagues when you don't share an office.

What to listen for: Self-awareness and active strategy. Strong remote workers know they need to invest in connection and have specific habits (regular 1:1s, async social interaction, in-person meetups when possible). Weak remote workers either deny needing connection or talk about it abstractly.

Questions about remote experience (if any)

For candidates with remote experience, get specifics.

Walk me through your most recent fully remote role. What was the operating model, and what worked or didn't?
Tell me about something that surprised you about working remotely.
Describe how your previous team handled difficult conversations remotely.

What to listen for: Real reflection on what's actually different about remote work. Strong candidates can describe specific differences (more written work, more deliberate communication, harder to read tone). Weak candidates describe it as "basically the same as in-office, just from home." That's usually a sign they haven't really adapted.

Questions for candidates with no remote experience

For candidates who've never worked remotely, you're testing for traits that predict adaptation.

Walk me through your routine and habits in your current role. How would they change if you worked from home full-time?
Tell me about a time you've worked on something with limited supervision. How did you structure the work?
Describe how you'd build relationships with new colleagues you'd never met in person.
What are you most worried about with going remote?

What to listen for: Self-awareness about the transition. Strong candidates have thought about what would actually change for them and have specific concerns. Weak candidates either dismiss the differences or panic about them.

The last question is especially useful. Candidates who can name a real worry usually have thought about the transition seriously. Candidates who say "nothing, I think it'll be great" often haven't.

A practical test: how they show up in the interview itself

A lot of remote-work signal comes from how the candidate handles the interview process itself.

Are they on time? Punctuality matters more remote, where you can't see someone walking in late.

Is their setup professional? Not the equipment (we don't all have ring lights), but the basics: good audio, no constant disruptions, ability to share screen if asked.

How do they handle a tech issue? Things break. Strong candidates troubleshoot calmly. Weak candidates get flustered or blame the tool.

How do they communicate between interviews? Their email follow-ups, scheduling responses, and take-home submissions all show their written communication in action.

These observations are often more predictive than answers to remote-specific questions. Pay attention.

Red flags for remote roles

A few patterns to watch for.

Reliance on managers for structure. Candidates who describe needing close oversight, frequent check-ins, or detailed direction will struggle remote.

Negative views of async communication. Candidates who say "I just prefer in-person" or "Slack feels impersonal" can adapt, but they need to want to. If they don't want to, they'll resist remote norms forever.

Vague descriptions of past remote experience. Candidates who can't describe what was actually different about working remotely usually weren't doing it well.

Underestimating the loneliness. Candidates who claim remote work has no downsides for them often haven't done it long enough or are overselling.

Treating it as a perk. Candidates who frame remote work as a benefit they want, rather than a way of working they're skilled at, often think about it from the wrong angle.

Build it into your structured interview

Remote-specific questions belong in your structured interview, not as a separate fit check. Build them into the hiring manager round, score with a rubric, and debrief like any other competency.

Build your free interview guide with Oryx

Previously in this series: Interview Questions to Assess Culture Fit (Without Bias)
Next in this series: Interview Questions for First-Time Hires (Entry Level)