Hunger beats tenure: Advice for junior engineers

Open original

Felix Rieseberg, a hiring manager at Anthropic, argues that AI has made the traditional coding interview obsolete and that engineers without seniority can now move fast by building working prototypes. He offers a playbook for newcomers to get noticed by tying their work to business impact.

  • Anthropic stopped giving coding interviews because Claude now outperforms candidates on small coding challenges, and top builders succeed regardless of how they do on them.
  • Newcomers have an advantage in spotting friction and questioning assumptions that old-timers stop noticing, but they usually lack the status to get ideas funded.
  • AI has cut the cost of execution, so a junior engineer can build a focused prototype over a weekend and skip the usual PRD and buy-in process. Keep it to one good idea, aimed at a business goal.

Felix Rieseberg, a hiring manager at Anthropic, has dropped the traditional coding interview. His reasoning: small coding challenges used to be a weak but real signal of how someone would perform, but Claude now outperforms candidates at those tasks, so the test no longer tells him anything useful. He argues that impact now depends less on years of accumulated framework knowledge and more on hunger, and that engineers without social capital, status, or power are well placed to exploit that shift. Newcomers bring fresh eyes and the ignorance to try things veterans have stopped questioning. He cites his own Notion interview, where an offline mode was dismissed as impossible on the assumption that nobody had checked, and his later experience of a new hire getting large TVs for live dashboards after he'd given up on the same idea. The core obstacle he identifies is that nobody listens to newcomers, because org structures route decisions through managers and rarely change quickly. His answer is that execution is no longer expensive, so the old bottleneck of grinding for status before anyone funds your idea matters less. His concrete playbook has five parts: pick work tied to business impact (he points to Patrick McKenzie's line that engineers are hired to create business value, not to program things), find a radical idea that would meaningfully move those goals, build a working prototype over a weekend instead of writing a PRD and lobbying for time, keep the prototype to one good idea rather than a pile of them, and lean on your outsider's empathy for users. He notes that Slack and Notion staff often struggled to see their products the way external users do, which is an advantage newcomers have. To show how fast this can go, he describes Anthony Morris and Alice Zhao, two relatively new Anthropic engineers, who built a working prototype of a Claude Code interface over a single weekend. The first public version shipped about eight days later. He closes by saying he's now scanning résumés and portfolios for small prototypes that show taste, empathy, and principled thinking, and he's asking readers for better ways to interview for those qualities. The piece is short, opinionated, and grounded in specific anecdotes, though its evidence is mostly one manager's observations inside one company.

Ask about this article