Imposter Syndrome Is Telling You Something Useful

Imposter syndrome isn’t a bug. It’s a signal that you’re surrounded by people who are better than you at something, and that’s exactly where you should be.

The standard advice is to “push through it” or remind yourself you deserve to be here. That’s fine as far as it goes. But it treats the feeling as noise to suppress rather than data worth reading. I’ve watched engineers spend years either fighting this feeling or running from it, when the more useful move is to listen to what it’s actually telling you.

I felt it hardest in 2012 when I moved from Facebook’s London office to California. I’d spent years building the EU SRE presence from scratch, starting as the first technical hire outside the US in 2008. London was my domain. I knew the systems, knew the people, knew where I stood. Then the London SRE team was shut down. All cache infrastructure responsibility shifted to California.

Two things hit at once.

The technical gap came first. In London, the team had taken ownership of the Memcache infrastructure. Well-understood system, key-value store, clear operational patterns. Now I was supporting a team who were additionally responsible for infrastructure for TAO, Facebook’s graph-aware caching layer. TAO cached the entire social graph in RAM. Fundamentally different data model, different failure modes, different scaling properties. The engineers who’d designed it had years of context I didn’t have. I was asking questions they’d answered three years ago. Building telemetry hooks for a system I hadn’t been involved in conceiving. They were so far ahead of me it was absurd.

The leadership gap was actually worse, and slower to close. In London, timezone meant I’d missed the afternoon management meetings in California where decisions got made and organizational context got shared. Now I was suddenly in those rooms, sitting next to managers and senior ICs who’d had years of leadership development, mentorship, and institutional knowledge that had never been available to me from 5,000 miles away. The gap wasn’t about ability. It was about exposure. They’d had hundreds of reps I simply hadn’t.

Here’s what I didn’t understand at the time: those two gaps were the best thing that could have happened to my career.

The pattern behind the feeling

The technical gap closed in about six months. Systems work has fast feedback loops. You debug an incident, you learn a subsystem. You review a design doc, you absorb a tradeoff. Six months of intensity and I was a lot closer to the mental model I needed.

The leadership gap took closer to a year. Leadership development has slower feedback loops. You run a meeting, you get indirect signals about what worked. You make a staffing call, you don’t see results for a quarter. The learning opportunities come less frequently, and each one teaches you less per rep than a production incident at 2 AM.

Both gaps closed because I stayed in the room where I was the least experienced person. That’s the pattern I’ve seen over and over since, both in my own career and now coaching engineers through theirs.

The engineers who grew fastest stayed uncomfortable longest. They took the role where they didn’t know the codebase. They joined the team where the bar felt impossibly high. They sat in meetings where they understood 60% of the conversation and took notes on the other 40%.

The engineers who stalled found comfortable pockets. They became the expert on one system and stayed there. They joined a team where they were immediately the strongest engineer. The imposter syndrome went away. So did the growth.

Whether you’re at a startup or a public company, the dynamic is the same. Discomfort is the leading indicator. Comfort is the trailing one.

When the feeling fades, pay attention

There’s a specific inflection point worth watching for. I think it’s the moment you realize you’re teaching more than you’re learning. You’re the one answering questions in code review. You’re the one people pull into design discussions for your opinion, not your questions. The pressure lifts. The imposter feeling fades.

Many people treat that as relief. Finally, I belong.

I’d treat it as a warning.

It means you’ve absorbed what this particular room has to offer. The people around you have taught you what they know, at least on the axes that matter to your growth. That’s not a reason to leave tomorrow. Teaching is valuable. Mentoring junior engineers, sharing institutional knowledge, building team capability. You can and should do that.

But if you’re the most experienced person in every room you’re in, something has gone wrong. You’ve stopped putting yourself in positions where you feel outmatched. You’ve optimized for confidence instead of growth.

The engineers I coach who’ve been “comfortable” for two or three years are almost always the ones who feel stuck. They can’t articulate why. The work is fine. The team is fine. Everything is fine. But they haven’t been challenged in so long that their skills have quietly plateaued, and the market has moved on without them.

Now, there’s a line here worth drawing carefully. Imposter syndrome and genuine unpreparedness feel similar but they’re different problems with different solutions.

Imposter syndrome is feeling inadequate despite evidence you belong. You were hired. You’ve shipped things. You’ve solved hard problems before. The feeling persists anyway, because the people around you seem to operate at a level you can’t match yet.

Genuine unpreparedness is a skills gap you can name. You don’t know Kubernetes. You’ve never designed a distributed system. You can’t write a design doc that passes review. If you can list exactly what you don’t know, that’s not imposter syndrome. That’s a learning plan. Write it down, close the gaps, check them off.

The distinction matters because the response is different. Imposter syndrome needs reframing and time in the room. A skills gap needs deliberate study and practice. Many engineers conflate the two and end up either over-studying things they already know well enough (trying to cure a feeling with knowledge) or ignoring real gaps because they’ve been told “you just have imposter syndrome, you’re fine.”

Be honest with yourself about which one you’re dealing with. If you’ve delivered results in similar situations before and still feel like you don’t belong, that’s imposter syndrome. Stay in the room. If you genuinely can’t do the work being asked of you, that’s a gap. Name it, close it, and stay in the room anyway.

The room is the point. The discomfort is the point. The people who make you feel like you’re not good enough are showing you what good enough looks like, and that’s the fastest path to getting there.

Reframing is the first step. The harder question is what to actually do when you’re in that room and the gap feels enormous. I wrote about that separately: how to operate when you’re the least experienced person in the room.