- What reaches them
- Two rejections inside one market cycle: one saying the experience sits above the band scoped for the role, one saying the depth is not yet at the next level's scope.
- What it means from there
- Together the two messages describe a person who is above one rung and below the next, with nothing open in between.
- What happens next
- Applies at both levels at once and shifts what the CV emphasises depending on which rung the posting names.
Seniority Double Bind
The same candidate is rejected as overqualified for junior and mid-level roles and as underqualified, or not specialised enough, for staff and leadership roles.
Pattern pat.seniority_double_bind Evidence: supported
⏳ What made this ordinary
A fixed number of seats (2024–2026) — The conditions that made hiring expensive were reversed; the number of positions was not. The contraction now runs through the hiring channel rather than the separation channel, which is why it is competition for a fixed and shrinking number of seats rather than a shortage of qualified people.
Trigger rule
The candidate is rejected as overqualified at level N and as short on depth at level N+1 within the same market cycle.
What it looks like
Composite excerpts, written to be typical rather than copied. No particular message, company or person is quoted here.
12 Feb — Senior Backend Engineer (level 4). Your experience sits above the band scoped for this role and we were concerned it would not hold your interest.
26 Mar — Staff Engineer (level 5). The panel felt the depth of platform ownership was not yet at staff scope; we would look for a broader track record of org-wide impact.
Both roles: same city, same domain, same six-week window.
What to notice: Neither message is unreasonable on its own. Put next to each other they describe a candidate who is above one level and below the next, with nothing in between open.
Established: two rejections, two stated grounds, two adjacent levels, one market cycle.
Not established: that either judgement was wrong, that the two employers coordinated, or that the candidate is unhireable. The motif is a property of the level grid, not of the person moving through it.
What to notice: The pattern is worth naming precisely because each half is defensible. The trap is structural, which is also why no single conversation can argue it away.
What this pattern establishes
- The candidate falls into a gap between evaluation tiers, where the compensation and experience expected match neither tier.
What this does NOT establish
- Does not establish that the candidate lacks market value.
- Does not establish malice or coordinated collusion between employers.
Observations this pattern requires
- obs.feedback_stating_candidate_is_overqualified_for_the_grade Feedback stating candidate is overqualified for the grade Candidate is rejected on the grounds that their experience, seniority, or previous scope sits above the band the role was opened at.
- obs.generic_closer_alignment_rejection_template Generic "closer alignment" rejection template A standard automated email saying that the team has decided to proceed with candidates whose profiles match the requirements of the role more closely.
Compatible mechanisms in this pattern
- mech.experience_age_grading_mismatch Experience-Age Grading Mismatch none A candidate with 10+ years applies for a role graded at mid or senior, and the screening note records forecasts about boredom, short tenure and salary expectation.
- mech.genuine_technical_skill_shortfall Genuine Technical Skill Shortfall candidate The candidate’s verified technical execution or domain depth does not meet the established baseline for the role level.
- mech.unstated_compensation_band_discrepancy Unstated Compensation Band Discrepancy intermediary Candidate market rate exceeds budgeted compensation for the requisition, but salary band was never published or clarified early.
Interventions that mitigate this pattern
- int.standardized_late_stage_rejection_feedback_taxonomy Standardized Late-Stage Rejection Feedback Taxonomy Provide candidates reaching technical or panel stages with structured, rubric-based feedback categories rather than generic templates.
- int.upfront_compensation_band_disclosure Upfront Compensation Band Disclosure Publish verified salary and equity bands directly in job descriptions or disclose them prior to scheduling technical interview rounds.
Reached without being linked
The relations above are one step. This is what the entry reaches only by walking through them — the shape of it, since the list runs long in a registry this cross-referenced.
- 24
- entity.artifact6Barrier14Mechanism4
From each side
The same entry from inside each position that meets it: what reaches them, what it means from there, and what happens next given what they control.
- What reaches them
- A profile whose years and previous scope sit above the band approved for the requisition being screened.
- What it means from there
- An expectation above the band reads as an offer that will not close, and the level of the requisition is fixed before the screen begins.
- What happens next
- Closes the application against this requisition and writes the rejection in terms of fit with the level it was opened at.
- What reaches them
- A candidate in a staff-level round, assessed against the scope the panel has agreed for that level: ownership across an organisation rather than a team.
- What it means from there
- A track record that has not yet run at that scope is a risk that lands on the person who makes the hire.
- What happens next
- Records a not-at-this-level decision and leaves the requisition open: a bad hire carries a name and a search still running does not.
- What reaches them
- A levelling grid in which every level has a band and the bands are contiguous, and requisitions that are each opened at a single level.
- What it means from there
- A candidate above one band and below the next is a mismatch between a person and a particular requisition, not a gap in the grid; the grid is what makes offers consistent across every hire.
- What happens next
- Holds the grid steady through the cycle and approves requisitions at one level, because the level is the unit finance funds.
ATS vendorNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
ClientNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
Public policy and industry standardsNot visible from here
From this position the entry is not visible. That is not a gap in the atlas — it is the finding: the decision is made where nobody in this position can see it.
