NAMED_MECHANISMS
The Science of Imposter Phenomenon in Software Engineering: Why It's Not Just Self-Doubt
3 named mechanisms — 'Everyone here is smarter than me and it's only a matter of time before they notice.' That thought — or something close to it — is so common among sof
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.
How it sounds in your headThe inner script: 'If I push this code now, Sarah will read it and immediately know I have no idea what I'm doing. I'll add three more comments and rewrite the function first.' The research reads this as the mechanism in action: the PR delay isn't about code quality — it's anticipatory threat management, with real productivity costs.
Engineering competence miscalibration is the systematic gap between an engineer's actual skill level and their internal estimate of it, most commonly running in the direction of underestimation among high performers. Kruger and Dunning (1999) identified that the metacognitive skills needed to accurately assess one's own performance are largely the same skills that constitute high competence — meaning the more capable the engineer, the better they understand the scope of what they don't yet know.
How it sounds in your headThe inner script: 'I've been coding for six years and I still don't know Rust. Everyone at this conference seems to know everything.' The research reads the comparison differently: the engineers who feel most out of depth in a room of experts are often those with enough expertise to accurately perceive how much more there is to learn.
Code review anxiety is a measurable, occupation-specific form of evaluative fear triggered by submitting code for peer review — distinct from general social anxiety. Lee et al. (2024) established it as a construct that predicts concrete behavioral outcomes: engineers experiencing it delay pull requests, reduce inline commenting, and avoid requesting reviews from certain peers. It is significantly correlated with imposter phenomenon and is partially mitigable through team norms that explicitly frame code review as a learning exchange rather than a competence verdict.
How it sounds in your headThe inner script: 'I know this works but I can't submit it until I've checked it another twelve times — what if they see I used a for-loop when everyone else would have used a generator?' The research reads it as code review anxiety operating on imposter fuel: the fear isn't about the for-loop, it's that the for-loop will be the tell.