The Science of Imposter Phenomenon in Software Engineering: Why It's Not Just Self-Doubt

TEST_YOURSELF · How well do you know this science?

1. 01 Pauline Clance and Suzanne Imes coined 'impostor phenomenon' in 1978 to describe what?

   A clinical disorder affecting only people with low actual abilityHigh achievers who believe they are frauds despite evidence of success and fear being exposedA deliberate self-handicapping strategy used to manage expectationsOverconfidence in one's own skills relative to peers

   Clance and Imes described a pattern in high-achieving individuals who, despite objective evidence of competence, internally attribute their success to luck or deception rather than ability — and persistently fear being exposed as frauds. source ↗

2. 02 What does the Dunning-Kruger effect tell us about the relationship between skill level and self-assessment of competence?

   High-skill individuals consistently and accurately assess their own abilitiesSkill level is unrelated to self-assessed competenceLow-skill individuals overestimate their competence while high-skill individuals often underestimate theirsOnly individuals in their first year on the job systematically misjudge their competence

   Kruger and Dunning found a systematic asymmetry: low performers overestimate their competence (they lack the metacognitive skills to recognize their own gaps), while high performers underestimate theirs — making imposter-like self-doubt more common, not less, at higher skill levels. source ↗

3. 03 What did Google's Project Aristotle research identify as the single strongest predictor of engineering team effectiveness?

   Average seniority level of team membersPsychological safety — the belief one can take interpersonal risks without punishmentCo-location in a single physical officeNumber of years the team had been working together

   Project Aristotle analyzed 180 Google teams and found psychological safety — whether team members felt safe to take risks and be vulnerable in front of each other — outperformed every other variable, including talent level, as a predictor of team output and effectiveness. source ↗

4. 04 What did Lee et al.'s 2024 study find about code review anxiety in software engineers?

   It is indistinguishable from general social anxiety and has no specific engineering contextIt only affects engineers in their first year who have not yet established credibilityIt is a measurable, distinct construct associated with avoidance behaviors and significantly correlated with imposter phenomenonIt disappears once engineers accumulate positive review feedback

   Lee et al. found code review anxiety is distinct from general social anxiety, measurable through survey instruments, predicts avoidance behaviors like delaying code submission, and correlates significantly with imposter phenomenon scores — making it a specific occupational stressor, not just general nervousness. source ↗

5. 05 What did the ICSE-SEIS 2024 study by Guenes et al. establish about imposter phenomenon in software engineering?

   It is rare and mainly affects developers who switched careers from unrelated fieldsIt only becomes a problem when engineers are assigned to tasks beyond their current skill levelIt is prevalent across seniority levels, team sizes, and educational backgrounds — an occupational pattern rather than an individual quirkIt is most prevalent in engineers who work remotely without daily standups

   Guenes et al.'s 2024 study at ICSE-SEIS was the first large-scale empirical measurement of imposter phenomenon in software engineers specifically, finding it present across seniority, team size, and educational background — structurally rooting what had often been treated as individual self-doubt. source ↗