Tag Every Title With a City on Multi-Hub Boards

Some careers boards look like one company and behave like three offices. Broccoli AI's Ashby list in early November 2026 showed San Francisco, Lehi, Utah, and Bangalore on the same employer, with on-site, hybrid, and remote mixed by title. If your CRM only stores "Broccoli / hiring in SF," you will pitch the wrong people and burn the wrong network. This playbook is the five-step checklist we use on multi-hub boards before outreach.

Primary example: Broccoli Ashby board, accessed November 2026. Broccoli careers page, accessed November 2026.

Step one: list hubs from the marketing page and the board

Careers marketing copy may say the company works from San Francisco, Lehi, and Bangalore. The board may still print Remote or Hybrid on individual lines. Capture both. Marketing hubs are the company's story. Per-role work modes are the submission constraint.

Step two: paste titles with city and mode as a single string

Use a format your partner can audit: "SDR | Lehi | OnSite" or "Staff Software Engineer | San Francisco | OnSite" or "Account Executive Mid-Market | United States | Remote." Do not store titles in one field and cities in a paragraph of notes. The join is the point.

Step three: build separate shortlists by hub

A San Francisco on-site engineering shortlist is not a Lehi support shortlist and not a Bangalore development shortlist. If you only place US on-site roles, hide Bangalore rows instead of arguing with yourself later. If you place remote US sales, keep those rows and drop SF-only on-site leadership you cannot fill.

Step four: watch for internal talent seats per hub

Talent Operations Associate in San Francisco is a process signal for that hub. It does not automatically close agency work in Lehi. Log it, then ask about overflow by function and location rather than assuming a global freeze.

Step five: re-check the board before second touch

Multi-hub companies edit boards unevenly. A Lehi support seat can close while a Bangalore engineering seat opens. Re-open Ashby the morning of any follow-up. Update the city-tagged string. Do not reuse last week's hub assumptions.

One employer with three hubs is three research problems that share a brand name.

In our Broccoli walkthrough, the useful correction was stopping a draft that said "they're hiring engineers in San Francisco" when the board also showed Bangalore software development titles and Lehi hybrid engineering support. Saying SF-only was not false for some lines. It was incomplete enough to look sloppy to anyone who opened Ashby.

Constraints

This checklist does not create agency authority. A tagged title is still not a job order. It fails when the board prints only "United States" with no city and no remote flag you trust. In that case, ask the employer for work-mode detail before you source. It also fails if you scrape aggregator cards that strip location. Prefer the employer ATS URL.

Use Broccoli as practice, not as a placement claim. We did not submit candidates on these roles. The win is a CRM note that survives a partner asking "which city?" without a pause.

Remote United States lines are a fourth pattern, not a free pass to ignore hubs. An Account Executive marked Remote still needs time-zone and travel expectations confirmed. Do not assume remote means work-from-anywhere worldwide. Copy the location text exactly as Ashby prints it.

When training a junior researcher, require three hub-tagged titles before any congratulations email on funding or growth. If they cannot produce three strings, they are not done. This rule prevents the single-HQ smear that wastes senior time on cleanup.

Multi-hub boards also break compensation folklore. A Bangalore software development seat and a San Francisco staff engineer seat are not one band you overheard at a meetup. Keep pay conversations tied to the tagged row or do not have them yet.

End every multi-hub research block with a one-line coverage decision: which hubs you will work this week, and which you will ignore. Ambiguous coverage is how SF resumes get sent at Lehi support roles. Write the decision before the email draft, not after the bounce.

Partner handoff language

When you pass a multi-hub board to a partner, lead with the tagged strings, not the company story. Say you reviewed Ashby on a stated date and that coverage this week is San Francisco engineering and remote United States sales, with Lehi and Bangalore parked. Partners can disagree with the coverage choice. They should not have to reverse-engineer which city you meant.

If a hiring manager says “we hire everywhere,” still refuse to store a blank city. Ask which titles are open where this month. Store the answer as new tagged strings. Everywhere is a brand claim. Tagged titles are research.

Do not let funding headlines rewrite your hub list. Growth capital may fund more seats later. Until Ashby shows the title and city, keep the later seats out of the active shortlist. That is the same discipline as treating press traction as non-orders elsewhere on the desk.