REALITYWIPE

CROSS_SECTION_ANALYSIS

The Seniority Oracle

SURFACE BEHAVIOR

  • In every meeting you run a live ranking of the engineers present, and you always finish last.
  • You spot the flaw in the staff engineer's design and file it under “I'm probably missing context”.
  • You mistake fluency for depth — whoever talks fastest about Kubernetes must know more than you.

THE HIDDEN RULE

“The org chart is a correctness proof — whoever outranks me is right, and my read of the room is my rank.” Google's Project Aristotle tested that theory on 180 of its own teams: composition and seniority predicted almost nothing; whether people felt safe to challenge and disagree predicted nearly everything. The hierarchy in your head is stricter than the one in the company.

INSTALL MECHANISM

Engineering Imposter Review Dread

Engineering imposter review dread is the anticipatory fear that a code review will expose one's perceived lack of competence to colleagues — not just that the code might have bugs, but that the review will confirm the reviewer's secret fear of being a fraud. Lee et al. (2024) found this is a measurable, distinct experience that leads to avoidance behaviors including delaying PRs, under-commenting code, and selectively avoiding certain reviewers.

REPLACEMENT PROTOCOL

  • Titles are routing metadata, not correctness proofs. The design is wrong or it isn't.
  • I'm not the weakest in the room — I'm the one grading myself on other people's specialties.
  • Questioning the staff engineer is the job description. Silence is the failure mode.

STATUS: READY_TO_INSTALL

I'm the weakest engineer in every meeting

Start this exact wipe in the app →

RELATED CONTENT

SCRIPTS

SCIENCE

RESEARCHERS

MECHANISMS

QUIZZES