Remote jobs that are quietly location locked
A role can say remote and still be closed to you. The three usual reasons are tax registration, a required overlap in working hours, and a hub office you are expected to visit, and all three can sit quietly inside a posting that never uses the word hybrid anywhere on the page.
Tax registration is the reason you will never see written down
Most companies are only registered to run payroll in a specific list of states or countries. Hiring someone outside that list is not a policy choice so much as a legal and accounting one: it usually means opening a new tax registration, sometimes a new payroll relationship, before the first paycheck can go out. Plenty of employers will not do that for a single hire, no matter how strong the match. This is almost never stated in the posting itself. It surfaces later, in a screener question that asks which state you currently live in, or in a recruiter call that starts with a question about your address before it gets to anything about the role.
The fix is not to take it personally. A company that cannot register in your state cannot hire you there this year, regardless of how good the interview goes. It is worth asking directly, early, rather than finding out after a final round.
Time zone overlap: remote does not mean asynchronous
A second, quieter constraint is time. Remote does not promise flexible hours. Plenty of remote teams still expect a real block of overlap, often four to six hours, so that meetings, reviews, and quick questions do not turn into a day of waiting on replies. A role can be remote in every legal and practical sense and still be closed to you if your day and the team's day do not meaningfully overlap. This rarely appears as a stated requirement. It shows up as a scheduling problem discovered during onboarding, which is a worse time to discover it than during the first screening call.
The hub requirement: still remote, still tied to a place
The third pattern is the hardest to see coming, because the role really is remote most weeks. It just is not remote every week. A hub requirement means a handful of trips a year, sometimes a full week each quarter, to an office where the rest of the team, or at least the manager, actually sits. The posting will call this remote because for most of the calendar it is true.
A single industry sweep of twelve sports employers shows how differently this plays out company to company. FanDuel's product roles sit in New York and Atlanta. Peloton's sit in New York. Hudl's sit in Lincoln, Nebraska. Strava's sit in San Francisco, and that one was hybrid even so, not fully remote. Twelve employers, and most of them tied their roles to a specific place in one way or another. The real supply of remote jobs covers the full sweep and what it says about how small the truly open pool turns out to be once you account for all three of these patterns at once.
A fourth pattern: employee status versus contractor status
A less obvious version of the same lock shows up as a difference in how you would be hired rather than where. Some companies handle out of area remote hiring by offering a contractor arrangement instead of employee status, specifically because a contractor relationship sidesteps the payroll and tax registration problem that a full employee does not. The work, the manager, and the day to day can be identical to the employee role posted elsewhere on the same page. The difference shows up in benefits, in job security, and sometimes in pay structure, and it is worth asking about directly if a recruiter offers this path, rather than assuming it is a downgrade or assuming it is equivalent without checking.
How to spot a location locked role before you apply
A few checks take less time than writing a cover letter and catch most of this in advance.
Read the states or countries list if one appears anywhere on the posting, often buried in a benefits section or an equal opportunity footer rather than the headline. Look for a named city attached to the team, even in passing, in a line like our New York based team or reporting to our Lincoln office. Read the screener questions before you fill them in: a question asking which state you currently reside in, on a role marked remote, is usually there because the answer changes whether you can proceed at all. Check whether the posting mentions core hours, standup times, or a specific time zone the team operates in, since that is often the plainest clue to a required overlap. Remote, hybrid and onsite: what a posting means covers the language patterns behind all three constraints in more detail, so you can read a posting once and catch the tell instead of finding it out during a call.
None of these checks take more than a few minutes combined, and doing them before you write a single word of an application is a better use of that time than doing them after a recruiter call that turns out to be a five minute conversation about your zip code.
What to do once you know where the lock is
Finding a location lock early is not always a reason to skip the role. Sometimes it changes the plan instead: you apply anyway and are upfront about a planned move, or you look specifically for the one employer in a field that solved this problem by going fully remote, the way the earlier sweep found exactly one company had. Applying out of state before you move covers how to handle the address field, the phone number, and the timing when you are applying somewhere you do not currently live, including the cases where that is a real, workable plan rather than a wasted application.
iapplyai.app checks the workplace type and location fields on every posting it scores, so a role with a hidden hub requirement or a tax registration limit shows up flagged instead of surfacing as a false remote match.
