What is geographical discrimination?

What’s the difference between geographical discrimination and national origin discrimination?

Geographical discrimination is bias tied to where someone lives or is perceived to be “from,” like a city, region, or country. National origin discrimination is a legal concept in many places and focuses on someone’s ancestry, birthplace, ethnicity, accent, or association with a particular nationality or ethnic group. Here’s why it matters: a “location” rule in hiring can quietly drift into national origin discrimination if it’s really being used to screen out people from certain countries, languages, or ethnic communities, even when the policy is framed as a time zone or “culture” issue.

What are the most common “reasonable-sounding” policies that create geographical discrimination in remote hiring?

It usually doesn’t show up as “we don’t like people from X.” It shows up as policies that sound operational but aren’t tightly linked to the job. The usual culprits are overly narrow time zone requirements, “must be in HQ city” rules for roles that rarely need office access, blanket pay cuts tied to someone’s address with no compensation philosophy behind it, and “communication” standards that penalize accents or local writing styles. If you can’t explain the requirement as a core job need—and apply it consistently—you’re in risk territory, even if geography isn’t a protected class where you operate.

How do you decide when a location requirement is legitimate versus discriminatory?

Use a simple test: can you tie the location requirement to a measurable business constraint, and would the job fail without it? Legitimate examples include roles that require in-person access to equipment, regulated environments that require local licensing, or roles that need real-time coverage during specific hours because the work is synchronous. Red flags include “team preference,” vague “culture fit,” or requirements that only appear after you see a candidate’s address. Document the rationale, keep it role-specific, and revisit it when the operating model changes—especially if the team is already functioning remotely.

What should you do if an employee says they’re being treated differently because of where they live?

Start by treating it like a serious People Ops issue, even if it’s not clearly illegal in your jurisdiction. Ask for specific examples, pull the decision trail (job level, comp bands, performance notes, promotion criteria, time zone expectations), and look for inconsistency across comparable roles. Then fix the system, not just the moment: clarify the policy, train the manager, and create a documented standard for future decisions. If the situation touches protected characteristics—like national origin, race, or disability—bring in legal counsel early, because what looks like “geography” on the surface can overlap with protected-class discrimination fast.

How can we set fair pay for a global team without penalizing people based on their location?

You don’t have to choose between fairness and financial reality, but you do need an explicit compensation philosophy. Many teams pick one of a few approaches: a single global band (same pay for the same level), a structured location-based approach with clear tiers and guardrails, or a hybrid that anchors to role value while adjusting for local market and statutory costs. The key is consistency and transparency—define what drives differences (market rates, cost of employment, taxes, and benefits), apply it the same way across the org, and pressure-test outcomes for adverse impact. If you’re building this from scratch, Oyster’s Salary Insights can help you benchmark by country so your pay decisions are grounded in real market data, not stereotypes or negotiation dynamics.