Questions to Ask in a Remote Job Interview

The best questions to ask in a remote job interview are about how the work gets done without an office: which hours you must overlap with, where decisions are written down, how many meetings fill a week, how onboarding works, what equipment the company pays for, how often you are expected in person, and whether remote employees actually get promoted. Ask for recent, concrete examples instead of policy statements, and get the location terms in writing before you accept.

Remote jobs go wrong in ways office jobs don't: an early standup nobody mentioned, a "remote" team that expects you in on Tuesdays, promotions that reward whoever is in the room. For general questions about the role and team, see our questions to ask the interviewer guide; this one covers what is specific to remote work.

1. Find out what kind of remote this is

"Remote" covers everything from a company with no offices to an office-first team that lets one person work from home. Companies use these labels loosely, so confirm with questions:

• "Is this role fully remote, hybrid or office-based, and will the offer letter say so?" A clear answer and a willingness to put it in writing is the baseline.
• "Are there states or countries I can't work from?" Many employers only hire in certain locations, partly because an employee working from a new state can create payroll-tax and other compliance obligations there.
• "Has the policy changed in the last two years, and does it vary by team?" Amazon, for example, moved corporate employees from at least three office days a week to five starting January 2, 2025. How a company handled its last change is a useful hint about the next one.

2. Time zones and working hours

A "flexible" job with a daily 9 a.m. Eastern standup means a 6 a.m. start if you live on the West Coast.

• "What hours do I need to overlap with the team, and in which time zone?" Good answers are specific, such as a four-hour window in one named time zone. "We're flexible" from a team with fixed daily meetings deserves a follow-up.
• "Where are my manager and the people I'll work with most closely?" Your real constraint is the handful of people you depend on, not the whole company.
• "When meetings span time zones, do the times rotate?" Listen for who takes the early or late slot, and whether it is always the same people.
• "What response time is expected on chat during my working hours?" Minutes and "by end of day" are very different jobs.
• "How does on-call work across time zones?" Ask whether pages go to whoever is awake or whether you could be woken at 3 a.m.

GitLab, which is all-remote, publishes a 12-question self-test for remote companies in its public handbook. One question is whether people can define their own working hours; where a role needs set hours, it says strong remote teams add backup coverage or better documentation so work doesn't stall when one person is offline.

3. Async habits, documentation and meetings

One of the clearest differences between good and bad remote teams is whether information lives in writing or in people's heads. GitLab's self-test asks whether most communication about work happens asynchronously, whether the company works "handbook-first," and whether communication expectations are documented in one place. You can probe all three:

• "If I wanted to know why a technical decision was made six months ago, where would I look?" Good: a design doc, RFC, ticket or decision log. Weak: "Just ask whoever was in the meeting."
• "Do you write design docs before building, and how are they reviewed?" Written review gives remote engineers a voice in decisions they could not attend live.
• "What happens to a question I post at the end of my day?" Ideally, it has a written answer by the time you log back on.
• "Roughly how many hours of recurring meetings does someone in this role have each week?" A number beats "not too many."
• "Could you walk me through last week for someone on the team?" A real week is harder to polish than a policy.
• "Are cameras expected on in every meeting?"
• "When some people are in a conference room and others are remote, how do you run the meeting?" GitLab's handbook recommends avoiding these mixed "hybrid calls," and when they happen, having everyone use their own camera, headset and screen even if they share a room. A team that crowds around one room camera usually hasn't thought about its remote people.

4. Onboarding and mentorship when nobody sits next to you

Onboarding and mentorship matter most early in a career. A study of software engineers at a Fortune 500 company, summarized by the Federal Reserve Bank of New York, found that while offices were open, engineers whose whole team sat in one building received 22 percent more comments on their code than engineers with teammates in other buildings. The effect showed up mostly as feedback from experienced engineers to junior ones. After the offices closed and everyone worked remotely, the gap largely disappeared.

The risky setup, in other words, may be less remote work itself than being the one distant person on a team that mostly sits together. These questions show which situation you would be in:

• "What do my first two weeks look like? Is there a written onboarding plan?"
• "Will I have an onboarding buddy, and is time set aside on their calendar for it?"
• "How many people on the team work remotely full time? Would I be the first?"
• "When did your most recent remote hire start, and what did they find hardest?"
• "How do junior engineers get code review and pairing time?" Especially important for new grads and career changers.
• "Who do I ask when I'm stuck and my manager is offline?"

5. Equipment, stipends and location-based pay

These logistics questions usually go to the recruiter, once you are past the first screen.

• "What equipment do you provide, such as a laptop, monitor and headset, and do I return it if I leave?"
• "Is there a home-office or internet stipend? Is it one-time or recurring?"
• "Do you reimburse a coworking space?" GitLab's self-test treats funding individual workspaces and reimbursing out-of-home office space as a mark of a mature remote company.
• "Is pay set by location? What happens to my salary if I move?" Some companies set pay bands by geography; others pay one rate wherever you live. Know which applies before you negotiate. Our salary negotiation guide covers the rest of that conversation.

6. In-person expectations

Plenty of good remote companies still bring people together. What you need is a number, not a mood. GitLab's self-test asks whether a company has "a documented and defined in-person strategy," and gives retreats, company-wide gatherings and in-person onboarding cohorts as examples.

• "How often does the team meet in person, and is attendance required?"
• "Who pays for travel and lodging, and how much notice do you give?"
• "Is any part of onboarding on-site?"
• "Do people who live near an office go in on set days? Do decisions tend to happen on those days?" If the in-office group effectively runs the team, remote staff become a second tier.

Watch for "we like people to come in when they can" with no frequency attached. Ask what that has meant in practice over the last three months.

7. Promotion fairness for remote staff

Proximity bias, giving more credit to the people you see in person, is a common worry for remote candidates. The evidence is mixed:

• A randomized trial at Trip.com, published in Nature in 2024, found that employees who worked from home two days a week showed no difference in performance reviews or promotions over the following two years compared with full-time office staff, and their quit rates fell by a third.
• That trial covered hybrid work at one company. The code-review study above adds a different concern: engineers separated from their teammates got less feedback, and the researchers suggest that remote work's short-term productivity gains may come at the cost of long-run skill development.
• Manager trust matters too. In Microsoft's 2022 Work Trend Index survey of 20,000 people in 11 countries, 85% of leaders said the shift to hybrid work made it hard to be confident people were productive, while 87% of employees said they were productive.

Research can't tell you how one company behaves, so ask:

• "Has anyone on this team been promoted while working remotely in the last year or two?" A name and a story beat any policy.
• "Are my manager and their manager remote?" GitLab's self-test puts "Are senior leaders remote by default?" first, arguing that when leaders default to the office, decisions get made less transparently.
• "How are promotion cases built: documented results, or a manager advocating in a room?" GitLab suggests a written promotion document as a guard against proximity bias.
• "How do managers judge performance remotely? Do you use activity-monitoring software?" Results-based answers are a good sign; keystroke or screenshot tracking tells you how much trust to expect.

8. How to spot "remote in name only"

Some "remote" jobs run like office jobs, or stay remote only until the policy changes. No single signal proves it, but several together are worth a closer look:

9. Who to ask, and how many questions

Prepare six to eight questions, ask two or three per conversation, and follow up on vague answers with "Can you give me an example from the last month?"

The questions run both ways. Remote employers commonly ask how you manage your time, write updates and stay unblocked across time zones, so have two or three specific stories ready and rehearse them out loud, for example in a free AI mock interview in CoPilot Interview, which reads questions built from your résumé aloud and scores each spoken answer. For the video setup itself, see our live coding tips for Zoom and Teams.

FAQ

What are good questions to ask in a remote job interview?

Ask which hours you must overlap with, where decisions are documented, how many meetings a typical week has, how onboarding works, what equipment is provided, how often you must be in person, and whether remote employees on the team have been promoted.

How can I tell if a job is really remote?

Ask whether the offer letter will say the role is remote, which locations you can work from, where your manager and teammates are based, and how often in-person attendance is required. Vague answers like "remote for now" deserve a specific follow-up.

Is it OK to ask about in-office requirements in an interview?

Yes. Office days, travel frequency, who pays for travel and how much notice you get are reasonable logistics questions, and the recruiter is usually the right person to ask.

Do remote workers get promoted less often?

The research is mixed. A 2024 Nature study at Trip.com found no difference in promotions for hybrid workers over two years, while a study of software engineers found that those separated from their teammates got less code feedback. Ask whether remote employees on the team have been promoted recently.

How many questions should I ask in a remote interview?

Prepare six to eight and ask two or three per conversation: logistics and pay to the recruiter, team habits and promotions to the hiring manager, and day-to-day reality to future teammates.