HaiAI123

Curated Global AI Tools Directory

NewIndustry update
New

Amazon memo tells engineers to stop chasing AI token usage

10/28/2026 — 10/28, 04:17·4 sources (all)·4 reports (all)·In the 2026-10-28 briefing

Key takeaways

  • According to CNBC, an internal Amazon memo dated October 27 told engineers to stop optimizing for token usage after some ran unnecessary tas…

Background & analysis

On October 27, 2026, Amazon issued an internal memo setting out how it wants engineers to use AI. According to a CNBC report covered by DEV Community, the memo told engineers to stop chasing token counts and to avoid using token usage, tool adoption rates, or code change counts as targets, describing these practices as 'seriously flawed.' The memo said AI effectiveness should instead be judged by long-term business outcomes.

Before this memo, some Amazon employees had reportedly used an in-house agent platform to run unnecessary tasks in order to inflate their numbers on internal leaderboards, which rewarded usage rather than results. Amazon shut one such leaderboard down in May. CNBC's report framed the memo as an instruction to be more selective about AI use, pushing back against adopting AI just to accumulate tokens, and noted that Amazon, under CEO Andy Jassy, has been integrating AI quickly across its sprawling business operations.

Earlier still, Amazon engineering leaders had updated the role guidelines for software development engineers in the AI era, stressing that what matters most is the outcome, not which tools are used. A separate target, cited by Tom's Hardware and referenced in the coverage, was to have 80%+ of developers using AI weekly. With the memo now public, the situation stands at Amazon formally discouraging token counts, tool adoption rates, and code change counts as measures of AI success, with a reported internal push for 80%+ of developers using AI weekly.

AI-generated from 3 reports · updated 1 hour ago

Latest turnAmazon told software engineers in an internal memo that judging AI adoption purely by token consumption or generated code is "deeply flawed," and discouraged staff from chasing usage numbers for their own sake, CNBC reported. The guidance signals a shift away from raw token counts as a way to grade AI adoption.

Related AI tools

24-hour heatHeat index 380 · peak 386 · now
24 hours agonow

Reports on this story headlines open the original

Today
  1. Amazon told software engineers in an internal memo that judging AI adoption purely by token consumption or generated code is "deeply flawed," and discouraged staff from chasing usage numbers for their own sake, CNBC reported. The guidance signals a shift away from raw token counts as a way to grade AI adoption.

    TechmemeAI score 54
  2. According to CNBC, an Amazon memo dated Oct 27 tells engineers to stop chasing token counts, after some staff reportedly ran needless tasks on an in-house agent platform to climb internal leaderboards. The memo calls token usage, tool adoption and code-change counts "deeply flawed" as targets, urging teams to judge AI by long-term business outcomes.

    DEV Community · AIAI score 54
  3. According to CNBC, an internal Amazon memo tells engineers to be pickier about when they use AI, pushing back on using it just to rack up tokens. Under CEO Andy Jassy, Amazon has been rapidly integrating AI across its sprawling operations.

    CNBC · 科技AI score 54
  4. Amazon engineering leaders have updated the role guidelines for software development engineers in the age of AI, emphasizing that the outcome matters most rather than which tools are used. The update was published on Amazon AI News and puts results ahead of tool choice.

    Amazon AI NewsFirst-partyAI score 55

Other stories people are talking about

How is heat calculated?About the method

Heat counts how many independent sources covered a story in the last 48 hours: one source counts once no matter how many posts it published, decaying with a 24-hour half-life. What ranks first is what many people are talking about.

This page aggregates public feeds. Headlines and summaries are machine-organized and remain the property of the original authors; verify important facts at the source. If you believe a headline or summary infringes your rights, email the contact address in the footer with the page URL and basis of your claim, and we will remove or replace it after review.

Surge
Discussion rising fast
New
First report within 6 hours
Rising
Still gathering discussion

Back to AI industry updates →