Read the JD Line When Ashby's Workplace Tag Says OnSite

Ashby job boards carry a structured workplace field: OnSite, Hybrid, or Remote. Many recruiters filter on it and stop. On November 5, 2026, two boards we pulled showed the field and the job description disagreeing. Joyful Health's Forward Deployed Engineer row is tagged OnSite, and its description says "Hybrid (in office 3 days a week)." Pi Security's Field Marketing Manager row is tagged OnSite, and its description says "Hybrid or West Coast Remote." If you filter on the tag, you either drop good candidates or pitch the wrong arrangement.

Sources: Joyful Health Forward Deployed Engineer on Ashby and Pi Security Field Marketing Manager on Ashby, both accessed November 5, 2026.

The two mismatches

Joyful Health announced a $22M Series A led by CRV inside the job description and says it is "doubling our engineering team." The FDE row lists New York City, full-time, $150,000 to $275,000 plus equity, and three office days a week. The structured field says OnSite. A candidate who will do three days in Manhattan but not five is a fit for the text. They fail the tag.

Pi Security's board is mostly in-person. Its Platform Software Engineer description says "Onsite, 5 days a week," and most San Francisco rows say the same. The Field Marketing Manager row is the exception. The text says the role "is remote and must be based in the U.S. Pacific time zone, with a strong preference for a California metro area." The tag still says OnSite, San Francisco.

The workplace tag is a form field someone filled in once. The description is what the hiring manager wrote. When they disagree, quote the description and ask.

Why the tag drifts

Ashby's workplace field is set per posting. Descriptions are often pasted from a template or a hiring manager's draft. When a company is mostly onsite, the field defaults that way and exceptions get written into the text instead. Neither company did anything wrong. The field just carries less information than the paragraph under it.

The playbook

1. Pull the structured fields: title, location, workplace tag, publish date.
2. Search the description for "hybrid," "remote," "days a week," "time zone," and "onsite."
3. If the text and tag disagree, store both and mark the row "mode conflict."
4. Write the arrangement in the description's own words in your CRM.
5. Confirm the arrangement with the hiring manager before you submit anyone.

A quick audit on the rest of each board

We ran the same check on the other rows we pulled. Joyful Health has five rows. Four are New York City tagged OnSite. The fifth, Revenue Recovery Specialist, is tagged Remote with location "US Based." The FDE row was the only one where we found hybrid language under an OnSite tag.

Pi Security has eleven rows across San Francisco and Tel Aviv, all tagged OnSite. Most San Francisco descriptions repeat five days in the office. The Field Marketing Manager row is the clear exception. One frontend engineering row also contains the word "hybrid" in its text. Read that row in full before you decide what it means. A single word can sit in a sentence about something else.

That is the point of the audit. You are not trying to prove every tag wrong. You are finding the one or two rows where the arrangement differs from the board's default, because those rows have a different candidate pool.

How to word the confirmation

Do not tell a client their posting is wrong. Ask a short question that shows you read both. For example: "Your FDE posting lists OnSite in the header and three office days in the description. Should I screen for three days in New York?" That takes ten seconds to answer and saves a rejected shortlist.

For Pi's marketing role, the question is about geography, not office days: "The description says West Coast remote with a California preference. Should I include Pacific-time candidates outside California?"

What this does not fix

The description can be stale too. A role written as hybrid in July may be onsite by November. Neither field gives you a date for the arrangement itself. The description is the better first read, not a final answer. If a candidate's decision depends on office days, get it from the hiring manager in writing.

This also does not mean every OnSite tag is wrong. On Pi's board, most rows say five days onsite in both places. The playbook is for catching exceptions, not for assuming flexibility.

When the tag is the better signal

Sometimes the description is the stale part. If a posting was published months ago and the tag was edited recently, the tag may reflect a newer decision. Ashby's public board does not show when the tag was last changed. That is one more reason to treat a conflict as a question, not as permission to pick whichever answer suits your candidate.

Fields to keep

Store the tag, the description phrase, the access date, and the confirmation status. When you re-pull the board, compare all four. A row whose description changes from "Hybrid" to "Onsite, 5 days" is a changed job, even with the same title and URL.