RESEARCH_TIMELINE
The Science of Imposter Phenomenon in Software Engineering: Why It's Not Just Self-Doubt
'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 software engineers that a 2024 study presented at ICSE found measurable imposter phenomenon in a majority of surveyed practitioners. It isn't a quirk of personality. Psychological research dating to 1978 has documented it as a recognizable pattern driven by competence-assessment errors, code-review anxiety, and team environments that either magnify or dampen it. The old script — 'I just need more confidence' — misses the structural half of the story.
How the science changed · 1978–2024
- 1978
Pauline Clance and Suzanne Imes publish the first formal description of 'impostor phenomenon' — a pattern of high-achieving individuals who, despite objective evidence of success, believe they are frauds and fear being exposed. Their clinical observations focused on high-achieving women but noted the pattern appeared across gender. ↗
- 1999
Kruger and Dunning publish their landmark study showing that low performers systematically overestimate their competence (the Dunning-Kruger effect), while high performers often underestimate theirs — a contrasting asymmetry that helps explain why the most skilled engineers are frequently the most likely to feel like impostors. ↗
- 2016
Google publishes Project Aristotle findings from a study of 180 teams: psychological safety — the belief that one can take interpersonal risks without punishment — was the single strongest predictor of team effectiveness, outweighing talent composition, seniority mix, and co-location. Teams where engineers feared judgment performed worse across every metric. ↗
- 2017
Santos et al. publish a meta-analysis of imposter phenomenon across populations, finding prevalence in approximately 70% of the general population at some point in their lives and noting that the experience was particularly pronounced in high-stakes evaluation contexts — directly applicable to code review, on-call incidents, and senior-engineer promotions. ↗
- 2021
Byskov and colleagues examine imposter phenomenon specifically in STEM and technical fields, finding that the combination of objective performance feedback (test failures, bug counts, benchmark scores) and social comparison within high-performing peer groups creates a compounding effect that elevates imposter feelings beyond what individual self-doubt alone would produce. ↗
- 2024
Guenes et al. present at ICSE-SEIS 2024 the first large-scale empirical study of imposter phenomenon in software engineering: measurable imposter scores in a majority of surveyed engineers, with seniority level, team size, and hiring source (self-taught vs. CS degree) all predicting variance — reframing imposter phenomenon from a personal quirk to a structurally explainable occupational pattern. ↗
- 2024
Lee et al. publish in Empirical Software Engineering a quantitative study of code review anxiety: they find it is measurable, distinct from general social anxiety, significantly associated with imposter feelings, and partially mitigable through structured review practices and explicit norms around the purpose of code review. ↗