When you give a tenured engineer a task, they produce a Jira ticket and then nothing else.
That line from Felix Rieseberg's recent essay "Hunger beats tenure" hit hard because it is true for too many teams. Not because senior engineers are bad at their jobs, but because the career ladder has limited rungs. Once you climb past a certain level, there is no way up without becoming a manager or reaching an individual contributor ceiling.
The coding interview is dead at his team. After seeing enough evidence, Rieseberg wrote on Anthropic's engineering team that it no longer provides signal. So what does? The answer is building things that work. Here is the framework he offers to junior engineers who want to break through.

The problem with tenure
Rieseberg frames the issue simply: tenure is a reward for surviving. But survival does not prove you can build what matters next. When promotion becomes automatic rather than earned through shipped work, the gap widens between who is building and who is managing.
This is not a criticism of individual engineers. It is a structural problem with how most companies measure engineering quality. The coding interview was supposed to solve this. Show up, solve a whiteboard puzzle, prove you are smart. But that test measures one kind of ability. It does not measure whether someone can ship something useful.
The career ladder creates its own ceiling. Above a certain level: no more rungs. You either move into management or stay put as an individual contributor at a very senior title. Rieseberg describes himself as "a longtime hater of promotions by tenure" for exactly this reason. When advancement depends on years rather than output, the signal gets noisy.

The five-step framework

Step one: Understand what your company is actually trying to accomplish
Find the right altitude, he says. Learn what your organization wants and then look one layer up at what your manager's manager cares about. This is often a useful proxy for where the real priorities lie.
Think of it like reading a map. You need to see both your immediate location and the horizon. A junior engineer doing the right task will always outperform one doing the wrong task well.
Step two: Pick a radical idea
Come up with ideas that would dramatically improve your organization's chances of hitting those goals. Be ambitious. Rieseberg does not mean "build a slightly better login page." He means find the thing that shifts the needle if it works.
The key word is "radical" because most safe ideas have already been explored by people with deeper pockets. A junior engineer who has nothing to lose can afford to go big.
Step three: Build it over a weekend
This is where hunger replaces process. Small groups and solo engineers fly past the usual cycle of product requirements documents, buy-in meetings, and lobbying for time with designers. They build something that works instead.
The proof point: at Anthropic, two relatively new engineers named Anthony Morris and Alice Zhao built a working prototype of the Claude Code command-line interface over one weekend. The first public version shipped roughly eight days later. A good graphical interface for Claude Code is now very popular.

The future is bright
Rieseberg does not think the coding interview will come back. It is easy to feel sentimental, given how many copies of algorithms and data structures books were sold in hopes of unlocking good jobs. But the death of the coding interview marks something real: software engineering reaching a new level of abstraction where showing what you built matters more than solving puzzles on a whiteboard.
The Claude Code example proves it. Two new engineers built something people wanted without going through any traditional approval process. That is what hunger does. It turns an idea into a product faster than anyone expected.
What he looks for now
I have been scanning resumes and portfolios for little prototypes that exhibit taste, empathy, and principled thinking. If you have figured out something better, it is worth sharing.
That line summarizes everything. Instead of whiteboard puzzles, Rieseberg looks for:
- Prototypes: real, working things
- Taste: evidence that the builder understands what makes a product good
- Empathy: understanding how real users experience software
- Principled thinking: not just hacks, but decisions backed by reasoning he can follow

Two kinds of fresh perspective
There are two different advantages to being junior:
User-facing work: You have a unique empathy for users. Your colleagues at Slack and Notion had a hard time internalizing what using Slack or Notion is like as an external user. The people inside the system forget what it feels like to be outside it.
Infrastructure work: You benefit from not having learned all the reasons things are impossible yet. Every veteran engineer has a mental catalog of "that can't be done because." A newcomer only sees what needs to be done.

Why this matters for everyone
The tension between hunger and tenure touches something everyone in tech feels: does experience alone make you valuable? Or do you still need to prove it, again and again, by building things people actually use?
Rieseberg's answer is clear. Build something. Show what it can do. Let the work speak louder than your title.
What to take away
Hunger beats tenure because it is measured by what ships, not by how long you have been around. The future belongs to people who build prototypes instead of writing Jira tickets and to anyone who can show taste, empathy, and principled thinking in their work. Follow along at https://myargoquest.com/blog for more perspective on engineering culture.