What questions should I ask in the interview to find out if a flexible job is actually flexible?
Six questions, asked in order, will tell you almost everything you need to know. Memorize them and ask them in the first or second interview. Each one is calibrated to surface a specific kind of red flag.
1. "Walk me through a typical Wednesday for someone in this role." The answer reveals the actual meeting load and the rhythm of the work. Vague answers ("oh, every day is different!") usually mean unbounded chaos. Specific answers ("two 30-minute syncs, one customer call, then deep work in the afternoon") tell you the job is structured.
2. "How are decisions documented after they're made in meetings?" This is the litmus test for async culture. If the answer is "we usually share notes in Slack," the culture is sync-default with documentation as an afterthought. If the answer is "we have a doc per decision in our wiki, with the author, the date, and the alternatives considered," the culture is async-first and you can mostly catch up on a week even if you missed every meeting.
3. "What's the parental leave policy in writing, and what does the ramp-back look like?" The "in writing" matters. Some companies tell candidates "we're really supportive of parents" and then have an unwritten policy that turns out to be six unpaid weeks. The ramp-back question is even more telling — companies that have actually thought about it can describe a phased return; companies that haven't will improvise. Both signals matter.
4. "What's the on-call rotation expectation for this role?" Don't assume there isn't one — assume there is until proven otherwise. The good answers: "we have a dedicated SRE team, no on-call for product engineers." The acceptable answers: "one week per quarter, business hours only, with the option to swap." The dealbreaker answers: "we share the rotation across the engineering team" without further bounds.
5. "Who has the most flexible schedule on this team, and what does their week look like?" This is the secret weapon question. It surfaces whether anyone is actually using the flexibility. If the manager can name someone and describe their schedule, the flexibility is real. If the manager pauses, fumbles, and falls back to "everyone's flexible," nobody is actually using the policy and you'd be the first.
6. "What happens when someone has a sick kid and has to drop offline at 11am?" Watch the tone of the answer. The good response is matter-of-fact: "they Slack the team, we cover, no big deal." The bad response is theatrical: "we're really understanding!" with no specifics. Real flexibility is boring; performative flexibility is enthusiastic.
Beyond these six, two meta-rules: ask the same question to multiple interviewers. Companies with consistent culture will give consistent answers; companies with inconsistent culture will reveal the gap. And listen for what's not said — if you ask about parental leave and the answer pivots immediately to other benefits, the parental leave is probably weak.
Finally, the question you're really asking with all of these is: does this team have a working language for boundaries? Companies that do can describe what they do clearly. Companies that don't will tell you it doesn't matter because everyone gets along. The latter is a warning sign, not a feature.