Dealing with Imposter Syndrome in Tech: How Do You Cope When You Feel Underqualified?

I've been working as a software engineer for over two years now, but every time I start a new sprint or look at senior codebases, I feel like a total fraud who doesn't belong here. Even though I pass code reviews and deliver features, the nagging fear that everyone will realize I have no idea what I'm doing is exhausting. How do you all cope with imposter syndrome in the tech industry without burning out?

Two years is right around the time the Dunning-Kruger effect wears off and you realize how much you actually don't know. It's completely normal, but it sucks.

If it makes you feel any better, I've been doing this for over a decade and I still google basic syntax sometimes. Senior codebases look terrifying because they usually are terrifying.

Focus on the fact that you are passing code reviews and delivering features. Data doesn't lie—your team trusts your output, even if your brain is telling you otherwise.

When my back starts hurting from staring at code all day stressing over this, I try to adjust my setup. Honestly, switching to ergonomic standing desks helped my physical posture, which weirdly helped my mental fatigue a bit too.

Keep a 'wins' folder. Whenever someone compliments your PR or you fix a nasty bug, screenshot it and put it in there. Read it on days when the imposter syndrome hits hardest.

Remember that software engineering isn't about knowing everything; it's about knowing how to figure things out. No one expects you to memorize the whole codebase.

Tech moves so fast that literally everyone feels underqualified at some point. The moment you stop feeling that way is usually the moment you stop growing.

Try talking about it with your manager during 1on1s. You don't have to frame it as 'I'm a fraud,' but rather 'I'd love to learn more about X architecture to feel more confident.'

I used to stay up late reading documentation just to catch up, which led straight to burnout. You have to set a hard boundary between work time and offline time.

Sometimes when my brain is fried from debugging, I log off and focus on completely unrelated habits, like managing my personal finances or reading up on long-term index funds to ground myself outside of tech.

Senior devs write messy code too. You just only see the polished end result of their refactoring, while you're seeing your own raw process.

Give yourself permission to be a junior-leaning-mid dev. You don't need to have senior-level answers after two years.

You belong in the room because you were hired through the same process as everyone else. Trust the hiring managers who saw your potential.