docs(hiring): state the office-cadence position #112

Merged
coilysiren merged 1 commit from docs/hiring-office-cadence into main 2026-08-13 00:17:54 +00:00
Collaborator

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.

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.
docs(hiring): state the office-cadence position
All checks were successful
Test and mirror to GitHub / test (pull_request) Successful in 2m42s
Test and mirror to GitHub / test-e2e (pull_request) Successful in 1m39s
Test and mirror to GitHub / mirror (pull_request) Has been skipped
bc81aef169
The page had nothing between "a comfortable Bay Area hybrid" and the
US-offices hard stop, so it said nothing about how many days onsite is
too many. Five-day onsite is the most common practical reason a role
gets passed on, and with no public position behind it every decline had
to improvise a firmness the page did not support.

Two drafts written this week claimed five days "doesn't work," which
overstates it. The scoring rubric puts five office days in the 1-4
lifestyle-drag band and the pipeline cards note the Bay Area office gate
still passes. So this is stated as a heavy preference rather than a gate,
matching what the cards actually record.

The three-day figure is inferred from a recorded ask on a five-day SF
role, where the question raised was whether three-day hybrid was
possible. Worth confirming in review.

Refs #109

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilysiren/website!112
No description provided.