hoba
ENUA

Candidate

The person applying. The only party in the funnel who sees the whole of their own process and almost none of anyone else's.

Read the whole atlas from here

Decides

  • What is submitted, and in what machine-readable shape
  • Which processes to enter and when to withdraw
  • Which questions to ask, and when to ask them
  • What is recorded: dates, wording, who said it

Cannot see

  • Whether a requisition is funded, frozen or already promised internally
  • The band, the level, and the rubric being scored against
  • How many others are in the pipeline and where they came from
  • Whether a rejection was written by a person or emitted by a rule

Measured on

  • Reach a decision quickly enough to keep options open
  • Avoid spending unpaid hours on processes that were never live
  • Preserve the ability to reapply without having burned the relationship

What it looks like

Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.

What the candidate can and cannot seereconstruction

Visible: every message received, every date, every stated reason, every hour spent.

Invisible: the requisition status, the approved band, the rubric, the queue depth, and whether a human read anything.

Most of the pain of a hiring process is an attempt to infer the second list from the first.

What to notice: This asymmetry is the reason the registry exists. It does not remove it — it makes the boundary between the two lists explicit.

What this position could do

Each of these is something this position actually controls, with the cost stated rather than implied.

  1. Check what the parser extracted before you submitCost: low

    The shape of the file is on the candidate's side of the line; what a reader decides after it is not. A layout a person reads without difficulty can arrive in the record as zero work-history entries, and the score that follows is arithmetic on what was extracted. Running the file through a parser first turns an invisible failure into an edit.

    What it costs: A single-column text export gives up the layout, and every later edit to the document has to be checked again.

    Addressesmech.ats_parser_extraction_failurebar.application_ingestionbar.automated_filter_parser_thresholdobs.rejection_within_minutes_of_application_submission

  2. Ask what the conversation is attached toCost: low

    Whether an approved requisition sits behind the outreach, and whether an internal candidacy is already running, are not in any field the candidate can see. Asking at the first exchange is the only route to either, and the answer arrives before the unpaid hours do.

    What it costs: A logistics question in the first reply comes before any discussion of the work, and the answer cannot be checked against anything.

    Addressesmech.speculative_sourcing_talent_pooling_without_openingmech.pre_selected_internal_candidatemech.stale_or_orphaned_job_requisitionbar.outbound_sourcing_talent_pool_contactobs.unsolicited_recruiter_outreach_followed_by_ghosting

  3. Ask for the band before any assessment is scheduledCost: medium

    The band, the level and the rubric are the second of the candidate's two lists, and the compensation bind runs on the candidate naming a number first. Asking for the band before an assessment is booked puts the mismatch at the screen rather than at week four, when the hours are already spent.

    What it costs: The question can end a process at the screen, and stating an expectation early fixes a number before the level is fixed.

    Addressesmech.unstated_compensation_band_discrepancybar.recruiter_screening_callbar.compensation_levelling_reconciliationpat.compensation_double_bindobs.compensation_band_reduced_or_altered_mid_process

  4. Keep a dated record of every messageCost: low

    Dates, wording and who said it are the one part of the process the candidate holds in full. Kept as they arrive, they separate what a process established from what it did not: a rejection timed minutes after submission, a requisition back on the board, two rounds whose feedback disagrees.

    What it costs: It is unpaid administrative time in the period when time is scarcest, and a complete record of a process that ends in silence is still a record of silence.

    Addressespat.closed_then_reposted_requisition_motifobs.materially_similar_role_reposted_shortly_after_rejectionobs.conflicting_feedback_across_different_interviewersobs.multiple_interview_reschedulings_or_interviewer_no_showmech.mid_process_role_requirement_redefinition

  5. Submit at the stated timebox and name the cutsCost: medium

    The hours a work sample takes come out of the same budget as the search itself, and the minutes it is read for are set on the other side of the gate. Stopping at the stated timebox and writing down what was cut to fit it keeps the exercise inside the scope that was agreed and leaves the trade-offs on the page.

    What it costs: A submission that stops at the timebox is read next to submissions that did not stop, and the reviewer's minutes are not something the candidate sets.

    Addressesloop.take_home_opportunity_cost_saturation_loopmech.take_home_evaluation_fatigue_asymmetrybar.take_home_work_sample_evaluationobs.take_home_assignment_exceeding_reasonable_stated_scope

  6. Set a date when a silent process closesCost: medium

    Silence after submission covers a listing nobody took down, a batch expiry job and a queue that was never reached, and none of the three is visible from outside. Choosing the closing date in advance turns an open question into a finished one and returns the hours to the searches that answered.

    What it costs: An answer that arrives after the chosen date is treated as no answer, and the time already spent is written off rather than waited out.

    Addressesmech.automated_application_expiration_timeoutmech.stale_or_orphaned_job_requisitionmech.recruiter_volume_quota_incentive_distortionbar.inbound_screening_triageobs.complete_silence_after_submission

Entries this position can see