Imposter syndrome doesn’t go away when you get better at the job. It goes away when you stop treating “I don’t know this yet” as evidence you don’t belong.

Why it hits engineers harder

Software has no ceiling. There’s always a framework you haven’t touched, a paper you haven’t read, a senior engineer on Twitter who seems to know everything. The field rewards a public display of expertise — conference talks, blog posts, viral threads — so you’re constantly comparing your rough draft to everyone else’s highlight reel.

Add the fact that most of the work is invisible until it breaks, and you get a job where feeling behind is the default state, not a personal failing.

The specific thoughts, and what’s wrong with them

“A real engineer would know this without looking it up.” No senior engineer writes code without documentation open in another tab. The skill isn’t memorization, it’s knowing what to search for and how fast you can verify an answer.

“I got this job by luck / they’ll figure out I’m a fraud.” Companies interview multiple candidates and pick one. That’s not luck, that’s a selection process working as intended. If you’re worried about being “found out,” ask yourself what exactly they’d find — that you sometimes Google things? Everyone does.

“Everyone else understands the codebase, I’m the only one lost.” They don’t. New hires universally overestimate how well the team around them understands the system. Ask three senior engineers to explain the same subsystem and you’ll get three different, partially wrong answers.

What actually helps

1. Keep a done list, not just a todo list

At the end of each week, write three things you shipped, fixed, or figured out. Nothing else moves the feeling as reliably as a written record, because imposter syndrome runs on selective memory — it remembers every stumble and discounts every win.

2. Say the quiet part in standup

“I don’t understand why this is timing out” is a normal sentence to say out loud. Engineers who say it get help faster and get treated as more competent, not less, because everyone else was thinking the same thing about their own code.

3. Separate confidence from competence

You can be extremely competent and still feel uncertain — that’s just how learning feels from the inside. Waiting to feel confident before you act is waiting for a feeling that arrives after the work, not before it.

4. Compare yourself to yourself, six months ago

Comparing to a staff engineer with ten more years in the field is a rigged comparison. Comparing today’s you to the version that joined six months ago is the only comparison with a useful answer.

5. Mentor someone, even informally

Explaining a concept to someone earlier in their career is the fastest way to discover you know more than you think. It also breaks the illusion that expertise is binary — you’ll see them making the same “obvious” mistakes you thought only you made.

What doesn’t help

Reading more about imposter syndrome past the first article. At some point it becomes a way to avoid the actual work of doing the job and collecting evidence. Positive affirmations without evidence behind them don’t stick either — your brain doesn’t believe claims it has no receipts for.

The actual fix

Imposter syndrome isn’t cured, it’s out-evidenced. Every shipped feature, every bug you root-caused, every question you answered for someone else is a data point your brain eventually has to update on. Keep collecting them and stop waiting to feel ready before you count them.

---