| I recently wound up in conversation with someone working at Amazon. Inevitably, the convo steered into AI/LLM's at some point. Here is what I learned: - AWS had an in-house LLM tool that was terrible they tried to use for a while - A lot of them still use Kiro - Claude Code is currently the de-facto standard - They're in the process of getting some custom Codex variant that doesn't phone-home and is audited approved - There's no mandated organizational standard for what exact tools to some, various teams have different levels of adoption and stacks - No org-wide/team-wide conventions for Claude Code - They do have token budgets - There's an intenral push for something called "Agent Spaces" which was described to me as a sort of Lovable/Bolt-type thing if I understood it right I can't validate all of this and I might have misremembered, but just in case anyone else finds it interesting. |
> No org-wide/team-wide conventions for Claude Code
Just for context, this pattern (different teams using different tools in different ways) is extremely normal within Amazon, and is intentional. These shouldn't necessarily be seen as a failure. Amazon likes to have multiple competing options they use for everything, and they constantly evaluate which option is best performing, like an A/B test. After a couple years they will pare away whatever performs worst, replacing it with a new option. This strategy definitely has it's disadvantages, but it is an intentional chosen pattern throughout the company.
Source: I worked there for 5 years, and painfully/tearfully remember the transitions chime -> slack -> teams and workdocs -> quip -> confluence :')