Something in this TechCrunch piece stopped me mid-scroll and I haven't been able to shake it.
The premise: AI token budgets are emerging as a fourth pillar of engineering compensation, alongside salary, equity, and benefits. Some companies are advertising them in job listings. Engineers are treating them as signals of a forward-thinking employer. The framing is unambiguously positive — we give you the tools to do your best work.
But sit with the mechanics for a moment.
Before the token budget era, AI infrastructure spend was a line item on the company's balance sheet. The company chose the tool, the company paid the bill, the company absorbed the variance when usage spiked mid-sprint or a new model repriced its API. That's how it works with laptops, cloud credits, software licences — the infrastructure cost lives with the entity that has the structural capacity to manage it.
The token budget inverts this. Now the engineer holds a monthly allocation. The engineer decides how to spend it. The engineer eats the variance when a long-context task blows through three days of budget in an afternoon. The engineer makes tool choices with one eye on their personal utilisation ledger.
That's not a perk. That's making the worker a cost centre.
The Utilisation Risk Is Real
Here's what nobody in the "tokens as compensation" conversation seems to be naming directly: utilisation risk is now personal.
If your cloud credits run short, that's a company logistics problem. If your token budget runs short in week two of a sprint, that's your problem — and the implicit pressure to ration a tool that's supposed to be making you more productive is a strange kind of gift.
There's also a subtler friction. The moment an engineer has a personal financial stake in tool selection, the tool choice stops being a pure engineering question. Do you pick the expensive model that's genuinely better for this task, or the cheaper one that keeps you safely inside budget? That's not a productivity optimisation. That's cognitive overhead that didn't exist when IT just provisioned you a licence.
I don't want to be cynical about this. Some employers are genuinely trying to give engineers flexibility and autonomy over their AI stack, and that's a reasonable instinct. But "flexibility" and "cost exposure" are not the same thing, and right now they're being sold as a package deal.
The honest version of this offer would say: we're shifting some infrastructure cost to you, in exchange for discretion over how it's spent. That's a trade-off worth evaluating. The dishonest version calls it a signing bonus and hopes nobody checks the mechanics.
Engineers have spent decades watching "flexibility" used as a word that means "you absorb the risk." Remote work stipends that don't cover actual equipment costs. Expense policies that technically reimburse things but practically discourage claims. The token budget, dressed up as compensation, fits that pattern uncomfortably well.
Hold the line before you list it on your offer comparison spreadsheet next to base salary.