Return-to-Office · Primly Community

asking about remote policy in a job interview without looking like you don't want to work

quietquit_quincy · 4 replies

There's this persistent idea that asking about remote work in an interview signals you're lazy or not serious. It's wrong, but it shapes how you have to frame the question if you don't want to set off alarm bells in a company where the culture is office-first.

I've been interviewing while employed for a while and I've tested different approaches. Here's what I've found.

What reads badly: asking about remote in a first screener before you've said anything about why you're excited about the role. That ordering matters. Enthusiasm first, logistics later.

What doesn't read badly at all: asking how the team collaborates day-to-day, what a typical week looks like, how cross-functional work happens. These are legitimate process questions that happen to reveal location culture. A team that does weekly async standups and documents decisions in Confluence is probably remote-friendly even if the job posting says hybrid.

The question I like: "What does a typical Tuesday look like for someone in this role?" If the answer is "usually at their desk in the office, couple of internal meetings, lunch break" you know where you stand. If it's "depends on the week, sometimes remote, sometimes in for planning sessions," that's a different signal.

What interviewers actually flag: candidates who seem uninterested in the role itself and only care about the perks/flexibility side. If every question is about vacation, remote policy, and hours before you've shown real curiosity about the work, that's the pattern that reads as a red flag. Not the individual question.

So if you want to ask about remote: make sure you've asked at least two substantive questions about the work first. Then the location question fits naturally as "thinking about the day-to-day, how much in-person time does the team typically do?"

Also: people asking about commute, childcare adjustments, timezone overlaps. All of these are real considerations, and most thoughtful interviewers understand that. The companies that penalize you for these questions are probably telling you something about their culture.

4 replies

ux_uma

Recruiter here: "what does a typical Tuesday look like" is actually a really good question in general, not just for the remote signal. It shows you're thinking concretely about fit and I've never once thought it was a red flag.

analyst_ana

I've been scared to ask this because I had one recruiter tell me that asking about remote in a first call "sends the wrong message." Did I read too much into that?

quietquit_quincy

Some recruiters are rigid about this, especially at companies where the exec team has made RTO a cultural point. That recruiter was probably at a place where the culture is pretty office-first and they've been trained to notice it. On the flip side, if the question tanks your candidacy there, maybe that's information about fit.

mobile_mara

"the companies that penalize you for these questions are probably telling you something about their culture" should be the last line of every interview prep guide, honestly.