I’ve spent most of my career leading engineers who were smarter, more accomplished, and more technically impressive than I will ever be. PhDs. Architects who could hold a whole system in their head. People who wrote code so clean it made my reviews feel optional.
For a long time that was a quiet problem. I would sit in an architecture review, listen to them argue an algorithm I was only following, and think: what do I even bring? They did not need me on the implementation. They needed space and a direction. When I tried to "add value" on the technical merits, it felt like handing a crayon drawing to someone mid-canvas.
The job is not to be the best player. The job is to make the field playable.
Stop competing with them
If you pick up the instrument to prove you belong, you become a bottleneck with a title. Your work is tempo, priorities, and whether the whole thing is actually pointed at a result or just a lot of talented noise.
The insecure version of this job is easy to spot. You nitpick pull requests to stay in the conversation. You insert yourself in every meeting. You manage people who did not need managing. That is not standards. That is fear looking for a costume.
What they actually need from you
Be the shield. Deep work dies in a calendar. Kill the meeting that does not need them. Absorb the priority whiplash and the status theater. Translate the noise so they can stay on the signal. You will earn more trust this way than with any clever comment on a diff.
Own the why. They own the how. Your altitude is different: other teams, the customer, the quarter, the thing leadership has not written down yet. Bring that back as context, not as a solution. Why this feature. Who is in pain. What "done" means besides "merged."
Ask better questions. "Use a queue here" is a cheap way to feel useful. Better:
- Where does this fail?
- What would we do if traffic were 100x in two years?
- What is the smallest test of the actual assumption?
- What is the risk you are least comfortable with, and how can I help?
Their answers will be better than your prescription. That is the point.
Make the next job possible. Know what they want — specialist, architect, manager of other people — and steer real work toward it. And when they take a hill, say so. People who only hear about the next mountain stop believing the last one counted.
Why this is not a demotion
They get autonomy and problems that matter. You get forced out of the ego job and into the actual one: clarity, protection, judgment about which work.
Hiring people smarter than you is not evidence that you are failing. It is evidence that hiring worked. The remaining test is whether you can get out of their way without disappearing.
Protect the time. Bring the context. Ask the question you are actually there to ask. Then let them play.