· ai-devtools

Anthropic Hiring Manager advises junior engineers on impact over tenure

At Anthropic, the traditional coding interview has ceased to provide meaningful indicators of potential.


The author, a hiring manager there, stopped requiring candidates to complete these assessments this month. While quick problem definition and elegant solutions were once a weak but useful predictor of team success, small coding challenges in real code no longer offer that insight. Claude now surpasses human ability in both these areas, making such tests redundant.

The core message is that impactful builders succeed irrespective of their performance on these standardized tests. The concept of "Hunger beats tenure" is the central piece of advice for engineers lacking established social capital or status.

Fresh perspectives, even those that appear naive, have historically held considerable power. When joining Stripe, founder Patrick Collison advised newcomers to keenly observe details that seemed strange to them. This aligns with James March's notion that organizations rely on "maintaining an influx of the naive and ignorant."

The author recalls an incident at Notion where a perceived "trick" interview regarding offline-mode architecture revealed a missed opportunity. The founder’s resistance to the complexity of syncing the data model, which the author, as a newcomer, had not questioned, proved to be a significant oversight.

The challenge with such "ignorant power" is that organizational structures often prevent new ideas from gaining traction. In environments where execution is costly, one typically needs significant social standing before an organization will commit to a new venture.

However, execution is no longer so prohibitively expensive thanks to advancements in AI. The advice shifts toward prioritizing business impact over backlog tasks. This involves understanding the company’s true objectives and finding the right level of organizational focus.

Ambitious engineers should generate radical ideas that could dramatically advance organizational goals. A practical method involves building a working prototype over a weekend, bypassing lengthy processes like writing product requirements documents (PRDs).

When prototyping, focus must remain on a single, strong concept; attempting to incorporate too many ideas dilutes the message. The purpose of a working prototype is to communicate an idea so clearly that leadership grasps both the opportunity and the candidate's ability to execute it.

The author notes that infrastructure and tooling engineers benefit from a unique vantage point, never having been taught why certain things are deemed "impossible." At Anthropic, two relatively new engineers, Anthony Morris and Alice Zhao, built a working prototype for Claude Code as a CLI over one weekend, leading to the first public version shipping about eight days later.

Related coverage

Also worth reading

  1. next.js 16.5.0-canary.35 released
  2. next.js 16.5.0-canary.33 released
  3. angular 22.2.4 released
  4. LibreOffice's 'no AI' stance meets LLM-assisted code
  5. “Urgency is an inherently subjective call”: Anthropic tells TNS how it grades Claude Duet