Org Leaders: Is Your AI Policy Attracting the Best Talent?

Org Leaders: Is Your AI Policy Attracting the Best Talent? 图片 1
Org Leaders: Is Your AI Policy Attracting the Best Talent? 图片 2
Org Leaders: Is Your AI Policy Attracting the Best Talent? 图片 3
Org Leaders: Is Your AI Policy Attracting the Best Talent? 图片 4

Jensen Huang said recently that he expects an employee earning $500,000 to consume $250,000 worth of tokens, and he called token allowances “one of the recruiting tools in Silicon Valley.”

Around the same time, Andrej Karpathy admitted he gets nervous when he doesn’t burn through his AI budget, and that when he hits a quota on one tool, he simply switches to another.

Now picture the engineer you’re trying to hire in that world. One offer comes from a company where AI usage is firmly encouraged, because they’ve built the governance, model flexibility, and cost visibility to make freedom affordable. The other comes from a company where a $1,500 monthly cap kicks in around week two and over-limit requests need a manager’s sign-off.

The salary and title are identical, so where does that engineer go?

This isn’t hypothetical anymore. Uber burned its annual AI coding budget in four months and responded with per-employee caps. Microsoft’s Experiences and Devices division gave thousands of engineers Claude Code, watched token billing consume the annual budget ahead of schedule, and mandated a migration to a cheaper tool. Gartner is now forecasting that AI coding token costs will overtake the average developer’s salary by 2028, and their peer data shows 6% of organizations already spend more than $2,000 per developer per month.

To be clear, the cost concern is legitimate. Nobody should be handing out blank checks, and the “tokenmaxxing” era of ranking employees by consumption deserved to die. But the response most organizations reached for, hard caps on a single premium provider, solves the spend problem by creating a talent problem.

The question worth asking isn’t “how do we limit usage.” It’s “did we build the tooling and cost optimizations that let us give developers access to everything they want to use?” Those are very different engineering problems, and only one of them shows up in your offer letters.

What developers actually do when nobody constrains them

At Kilo, we sit in…

添加评论
点赞收藏
点踩分享查看原文
评论
?
参与讨论