Remote jobs by time zone: what employers ask for in 2026

Most remote postings never mention a time zone at all. They name a city, because the applicant tracking system makes them: Greenhouse states that a job post "won't save unless you add at least one valid Searchable location, even if Work type is set to Remote." The pool those postings come from is also narrower than the phrase "remote work" suggests — 22.6 percent of workers teleworked or worked at home for pay in March 2026, according to the Current Population Survey (BLS, published April 16, 2026). And when an employer does have a real geographic constraint, it is rarely written as a time zone. It is written as overlap hours, which is a different requirement with a different answer.

What follows separates the three things that get collapsed into "remote by time zone": where a company can employ you, where the posting says the job is, and when you have to be at your desk.

How much remote work is there for the job you are applying to?

Customer Support Specialist and Recruiter sound equally remote-friendly. They are not. A Customer Support Specialist is counted by BLS as a Customer Service Representative; a Recruiter falls under Human Resources Specialists. Their pay, their direction of travel and the telework rate of the occupation group each one sits in all differ.

How to read this. The telework column is not the share of postings that are remote. It is the share of people in that broad occupation group who teleworked at all during the survey week in August 2026, including anyone who did so for a few hours. A Recruiter is fishing in a group where more than one in three people teleworked that week. A Customer Support Specialist is fishing in one where fewer than one in four did, in an occupation BLS projects will lose 141,800 jobs between 2025 and 2035. Neither figure tells you what any individual employer will allow, and no federal series records time-zone requirements at all.

What the location field on a posting actually is

The field is a database object with several jobs to do, and describing your permitted whereabouts is only one of them. Greenhouse's own configuration guide is blunt about the first of those jobs: job post location is a required field for all job posts, and administrators can narrow it further to a list of offices or a custom dropdown so that nobody types anything unexpected into it.

The location field, as the two systems define it

Vendor documentation on how a remote posting's location is stored and displayed. An em dash means that vendor's page does not address the row.

	Greenhouse	Workday
Location on a remote post	Required — the post "won't save unless you add at least one valid Searchable location, even if Work type is set to Remote"	A primary job posting location on the requisition, which displays to candidates when they apply
How "remote" is expressed	A work type set to Remote, plus searchable locations at city or country level	A custom remote value the employer creates for the requisition
More than one location	Up to seven searchable locations per post on third-party job boards	Additional job posting locations alongside the primary one
Country-only location	Allowed only for remote roles	—
Statewide remote	Not currently supported	—
What the location carries behind the scenes	—	Time zones and locales, which assigned workers inherit automatically
What you store as a candidate	Worksite preference — in-office, hybrid or remote — plus location, in a saved profile	—

Two rows there do most of the work. Greenhouse allows a country-only searchable location only for remote roles, which makes "Remote — United States" a deliberate signal rather than a shrug. Greenhouse also does not currently support statewide remote, so an employer willing to hire anywhere in Texas has to choose between naming individual cities and naming the whole country. That single limitation produces postings that look narrower than the employer's actual appetite, and it produces others that look far broader.

Why a remote posting still names a city

Because in Workday the location record is doing payroll and configuration work. Workday's setup guidance says locations carry "time zones and locales so that workers automatically inherit those attributes" — attach a new Recruiter to the Chicago site and a default clock comes with the assignment, whether or not that Recruiter ever sees Chicago. The same guidance tells administrators that when workers are assigned to remote sites they should consider the implications of assigning them to physical locations, and suggests grouping those workers "by state, province, or other logical designation" instead. That is a vendor telling its customers, in a setup manual, that the physical site on a remote worker's record is a convenience rather than a fact. The city anchors the employment record. It is not automatically a fence.

The most expensive assumption in a remote job search is that a city printed on a posting is a restriction. The evidence against it is sitting in the vendor documentation. One system refuses to publish a remote post without a location value; the other attaches a location to every requisition because pay and calendar hang off it. A field that cannot be left blank carries no information about whether anyone meant it. Where a genuine restriction exists, it appears a second time — in the posting body, in the shift description, or in a screening question asking which state you would be employed in. One mention is a database requirement. Two mentions is a rule.

Why the same remote job shows up in three different cities

Because one posting can carry up to seven searchable locations, and the boards do not all render them the same way. Greenhouse says remote posts "are surfaced based on the Searchable locations you add" and that "how those locations appear can vary by third-party job board." Its own example spells out the consequence: a remote post with Denver, Colorado as a searchable location is findable by people searching for remote jobs in Denver, and if more searchable locations are added, "some third-party job boards may display those as separate job posts by location."

So a single Recruiter requisition can surface as several distinct-looking listings, each stamped with a different metro, all pointing at the same req and the same hiring manager. Indeed picks the post up within 48 hours; on LinkedIn Limited Listings, jobs "can be posted in any location and appear as remote." None of those city stamps is a residence requirement. They are search-visibility settings chosen by whoever wrote the post, working around a system that has no way to say "anywhere in Texas."

The practical move is to stop judging a remote role by the city on the aggregator and open the employer's own careers page instead. That version is the canonical one — the same fields, without the board's rendering on top. It is also where the shift hours and the excluded-states list usually live, because those are written into the description rather than into a location field, and descriptions survive syndication in a way structured fields do not.

What a time-zone line means when it appears

When employers do write hours into a posting, the phrasing falls into a few recognisable shapes.

This table is interpretation, not measurement, and the distinction matters. BLS publishes no data on time-zone requirements, and neither Greenhouse nor Workday documents what an employer intends by words typed into a free-text field. What the documentation does establish is the mechanics underneath: which fields are compulsory, which ones are searchable, and which ones quietly set a default clock for whoever gets hired.

Does "US Remote" mean any US time zone?

No. It answers a legal question rather than a scheduling one. A Customer Support Specialist role posted as "Remote — United States" with a shift listed as 11am to 8pm Eastern is fully open to someone in Phoenix and closed to someone who has to finish by 3pm local time. Read the shift line, not the country line.

The industries where the overlap actually exists

Telework is not spread evenly across the economy, and the gap between sectors is far wider than the gap between one year and the next.

Share of workers who teleworked or worked at home for pay, by industry, August 2026

People at work during the survey week who teleworked for any of their hours. Not a count of remote job postings.

Financial activities		51.2%
Information		49.1%
Professional and business services		42.8%
Nonagricultural industries		21.8%
Education and health services		17.8%
Leisure and hospitality		6.7%

This is why the same title behaves so differently depending on who is hiring for it. A Recruiter at a professional services firm sits in a sector where 42.8 percent of workers teleworked in August 2026. A Recruiter for a hospital system sits in one at 17.8 percent, and the job description may be word for word the same. Search the title alone and both roles come back looking alike; the industry, not the title, predicts whether a conversation about hours is even available to have.

There is a further wrinkle in how those remote hours are split. In the first quarter of 2024, 47.9 percent of teleworkers worked all of their hours from home and 52.1 percent worked only some of them, per BLS's analysis of the Current Population Survey. For that slim majority, the city on the posting is not decorative at all — it is where they go on Tuesdays. A posting naming a metro and a hybrid schedule is describing a commute, and no amount of time-zone flexibility substitutes for living inside one. Worth noting too: the survey question only reaches people who were at work during the reference week, so anyone on leave that week is outside these figures entirely.

What to put in your own location field

Put where you live. The field feeds recruiter search, and in Workday it connects to a location record that sets a default time zone for whoever ends up assigned to it, so a city you do not live in becomes a payroll and tax problem at offer stage — a worse outcome than being missed in one search. Greenhouse's candidate profile stores a worksite preference alongside location, with three values: in-office, hybrid or remote. Setting that field deliberately does more for you than editing the city does.

Where there is room to be strategic is in the fields that accept sentences rather than dropdown values:

• In the location field itself, write your actual city and state. Nothing else belongs there.
• In a preferred-location or worksite-preference field, choose remote plainly rather than naming an aspirational city.
• In the cover letter or the "anything else we should know" box, state your hours in the employer's time zone once: "Based in Denver, available 7am–4pm Mountain, which is 9am–6pm Eastern." That sentence answers the only version of the question that actually matters, and it answers it before anyone has to ask.
• In a screening question asking which state you would work from, name the state you can be employed in today, not the one you are thinking of moving to.

If you are applying for this role

Three specifics, whether you are chasing Customer Support Specialist or Recruiter postings.

Search the adjacent titles. For support work, that means Customer Service Representative, Customer Support Associate and Client Services Specialist — BLS counts 2,666,000 customer service representatives with a median wage of $44,770 as of May 2025, and the postings for them are scattered across all three phrasings. For recruiting, add Talent Acquisition Specialist and Recruiting Coordinator to the Human Resources Specialist title BLS uses, an occupation of 939,700 people with a median wage of $75,940 in the same estimates.

Expect the hours question, not the map question. Write one sentence giving your city and your availability translated into Eastern time, and reuse it in every application that offers a free-text box.

Ask one question on the first call. Not "is this really remote" — ask which hours the team expects overlap on, and whether the location on the posting is a payroll location or a residence requirement. Recruiters answer that one directly, because they are the people who filled the field in.

If the repetitive part is typing the same city, worksite preference and availability into every form, the platform fills those fields from your profile, leaving the sentence about your hours as the only thing you write fresh.