Imposter syndrome is the feeling that you are a fraud who is about to be found out, even when your work keeps showing that you can do the job.
Developers can feel it at any level, beginners and seniors alike, and knowing how it works makes it much easier to keep going while you have it.
What imposter syndrome is
Imposter syndrome is a gap between your skill and your belief in it. The skill is real: your code works and your features ship. The confidence isn't there to match, so you explain your own success away.
The idea was first described in 1978 by the psychologists Pauline Clance and Suzanne Imes, who called it the 'impostor phenomenon'. They noticed that many high-achieving women they worked with believed they weren't really capable, whatever their results said. You will see it spelt both 'impostor' and 'imposter'; they mean the same thing.
It is a pattern of thinking, not a medical diagnosis: a habit of reading the evidence about yourself unfairly. That matters, because a habit can be noticed and changed.
The thoughts behind it
Three thoughts come up again and again. Each one sounds reasonable in the moment, and each one bends the evidence.
'I just got lucky'
Your feature works and you put it down to luck or an easy ticket. That way, success never counts as proof of skill. If luck explains every win, no amount of winning will ever convince you. Yet the same person usually treats a bug as entirely their own fault, so the wins go to chance and the losses go to them.
'I'm not good enough'
This one measures you against an imagined standard: the developer who knows every framework, never searches for syntax and never ships a bug. Nobody works like that. Software is too big for anyone to know all of it, so 'good enough' becomes a target that moves every time you get close.
'Other developers are smarter'
You see other people's finished work, such as a clean pull request or a confident conference talk. You don't see the hours they spent stuck or the questions they asked first. Comparing your messy process with their finished result is a test you are bound to fail.
Why developers feel it so often
Wondering how this was made? How we make these