Harry Cook

<start of post>

I was talking to a Founder yesterday who is convinced that the "Senior Engineer" title has lost all meaning.

He’s been interviewing for a Lead Backend role for three weeks.

On paper, the candidates look like giants. 10+ years of experience. Names of big-tech firms on their CVs. Lists of languages that span two pages.

But when they get into the technical deep dive?

They can talk about architecture. They can explain high-level concepts. But they struggle to actually build a simple, scalable feature from scratch without a massive support team around them.

He told me: "I don't need a philosopher. I need a builder who hasn't forgotten how to get their hands dirty."

This is the "Architecture Trap."

As engineers move up the ladder, many stop coding. They move into meetings, Jira tickets, and "strategic oversight."

And slowly, their edge blunts.

They become great at telling people how to do the work, but they lose the ability to do the work themselves.

In a startup environment, that is a recipe for disaster.

Still have a side project or a repo they tinker with.

Can jump into a production bug at 4 PM on a Friday and actually fix it.

Understand the "why" but never lose sight of the "how."

If you are a Senior or Lead Engineer, how do you make sure you aren't falling into the Architecture Trap?

And Founders—are you seeing the same thing in your hiring loops right now?

<end of post>