docs(hiring): state the office-cadence position #112
No reviewers
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
burndown-2026-06
burndown-2026-08
icebox
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilysiren/website!112
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/hiring-office-cadence"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Adds an Office cadence entry to Practical fit. Refs #109.
Why
The page had nothing between "a comfortable Bay Area hybrid" and the US-offices hard stop, so it never said how many days onsite is too many. That is the single most common practical reason a role gets passed on, and with no public position behind it, a decline has to improvise.
This surfaced concretely. Two decline drafts written this week claimed five days onsite "doesn't work from the East Bay." That overstates it, and the internal record says so plainly: the scoring rubric puts five office days in the 1-4 lifestyle-drag band, and the Triumph card reads "a serious lifestyle cost, though the Bay Area office gate passes." So the drafts asserted a gate where only a heavy preference exists.
What it says
Up to about three days a week in a Bay Area office works well. Five days is not an automatic no, but it is more than is wanted from the East Bay and weighs heavily enough to usually end in a pass. Recruiters are asked to state the expected cadence early.
Stated as a preference rather than a gate, deliberately, because that is what the cards actually record.
One thing to confirm in review
The three-day figure is inferred, not previously stated. It comes from a recorded ask on a five-day SF role, where the question raised was whether a three-day hybrid was possible. That is reasonable evidence but it is not the same as an explicit position, so change the number if it is wrong. Everything else here is a restatement of existing internal rules.
Verification
Content-only change inside existing markup, no new Nunjucks constructs, so the Cypress smoke check is skippable per AGENTS.md. Voice-linted: no em-dashes, en-dashes, semicolons, or italics in the added lines.