Three months after a new Director of Engineering starts, the VP of Talent looks at a candid 90-day review and a calendar that says the role is open again. The interview loop scored 4.6 out of 5 on every panel. The first month was clean. By week ten, cross-functional partners have stopped looping the new hire in, and the CTO is forwarding "what's the status?" emails up the chain. Nothing about the candidate has changed. The job did. The role is fully remote, and the rubric the panel scored against was built for an office.
About a quarter of U.S. workers age 25 and older still telework in some form, and the share rises sharply with role seniority and education. In the first quarter of 2024, 43.6% of workers with an advanced degree teleworked, alongside 38.4% of bachelor's-only graduates. Distributed work has not collapsed back to a 2019 baseline. Gallup's most recent panel finds 51% of remote-capable U.S. employees work hybrid as of Q2 2025, with only 21% fully on-site. For most knowledge-work organizations, distributed roles aren't a side bucket on the headcount plan. They are the headcount plan.
The standard interview rubric was built for a different job
Most interview rubrics still test the in-office version of the role. They score collaboration as something that happens when a hiring panel pulls you into a room. They score communication as the back-and-forth in a one-hour Zoom that rewards quick verbal recall. They lean on three signals that travel well under ambient supervision and degrade quickly without it: credentials, polish, and presence.
In an office, weak performers are partially carried by the system around them. A hallway question prompts an unblock. A nearby manager notices the work has stalled. A teammate sees the unread Slack and walks over. Remote work strips out those bridges. A new hire who doesn't ship in a distributed team often isn't worse at the job; they were assessed against a job that does not exist in this org.
Remote work surfaces three signals a standard rubric never tested
The first is written and asynchronous communication clarity. In a distributed team, half the work happens in writing: a ticket, a Loom, a design doc that has to make sense without its author present. Candidates who interview well on camera can still write paragraphs that bury their conclusion, ask questions that ignore prior context, or send updates that force a manager to chase. None of that shows up in a thirty-minute behavioral interview.
The second is responsiveness under ambiguity. Office work has a default routing: the person sitting next to you. Remote work doesn't. The behavior that matters is what the candidate does when the spec is unclear, the partner team has gone quiet, and the deadline is in two days. Do they write a one-paragraph note proposing a path and asking for a thumbs-up by end of day? Do they hold the work and wait? A standard interview rarely puts that question on the table.
The third is self-direction with proxy signals. In an office, a manager picks up motivation problems by walking past a desk. Distributed managers read a board, a commit log, and a weekly write-up. Remote-ready candidates show evidence of running their own tempo: the artifact they used to keep themselves on track, the cadence they set with a manager, the tool they used to surface blockers before being asked. Generic "I'm proactive" answers do not reveal this.
What remote-ready screening actually looks like
Three changes to the format catch most of the gap.
Front-load an asynchronous exchange. Before the live conversation, send a written prompt that mirrors a real artifact the role produces: a status update for a delayed project, a one-page proposal, a candidate response to a vague design ask. Score it against the rubric a real teammate would use. Clarity of conclusion. Surfacing of risks. A reader who doesn't need to ping back for context.
Use a work sample in the medium the role uses. If the role lives in writing, run a written exercise. If it lives in async video, run an async video exercise. Live whiteboard sessions are a poor proxy for work that mostly happens at 9 p.m. when the candidate is alone with the problem.
Add structured behavioral prompts that target self-direction. Replace "tell me about a time you took initiative" with "walk me through a week in your last role where your manager was on PTO and a partner team was blocked on you." The first prompt invites a polished story. The second forces evidence.
The downstream cost of the wrong rubric
When the rubric and the role diverge, a predictable thing happens after the hire starts. Gallup's most recent data finds only 54% of managers who oversee remote workers strongly agree they trust their team to be productive remotely. That trust gap is rarely about ideology. It accumulates after a series of post-hire surprises: a strong interviewer who can't write a status update, a polished panel performer who stops shipping when no one is in the room. The org stops trusting the cohort because the screen never tested the cohort against the job.
If your headcount plan includes distributed roles, the question is not whether your hiring funnel is fast enough. The question is whether the rubric at the top of the funnel is testing the right job. A panel that scores presence and verbal recall will find candidates who score well on presence and verbal recall. A panel that scores written clarity, responsiveness under ambiguity, and self-direction with proxy signals will find candidates who can run a remote role. The two are not the same, and the second one is harder to design, which is why most orgs are still hiring against the first.
Want to see what structured screening looks like for a remote role on your req volume? Book a pilot and we'll run your next role through the Eximius workflow.