hoba
EN UA

Employer policy

Finance, leadership and the people function: the layer that authorises headcount, fixes bands and writes the rules the funnel executes. Never meets a candidate.

Read the whole atlas from here

Decides

  • Whether a requisition is funded, and whether it stays funded
  • The band and the levelling grid
  • Whether postings must be published externally regardless of internal candidates
  • What may be disclosed, and what must not be

Cannot see

  • What a freeze looks like from the far end of a five-round process
  • How a compliance posting reads to someone who spent six weeks on it
  • The cumulative candidate hours a policy consumes

Measured on

  • Optionality: an approved requisition that can be paused costs less than one that cannot
  • Consistency and legal defensibility across every hire
  • Cost control, on a cycle measured in quarters rather than in conversations

What it looks like

Composite excerpts, written to be typical of this signal. They are not copies of any particular message, company or person.

Where the decisions actually sit reconstruction

Requisition funded: finance · Band: compensation · Level: levelling committee

External posting required regardless of an internal candidate: policy

Interviews conducted: the team. Rejection sent: the recruiter.

The candidate only ever meets the last two rows.

What to notice: Several observations in this registry are the visible end of a decision taken in a row the candidate never sees.

What this position could do

Each of these is something this actor actually controls, with what it costs them stated rather than implied.

  1. Publish the band on the posting itself Cost: medium

    The band and the levelling grid are set in this layer, and nothing downstream can disclose a number this layer has not released. Publishing it turns the reconciliation at B-009 into arithmetic rather than a conversation that happens for the first time after the panel.

    What it costs: The published number becomes a commitment the band cannot be quietly revised against mid-search, and it is legible to everyone already employed at that level.

    Addresses M-004B-004B-009P-004

  2. Sign the headcount before the role is published Cost: high

    This layer decides whether a requisition is funded, and B-010 is the only gate that stops a process after every person the candidate met has said yes. Moving the finance signature ahead of publication makes the later approval a countersignature, so a published role is one whose headcount already exists.

    What it costs: Budget is committed at publication rather than at the offer, and a requisition funded in advance is harder to pause than one approved at the end.

    Addresses B-010B-013M-007A-003

  3. Expire the listing when its authorisation lapses Cost: medium

    Whether a requisition stays funded is decided here, and that fact reaches no configuration screen on its own. A rule that withdraws the listing when authorisation lapses, and notifies everyone still inside the process, closes the gap between the decision and what the page shows.

    What it costs: A paused search cannot be kept warm: reopening means another trip through the approval chain and a posting that restarts from zero applicants, which is a direct charge on this layer's optionality.

    Addresses M-006M-007B-001P-002L-003A-001A-003A-011

  4. State on the posting that an internal candidacy exists Cost: medium

    The rule that a role is published externally regardless of an internal candidate sits in this layer, and so does what the posting may say. One line stating that an internal candidacy is in process gives an external applicant, at the point of applying, the fact the panel already has.

    What it costs: The external pool for those postings shrinks, which weakens the same posting as evidence of an open search, and an internal candidacy goes in writing before the search has concluded.

    Addresses M-005B-013A-002A-003

  5. Narrow the checks and show the candidate any discrepancy Cost: medium

    Which checks a role requires, and whether a third-party record is put to the candidate before it decides anything, are both settled in this layer. At B-011 a mismatch between a vendor record and an application holds the offer, and only a policy rule makes the candidate's account part of the file before the hold becomes a decision.

    What it costs: Every discrepancy adds a round trip before countersignature, and the single standard check pack has to be split by role instead of running identically on every hire.

    Addresses B-011B-012M-021

Entries this position has a view of