← Reddit

Engineering leaders - do your interview questions assume candidates can afford Claude Code Max?

Reddit · OfficialLeadDev · August 12, 2026
James Lowman, engineering team lead at Starboard, began asking interview candidates about the last three Claude Code skills they had written to evaluate their fluency with AI agents. The question became his standard interview approach until he realized a critical flaw: it assumed all candidates could afford access to Claude Code Max.

Detailed Analysis

A hiring manager's seemingly straightforward interview question has surfaced an uncomfortable equity problem in the AI coding era. James Lowman, an engineering team lead at trade infrastructure company Starboard, began asking candidates to describe the last three Claude Code skills they had written, treating the question as a practical litmus test for fluency with agentic coding tools. The approach made intuitive sense: as AI coding assistants become central to modern software development workflows, understanding how a candidate actually uses these tools in practice seemed far more revealing than abstract discussions of AI knowledge. But Lowman discovered that the question inadvertently filtered for something unrelated to skill or aptitude — access to money. Claude Code Max, the premium tier needed to make heavy, sustained use of Anthropic's coding agent, carries a real cost, and not every capable engineer can justify or afford that expense, especially candidates between jobs, early-career developers, or those from regions where subscription costs represent a larger share of income.

This dynamic matters because it exposes a structural tension in how the tech industry is adapting its hiring practices to the agentic AI shift. Companies increasingly want engineers who can work fluidly with AI coding agents, treating that fluency as a proxy for future productivity and adaptability. Yet the tools best suited for demonstrating deep, sustained experience — like Claude Code's higher-tier subscriptions that unlock expanded usage limits, more powerful models, and features like custom "skills" — are gated behind paywalls that not all job seekers can clear, particularly while unemployed. An interview question intended to be a neutral technical filter risks becoming a de facto wealth test, privileging candidates who already have employer-funded access, side income, or personal savings to spend on premium AI subscriptions, while penalizing equally talented engineers who've been experimenting with free or lower-tier alternatives.

The episode also reflects broader unease about how quickly AI tooling costs are becoming embedded in expectations around technical competence. Anthropic has pushed Claude Code aggressively into professional workflows, with Max plans marketed toward power users and enterprise teams who need higher throughput and fewer rate limits. As adoption spreads, the tools someone can afford to use daily increasingly shapes the depth of experience they can showcase in interviews — a dynamic reminiscent of earlier debates about unpaid internships or expensive bootcamps gatekeeping entry into tech, now recurring in the context of AI subscriptions. It raises the question of whether "AI fluency" as an interview criterion is measuring genuine skill or simply measuring who can pay for practice reps.

More broadly, this incident is a small but telling data point in the rapid, uneven diffusion of agentic AI coding tools across the labor market. As companies like Anthropic, OpenAI, and others compete to make their coding agents indispensable to professional developers, the economic stratification of who gets fluent access to these tools — employed engineers with corporate subscriptions versus job seekers paying out of pocket — could quietly reshape hiring pipelines and widen existing inequities in tech recruiting. Engineering leaders like Lowman rethinking their interview questions in response suggests an early, healthy course-correction, but it also signals that as agentic coding becomes table stakes, the industry will need to grapple more deliberately with cost, access, and fairness rather than assuming technical fluency and financial privilege are unrelated.

Read original article →