Asking about return to office before you sign
Remote today is not remote in writing, and a verbal remote today can turn into three days a week in an office by next spring with nobody along the way having technically lied to you. Four questions, asked before you sign rather than after, usually surface the real plan.
Why this is worth asking about at all
Given how rare a genuinely remote match already is in plenty of fields, protecting the ones you do find is worth real effort. The real supply of remote jobs covers just how small that real number can be in a given industry. A role that clears every other bar and then quietly reverses its remote policy six months in is a worse outcome than never finding the role at all, because you have already turned down other options and built your life around this one.
The first question: what does the offer letter actually say
A recruiter's verbal answer and an offer letter's written terms are not the same document, and only one of them is enforceable. Ask, plainly, whether the remote arrangement will be written into the offer letter itself, and if it will not be, ask why not. A company confident in its own policy usually has no problem putting it in writing. One that hesitates is telling you something too, even if nobody says it out loud.
It also helps to ask who specifically owns the policy: HR broadly, or the hiring manager for this one team. A recruiter's answer describes company policy. A hiring manager's answer describes what will actually happen to your calendar, and the two do not always match.
The second question: has this changed in the last two years
Policy on paper is a snapshot. History is a trend. Asking whether the remote or hybrid policy has changed recently, and in which direction, tells you whether you are looking at something stable or something mid slide toward more office time. A team that moved from fully remote to two days a week last year is more likely to move again than a team that has held steady the whole time. Most interviewers will answer this honestly if you ask it as a plain question rather than an accusation. A useful way to phrase it: has anything about where people are expected to work changed since you joined, and if so, what prompted it. That framing tends to draw out a real answer rather than a rehearsed policy summary.
It is also worth remembering that a verbal arrangement made during a hiring process, however sincerely meant, is not the same thing as a commitment the company is structurally prepared to keep. Teams grow, offices get leased, and a policy that feels settled during an interview in the spring can look different by the time a lease renewal comes up in the fall.
The third question: who else on the team is fully remote today
A policy statement describes what is allowed. A specific, named example describes what actually happens. Asking whether anyone on the team you would be joining is fully remote right now, and roughly how far they live from the nearest office, turns an abstract policy into a concrete fact you can weigh. If the honest answer is nobody, or only people hired years ago under an older policy, that tells you something the job description never will.
It is worth asking this one in a way that invites a real name or a rough count, not just a yes, since a vague confirmation that remote people exist somewhere in the company says nothing about the specific team you would actually be joining.
The fourth question: what happens if the policy changes after I start
No employer can promise a policy will never change, and asking them to would be an unreasonable question. A reasonable version of the same question is what happens to people already in the role if it does: are existing remote employees grandfathered in, or does everyone move together when leadership decides to move. The answer will not be a guarantee either way. It will tell you whether the company has even thought about the question, which is itself useful information.
A fifth signal that costs nothing to notice
If any part of the process happens in person, the office itself is worth a look. A floor of empty desks, a kitchen stocked for a headcount that clearly no longer works there, or a reception area that has to check with someone before letting a badge visitor through all say something a policy document will not. None of this is proof of anything on its own. Combined with a direct answer to the four questions above, it either confirms what you were told or gives you a reason to ask a sharper follow up before you sign anything.
Where the answer should land before you accept
None of these four questions has a single right answer that applies to everyone. What matters is deciding, before you are sitting across from an offer with a deadline attached, what answer would change your decision. Questions worth asking your interviewer covers how to work questions like these into an interview naturally, as part of you evaluating the role rather than as a challenge to the interviewer. If the answers you get back describe a policy that is recent, unwritten, and inconsistently applied across the team, that is real information, not paranoia, and it belongs in the same column as salary and title when you weigh the offer. When to walk away from an offer covers the handful of situations, an unwritten remote promise chief among them, worth treating as a real reason to pass even on an offer that looks good everywhere else.
None of this guarantees an outcome either way. It just means the decision to accept happens with real information in hand, instead of a comfortable assumption that today's arrangement is permanent simply because nobody mentioned otherwise.
iapplyai.app flags a role's stated workplace type as part of every match it scores, but the honest answer to how firm that policy really is only comes from asking a person these four questions directly.
