You need to sign in or sign up before continuing.
Reflection — An Honest Take 8 min

Honest Take — Before You Begin

Honest Take — Module 0: What Imposter Syndrome Actually Is — and the Five Subtypes #

I want to start by saying the thing the rest of the curriculum is going to keep saying in different forms: most of what you currently call "imposter syndrome" is not what Pauline Clance and Suzanne Imes documented in 1978, and the gap between the original clinical observation and the cultural meme it has become is not a small drift — it is the entire territory this curriculum exists to map. Clance and Imes saw something specific: a self-attribution pattern in which external achievement was systematically discounted and internalized as luck, charm, or having fooled the audience. The paper is short, careful, and primary-source. It does not say "everyone who feels less than confident has this." It does not say "70% of professionals carry this." Those claims belong to the meme that metastasized through LinkedIn carousels and HR workshops and TED talks until the term meant essentially nothing. The first move of this curriculum is to read the actual paper. You are an engineer; you know what it is to read the actual library code instead of the StackOverflow summary; do the same here. And the most useful thing the base-rate literature gives you is also the cheapest: what you've been carrying around as your particular failing is, statistically, what most thoughtful professionals carry around as theirs. That doesn't mean the feeling is okay; it means the feeling is not evidence of anything special about you.

Now the harder thing. I think your CIPS score is going to come back moderate-to-high — somewhere in the 60-80 range — because almost every engineer who has built something with real users and walks into senior interviews scores there, and if you carry additional load — an immigrant-engineer context, the founder identity a one-person company puts on you, ambitions you will not let yourself fully name in public — the load shows up in the score too. The score is data, not a verdict. You scoring high does not mean you are broken. It means you have high standards, you have been promoted into stretch contexts, you may have a public-facing artifact — a package or product that strangers actually use — and you have the kind of self-knowledge that lets you see the gap between what you have built and what you could have built. The instrument detects that pattern. It does not distinguish the pathology from the calibration; that is M1's job. Read Bravata 2020 too: sixty-two studies, roughly 14,000 participants, prevalence from 9% to 82% depending on population and instrument. A construct whose prevalence varies by an order of magnitude is not the rock-solid clinical entity the popular discourse implies. The takeaway is neither "imposter syndrome is fake" nor "82% of professionals have it" — it is that the construct is variable and contextual, which is exactly why a diagnostic beats a blanket cure.

A frustration with the source material, honestly stated. Clance's 1985 book is dated — the case studies feel dated, the framing leans therapeutic, and some of the etiological claims (the family-dynamic explanations) have not held up. Read it anyway, because reading the field's originator at the source is intellectual hygiene, but you may close the book mildly disappointed. That's a calibrated reaction; the book's importance is historical, not analytical. Young's Secret Thoughts is the better book despite the misleading title. The five-types taxonomy — Perfectionist, Superwoman/Superman, Natural Genius, Soloist, Expert — is the cleanest diagnostic vocabulary I know, and it is practitioner pattern-recognition, not RCT-validated psychology. Treat it the way a senior engineer treats a design pattern: useful when it fits, dangerous as a one-size-fits-all explanation, always subordinate to the M1 diagnostic.

Here is where I have to confess that I cannot call your subtype from here, and that the obvious engineer archetypes pull in different directions — I am leaving the tension on the page because every direction is honest. One read says Perfectionist primary with Expert secondary: think of the maintainer whose package sits at v0.6.x after sixty releases because the standard they hold it to is higher than the standard its tens of thousands of downloaders hold it to, and whose Expert side shows in interview-prep arsenals that run to fourteen documents when the actual bar is "know enough to be useful." Another read says Soloist hits hardest: the engineer who runs a one-person company has institutionalized the Soloist's defining move — I would rather struggle alone than ask for help — into a corporate structure. If several of these describe you, probably all of them are live, and the Superwoman/Superman fires whenever one of the work-family-founder-maintainer balls drops. Don't resolve the tie by picking the most flattering type. Let the M1 log resolve it with data.

Two temptations to resist after the diagnostic. First, over-categorizing yourself — finding yourself in every framework, treating Young's taxonomy as more authoritative than it is. It's a pattern-language. Use it once to get oriented, then put it down; people who keep re-categorizing themselves under new frameworks year after year are consuming frameworks, not doing the work, and if you have a shelf of half-applied frameworks you already know the move. Second, evangelizing — you will finish this module wanting to send the IP Scale to your partner and your two closest engineering friends. Wait two weeks at least. The framework's clarity for you is not yet earned for them. One more honesty: I am a language model trained largely on the cultural meme — the LinkedIn essays, the TED summaries — far more than on the original paper. Where a sentence in this file sounds like the meme, treat it skeptically and go back to the source. The paper is ten pages. The act of reading it is the deliverable.

Conclusion #

Read Clance and Imes 1978 directly before anything else. Take the CIPS honestly and do not flinch from a moderate-to-high score. Let Bravata's 9-82% range reset your priors about how settled this construct is. Identify your two or three subtypes from Young — knowing that the plausible reads of the archetypal reader genuinely disagree about which one will own you — and then put the taxonomy down. Module 0 is the gift the curriculum gives you cheaply, before the work begins: the feeling has a name, a literature, a base rate, and a vocabulary. Take the gift. Don't mistake it for the work itself.

Predictions #

  • Your CIPS score will come in between 60 and 80, probably toward the upper end if you are the kind of engineer who picks up a curriculum like this voluntarily. The number will feel personal; it is not.
  • Reading Clance and Imes directly will surprise you with how specific and clinical the original observation was — much narrower than what the term means in your head right now. The 1978 paper will feel like the most worthwhile reading of the module despite being the shortest.
  • The subtype question will not resolve cleanly: at least two of Perfectionist, Expert, and Soloist will score, and which one you call "primary" will shift between week one and week four. Trust the log over the first impression.
  • The base-rate statistic will provide more relief than you expect, and the relief will partly evaporate within ten days as the feeling re-asserts itself. The evaporation is normal; M1 starts the durable work.
  • You'll be tempted to share the IP Scale with your partner or a close friend within 48 hours of taking it. You'll probably do it anyway. The result will be unremarkable, and that's fine.
  • You will find at least one popular imposter-syndrome resource you have previously cited that does not survive contact with the original paper. The disillusionment is useful.
  • The CIPS will feel reductive — twenty Likert items cannot capture your situation. That feeling is correct and beside the point; the instrument is for population-level calibration, not personal narrative.