Every Engineering Leader Feels Like a Fraud Sometimes — You Are Not Alone
Imposter syndrome hits engineering leaders differently. The higher you climb, the louder the voice gets. Here is how to work with it instead of against it.

Three months into my first VP of Engineering role, I sat in a bathroom stall during a board meeting break, Googling "what does a VP of Engineering actually do." I'd been leading engineering teams for five years. I'd shipped products used by millions. And in that moment, I was absolutely certain that someone was about to walk into the meeting room and announce that they'd made a terrible mistake hiring me.
Nobody did. The meeting went fine. But that feeling — that nauseating certainty that you're about to be exposed — followed me for years. It still visits sometimes, usually at the worst possible moments.
If you're reading this and thinking "that's me," I want you to know something: you are not broken. You are not uniquely unqualified. You are experiencing something that nearly every engineering leader goes through, usually in silence, usually convinced they're the only one.
Why Engineering Leaders Are Especially Vulnerable
There's something particular about engineering leadership that makes imposter syndrome hit harder than in other domains. Let me name it.
You used to be the expert. As an individual contributor, your value was clear. You wrote the code, you solved the problem, you shipped the feature. The feedback loop was tight and undeniable. Now your value is measured in other people's output, in decisions that take months to validate, in culture that's invisible until it isn't. That ambiguity is fertile ground for self-doubt.
The skills that got you here don't help you here. You probably got promoted because you were an exceptional engineer. But engineering leadership requires a completely different skill set — emotional intelligence, political navigation, strategic thinking, conflict resolution. You're essentially a beginner again. And engineers hate being beginners.
You're surrounded by people who seem to have it figured out. Every other leader in the room appears confident, articulate, certain. What you can't see is that they're performing competence just as hard as you are. The meeting you're Googling through? At least two other people in that room are doing the same thing.
The stakes feel higher. When you were an IC and you made a mistake, you broke some code. As a leader, when you make a mistake, you might break someone's career. That weight is real. It's appropriate to feel it. But feeling the weight of responsibility isn't the same as being inadequate.
The Patterns I've Noticed
After years of mentoring engineering leaders, I've seen imposter syndrome show up in predictable patterns. See if you recognize yourself:
| Pattern | What It Looks Like | What's Really Happening |
|---|---|---|
| Over-preparation | Spending 4 hours prepping for a 30-min meeting | Fear of being caught not knowing something |
| Deflection | "Oh, the team did all the work" | Inability to accept your contribution |
| Comparison spiral | "My peer shipped faster / grew their team bigger" | Measuring yourself against curated versions of others |
| Decision paralysis | Delaying decisions until you're "certain" | Fear that a wrong choice will reveal incompetence |
| Knowledge hoarding | Reading every technical detail to "stay current" | Clinging to IC identity for safety |
| Qualification collecting | Another certification, another course | Hoping credentials will silence the doubt |
If you're nodding at two or more of these — welcome to the club. It's a big club. The membership fee is feeling terrible about yourself for no good reason.
What Helped Me (Slowly, Imperfectly)
I'm not going to pretend I've "cured" my imposter syndrome. That framing is wrong. It's not a disease to cure — it's a voice to develop a relationship with. Here's what helped me shift from being paralyzed by it to being able to function alongside it.
1. I Named It Out Loud
The first time I told a peer "I feel like a fraud today," something broke open. He laughed — not at me, but in recognition — and said "God, me too. I've been faking it in product reviews for six months."
That conversation did more for me than any self-help book. Imposter syndrome thrives in isolation. It tells you that you're the only one who feels this way. The moment you name it out loud to someone safe, you break its power.
Try this: Next time you're with a peer you trust, say some version of "Can I be honest? I have no idea if I'm doing this right." Watch what happens.
2. I Started Keeping a "Proof File"
Every Friday, I spend five minutes writing down three things that went well that week because of something I did. Not my team — me specifically. A conversation I handled well. A decision that turned out right. A person I helped.
This sounds embarrassingly simple. It is. But imposter syndrome has a selective memory — it remembers every mistake and forgets every success. The proof file is a corrective. When the voice gets loud, I open it. The evidence is right there.
3. I Separated "Not Knowing" From "Not Being Qualified"
This was the biggest mindset shift. I used to think that if I didn't know the answer, it meant I was in the wrong role. Now I understand that my job isn't to know everything — it's to figure things out, to connect the right people, to ask the right questions.
The best leaders I've worked with say "I don't know, let me find out" constantly. It's not a weakness. It's how senior leadership actually works.
4. I Got Comfortable With Slower Feedback Loops
As an IC, you know immediately if your code works. As a leader, you might not know if a decision was right for six months. That ambiguity used to eat me alive. Now I've learned to trust the process and evaluate myself on a longer timeline.
A question that helps: "If I zoom out to the last six months, is the team better off than when I started?" If yes, you're doing something right — even if today feels chaotic.
5. I Found My "Me Too" People
I have three people I can text at 11 PM with "I just bombed that presentation and I want to quit." They don't fix it. They don't coach me. They just say "me too, last week I forgot my CTO's name during an all-hands." The normalization is the medicine.
The Paradox Nobody Warns You About
Here's the cruel irony: the people most likely to experience imposter syndrome are the people most likely to be good at their jobs. Research consistently shows that imposter feelings correlate with conscientiousness, high standards, and self-awareness. The people who never doubt themselves? They're often the ones who should.
So if you're feeling like a fraud, it might actually be a signal that you care deeply about doing good work, that you take your responsibility seriously, that you're self-aware enough to see your own gaps. Those aren't weaknesses. Those are the raw materials of great leadership.
What I Tell My Reports
When someone on my team confesses to feeling like an imposter, here's what I say:
"That voice in your head? It's not telling you the truth. It's telling you a story based on fear. Here's what I see: I see someone who [specific thing they did well recently]. I see someone who [another specific thing]. The evidence doesn't match the story you're telling yourself."
Then I share my own bathroom-stall Googling story. Because the most powerful thing a senior leader can do is be visibly imperfect. It gives everyone else permission to be human.
When It's More Than Imposter Syndrome
I want to be responsible here. Sometimes what feels like imposter syndrome is actually a signal that you're in the wrong role or the wrong environment. If you're consistently miserable, if you've lost all interest in the work, if you're dreading every day — that's worth examining honestly.
The difference: imposter syndrome says "I'm not good enough for this role." Genuine misalignment says "this role isn't right for who I am." One is fear talking. The other is wisdom. Learning to tell the difference is a lifelong practice.
A Permission Slip
If you're an engineering leader reading this and the voice is loud today, let me give you what I wish someone had given me earlier:
You are allowed to not have all the answers. That's not incompetence — that's honesty.
You are allowed to be learning on the job. Everyone at your level is. They're just better at hiding it.
You are allowed to ask for help. The best leaders I've ever worked with asked more questions than anyone else in the room.
You are allowed to doubt yourself sometimes. Just don't let the doubt make your decisions for you.
The voice might never fully go away. But it can get quieter. And you can learn to hear it, acknowledge it, and then do the brave thing anyway.
You're not a fraud. You're just a human doing a really hard job. And from where I'm sitting, you're doing it better than you think.
Recommended reading

The Legacy of Leadership: What Remains When You Leave
The thing people remember is not your architecture. It is not your processes. It is how you made them feel. Reflections on what actually endures from engineering leadership.

What 3 A.M. Incidents Taught Me That AWS Certifications Never Did
Twenty production incidents reviewed: why understanding beats fixing, what certifications actually train, and the habits that keep a team calm at 3 a.m.

An Engineering Leader's Sustainable Weekly Rhythm
A realistic weekly rhythm that balances strategy, people, and operational work — without burning out or losing yourself in back-to-back meetings.

Comments
No comments yet. Be the first to share your thoughts.