Everyone in tech talks about Imposter Syndrome — the fear that you are one bad pull request away from being exposed. We talk less about the mirror image.
The engineer who feels perpetually overlooked. Sure their skills are top-tier. Title, scope, and influence stay put. They simmer because they were left out of an architecture meeting. They are quietly certain a senior promotion is six months overdue, even if nobody else sees the evidence.
From the outside it looks like arrogance. Usually it is more complicated. Call it inverse imposter syndrome: Protagonist Syndrome.
It is the belief that your baseline output is obviously better than how the team treats it. You are the main character. The org's plot should follow your arc. That headspace is miserable, and it is also what keeps the recognition away.
It rarely starts as delusion. It usually starts as talent.
Why it feels true
Most people in this spot are actually good. Clean code. Hard tickets. Features on time. Mastery of this job starts to feel like a coupon for the next one. They have mastered line cooking and cannot see why they are not running the kitchen.
The destination is visible: Staff on Slack, the architecture review on the calendar. The path is not. That path is the work that never shows up in a commit — ambiguity, consensus, mentoring, tying a technical choice back to revenue.
Sometimes the frustration is fair. If your manager will not give usable feedback, or promotion criteria read like a horoscope, ambition fills the silence. In a vacuum you assume you have already done enough.
The traps
"My code should speak for itself." It does, up to a point. Execution gets you in the room. It does not scale you. Seniority is leverage: a design doc that saves six people a month, a team you unblock. Individual throughput has a ceiling. Influence does not.
Invites are not trophies. The architecture sync is not a lounge for the best coders. It is a working session for the people needed on a specific risk. If you are not there, the useful question is not "why was I left out?" It is "how do I become someone the project fails without?"
The unappreciated genius. It is comforting to decide you are a rare gem and management are bad jewelers. Part of the job is translating your value into a language the business speaks. If nobody can see the impact, the work is not finished.
The exception: redwoods in bonsai pots
There is a real exception. You did the honest inventory. The ego is not the problem. The math still does not work.
You may be a redwood in a pot that cannot hold you. Flat startup. Lean agency. There is no Staff role because the company does not need one yet.
Bitterness is the easy next step — shrink until you fit. The move is not to demand a title that does not exist. Help them build a bigger pot, or transplant.
What to do instead
Stop aiming at status. Aim at leverage.
- Own the ugly problems. The vague ticket everyone skips. The first draft of the docs. The new hire who is drowning. This role is not a waiting room.
- Trade the stew for a question. Find someone who was in the room: what were the hard trade-offs? What are we actually trying to solve?
- Do the work. Influence is what happens when you solve hard problems for the people around you. It is a poor target and a decent byproduct.
Imposter Syndrome and Protagonist Syndrome make the same mistake: they make you stare at yourself. One says you do not belong in the story. The other says the story is about you.
Look at the engineering. Look at the team. The spotlight is a bad thing to hunt.