Remote resume: city, zone, and eligibility in the text layer

Maya Reyes answers phones and Zendesk tickets for a regional internet provider in Austin. A B2B SaaS board posted “Support Specialist — Remote (US)” in Greenhouse. Her current resume opens with a Canva banner that says “Open to remote worldwide,” hides the email in a header box, and lists Slack, Zoom, Notion, and Asana because a blog called them remote skills. That file is not ready. The first screen is not an LLM. It is four questions: authorized to work in the United States without sponsorship; currently living in the United States; able to overlap 9 a.m. to 1 p.m. Eastern; willing to sit in Denver two days a month. Workday copies of the same requisition store those answers as candidate fields. Greenhouse stores them as custom questions. Taleo and iCIMS use dropdowns. None of them wait for a paragraph about being a remote-first communicator.

If Maya clicks Yes on US authorization and the PDF still says “digital nomad, any country,” the sourcer who opens the attachment hesitates. If she clicks No on Denver because she cannot fly, the requisition is already closed for her — rewriting “hybrid-friendly” in the headline will not reopen it. Knockouts are not preferences you negotiate in the summary. They are gates. The ATS resume rules still apply after you pass them: selectable text, standard headings, true dates. They do not replace the gates. For the broader parse-and-questionnaire pattern, keep how to pass an ATS next to this page.

What “filtered” usually means on a remote requisition is not a low model score. It is a location field that does not match the posting, a sponsorship answer that blocks the workflow, a time-zone question left blank, or an on-site day count the hiring manager already marked required. Some Workday tenants hide the rest of the apply flow until those questions are answered. Some Greenhouse boards let you finish and then drop the row from the “yes” view. Either way, the rank — human or model — never gets a turn. A 94 on a public scorer that never saw this company’s knockouts is entertainment.

The four gates, in the order they actually run

• Location: country first, then state or metro if “remote US” still means reside in the US.
• Work authorization: sponsorship Yes/No. Citizenship and a passport number do not belong on the resume.
• Time zone or overlap hours: an Eastern desk vs Central vs Pacific vs “any,” which almost never means any.
• On-site days: fully remote vs two days in a named city vs a quarterly onsite. Guessing “flexible” is a No later.

The file has to tell the same story as the form. If the contact line has no city, Workday’s location widget is empty and a recruiter search for “Austin” or “Central” misses you even after you typed Austin into the knockout. If you claim “fully remote” on the PDF and “2 days Denver” on the form, the coordinator who opens both closes the file. Tailor the resume to the posting’s nouns only after these four answers are honest. Nouns will not save a failed gate.

After the gates, sourcers still search. They type Zendesk, “Central,” “authorized,” or the metro the payroll team already approved. That search runs on the extract, not on the Canva banner. If the city and zone never made it into the body, you are invisible in the database even though you clicked the right radio buttons. Treat the knockouts as the outline of the contact line, then write the rest of the resume for the human who survives the filter.

Workday tries to hang a location on a candidate field. Greenhouse search looks for city and “remote” as nouns inside the extract. If that line lives in a header text box or a graphic, the extract can come back empty — the same failure as a missing email. “Open to opportunities globally” in a banner gives the parser nothing to store and the knockout nothing to confirm. Write the line in the body, in normal text, on one or two lines the select-all test can highlight.

A line that survives both the parser and the screen looks like this: Maya Reyes · Austin, TX · Remote (US), Central Time · 512-555-0144 · maya@email · linkedin.com/in/mayareyes. A line that fails looks like a skyline header that says REMOTE ONLY, or a footer that says “willing to relocate anywhere” with no city. You do not need a street address. You do need a city or metro the payroll and background-check teams can place. If the posting is hybrid in a named office, add the day count you can keep: “Austin, TX · Hybrid, 2 days downtown.” If you can take a quarterly Denver onsite and the ad asks for it, say that in the same line, not in a cover letter nobody opens.

City still matters on a fully remote requisition. “Remote US” almost always means you reside in the United States for tax, equipment shipping, and employment law. A sourcer filters the Greenhouse inbox by state because benefits differ. A Workday location field that says only “Remote” gets sorted under a blank metro. Recruiters also search “CT” or “Central” when the desk is Eastern and they need morning overlap. If Austin never appears in the body, that search misses you. Write the zone in words a human and a parser share: Central Time, CT, or UTC−6 — not “flexible schedule” alone.

What to put on the line — and what to leave off

• Put city or metro, country if you are applying across a border, remote or hybrid, and the zone you actually keep.
• Put “authorized to work in the US” (or the country in the ad) only when it is true and the posting or knockouts ask.
• Leave off street, Social Security number, citizenship, date of birth, and a photo. Those are not location fields.
• Leave off “open to worldwide” on a US-only requisition. The knockout already decided the map.

LinkedIn can stay broader — “Open to remote” as a setting is fine. The attachment you upload to one Workday requisition cannot. The apply form and the PDF are one story. If you are in Raleigh this month and might move to Tampa next year, write the city you will sit in on day one. A future move belongs in a screen, not in a fake second metro on the resume. For how nouns from the ad sit next to this line, use resume keywords after the location facts are true.

If you do not want a full city on a public PDF, a region plus country still parses: “Central Texas, US · Remote, CT.” A blank is worse. International applicants should name the country in the body even when the headline says remote, and confirm passport validity windows before a cross-border start date. A hiring manager who must hire inside the US will not infer Madrid from an email domain. Privacy is a real preference; an empty location field is a failed knockout.

Maya’s skills cloud lists Slack, Zoom, Notion, Asana, and Monday.com. At the ISP she lives in Zendesk, the carrier’s phone queue, and Microsoft Teams. She joins a Zoom standup on Fridays. She has never opened Notion. A Greenhouse questionnaire that asks “years of Slack” will not be kind if she typed three because a template said remote people use Slack. Tools belong on the resume only when she can describe a ticket, a channel, or a doc she actually touched. The same rule applies to Zoom and Notion. Name them if the posting names them and the work is true. Do not import a remote-tool list from a blog.

What reads as remote experience to a human is not the word remote in twelve places. It is a bullet with a place, a volume, and an overlap: tickets closed from Austin, a 9-to-1 Eastern window, a written queue note for the person who starts in London. It is a hybrid pattern she already kept — two office days, three home days — if the new job asks for a similar shape. It is not “collaborated with a distributed team during COVID.” That sentence is everywhere and searchable nowhere. Put the proof under the job where it happened, next to dates a parser can tokenize: “Mar 2022 – Present.”

Proof that belongs — and theater that does not

• Overlap hours you kept, named against the posting’s desk (ET, CT, PT, or a city).
• The ticket or chat system you opened: Zendesk, Intercom, Teams — not a list of apps you have heard of.
• A handoff artifact: written queue, recorded loom, shared runbook. One is enough.
• Skip internet Mbps, a photo of your desk, and “self-starter” as a remote skill.

A Skills heading can repeat Zendesk and Teams so Workday’s skill widget has something to map. The proof still lives in a bullet. Do not create a heading called “Remote tools” and dump every collaboration app in the requisition. That is stuffing, and it is the same failure described when you use resume keywords: overlap only for work you can say out loud. If this posting is a different family than her ISP file — say, a product-led Intercom desk instead of a carrier queue — tailor the resume after the knockouts and the contact line are set. Do not tailor by adding Slack she never used.

Hybrid proof is days, not adjectives. If she sat in the Austin office Tuesdays and Thursdays, write that. If the new job wants two days in Denver and she has never been to Denver, do not borrow “hybrid professional” from the ad. Travel she actually did — a quarterly vendor onsite, a week at HQ — can sit in one bullet. Invented office days die in the first scheduling email. Remote-ready is a work pattern you already ran, not a personality.

Steal the pattern. Do not steal the facts. The first edit is Maya’s contact line. The second is the tool dump. The third is the empty “worked remotely” bullet. In all three, the employer and the dates stay the same. Only the words a knockout and a search can use move into the body.

If a role was on-site and she is now applying remote, do not relabel the old badge “Remote Support Lead.” Write the true title and the true site pattern: “Customer Support Specialist — Regional ISP, Austin, TX (office 2 days / home 3), Mar 2022 – Present.” A fake remote title passes a dumb keyword gate and dies when the recruiter asks where she sat. Honest scope plus shared language survives the job-title field and the on-site-day knockout. Then stop. Three sharp lines beat a new “Remote skills” section.

Set a timer. Have the posting, the knockout list, and your last resume. If you want a layout parsers already map, start in the Enhance CV builder and paste facts as you go. This is filtering, not a new autobiography about working from cafes.

1. Open the requisition and write down the four gates: location, authorization, time zone or overlap, on-site days.
2. If a required gate is a No you cannot change, stop or send one honest sentence. Do not tailor a fiction.
3. Duplicate the master resume. Never overwrite the ISP file. Name the copy FirstLast_RemoteSupport.pdf.
4. Put name, city, remote or hybrid, zone, phone, email, and LinkedIn in the body — not in a header text box.
5. Add “authorized to work in the US” (or the ad’s country) only if it is true and the posting asks.
6. Under the most relevant role, list where you sat, the overlap hours you kept, and the system you opened.
7. Delete Slack, Zoom, and Notion unless you used them. Keep Zendesk, Teams, or Intercom if those are real.
8. Rewrite three bullets as verb + object + number or zone. One bullet must show a handoff or overlap.
9. Build a Skills heading from tools you can defend. No star ratings. No “remote tools” cloud.
10. On paper, answer every knockout. Compare each answer to a sentence on the PDF. Fix mismatches.
11. Export selectable text. Select-all in Preview. City, zone, and email must highlight.
12. Paste resume and ad into the ATS checker. Fix contact and noun gaps, then apply and read the preview.

People invert the order. They polish a summary about being “async-native,” then click through knockouts and discover the job is two days in Denver. Gates first. The summary, if you keep one, should sound like a coordinator repeating you: title, city, zone, one ticket number. Do not spend the hour on a cover letter while the PDF still hides Austin in a sidebar.

The playbook is enough when the master file already has true dates and real tools. If every job is missing a city or the ticket system never appears, you need a longer pass, not a prettier remote template. That longer pass is still this page; you are paying down a generic resume. After submit, open the Workday or Greenhouse preview and confirm the location field and the latest job block match what you intended.

Use this as a desk-side filter while the timer runs. If a choice is not in the table, ask: will Workday store it, will the knockout match it, and can you say it on a screen?

A cover note can carry “why this product” or “I can keep Eastern overlap from Austin.” The resume still has to stand if the letter is never opened — many Greenhouse flows make it optional. Do not paste the same remote letter into every requisition with only the company name swapped. The contact line and the knockouts do more work than a second page of adjectives.

If you need visa sponsorship, say so in the knockout and do not contradict it on the PDF. A line such as “Austin, TX · Remote · requires H-1B sponsorship” is ugly and honest. Hiding the need and clicking “authorized without sponsorship” is how offers die in background check. Some remote US roles will not look at the file after a Yes on sponsorship. That is a gate, not a formatting problem. Tailoring will not create an authorization.

Digital nomads and people living abroad should still name a country and a zone. “Remote” with a Portuguese phone number and no city is a blank location field plus a surprise for payroll. If the requisition requires US residence, Madrid will not become Austin because the headline says remote. You can apply when the ad is truly worldwide and you say Lisbon, Western European Time, and your work-authorization fact in the body. You cannot apply to “Remote (US)” from another country and hope the knockout is optional.

Hybrid fiction is the other common fail. “Remote-first” in a brand paragraph and “3 days in the Seattle office” in the knockout are different jobs. If you cannot be in that office, do not ship a file that says fully remote and a form that says yes to three days. Two files are allowed: one for true remote US desks, one for a local hybrid you can walk to. LinkedIn can mention both. One Workday upload cannot average them. State-licensed remote work — insurance, teaching, nursing advice — needs the licensed states on the file, not only in a portal dropdown.

Frequent movers (military households, rotating contracts) should write the city they will sit in on day one and, if true, “authorized to work in the US; household may move within the US.” Do not list four metros you might land in. Contractors should still put a tax-home city on the line; “1099 / remote” without a place leaves the same empty field. If two very different desks — carrier Zendesk vs product Intercom — need different nouns, that is a posting-family split, not a reason to hide the city.

When to stop. If the checker still flags a missing email or a city that will not highlight, fix that before you add another collaboration app. If the four gates are honest, the contact line parses, and three bullets show hours and a real tool, ship it. Sitting on the file until it feels “remote enough” is how the requisition closes. After you apply, read the preview. Old attachments stick. The recruiter opens the last PDF, not the Slack message where you mentioned Austin.