How Uber uses AI for development: inside look
Summary
Uber has significantly integrated AI into its engineering workflows, aiming to become a "GenAI-powered" company by eliminating toil and freeing engineers for creative work. This initiative, detailed by Principal Engineer Ty Smith and Director of Engineering Anshu Chada at The Pragmatic Summit, involves a four-layer agentic system built on Uber's Michelangelo platform, accessing internal context, supporting industry agents like GitHub Copilot, and deploying specialized agents for tasks like code review. Uber developed internal tools such as the MCP Gateway for standardized agent-data interaction, Uber Agent Builder for no-code agent creation, and the AIFX CLI for agent provisioning and management. The company also introduced Minion for scaling background agents and new dev tools like Code Inbox and uReview to manage increased AI-generated code. Currently, 92% of Uber developers use agents monthly, with 31% of code being AI-authored, yet AI-related costs have surged 6x since 2024.
Key takeaway
For AI Architects and Directors of AI/ML evaluating internal AI adoption, Uber's experience highlights the necessity of a robust, integrated AI stack and developer-centric tooling. Your strategy should prioritize eliminating developer toil and providing intuitive platforms like Uber's MCP Gateway and Agent Builder to foster organic adoption, rather than relying on top-down mandates. Be prepared for significant cost increases, as Uber saw a 6x rise in AI-related costs since 2024, necessitating early token cost optimization strategies.
Key insights
Uber's comprehensive internal AI stack transforms developer workflows, automating toil and increasing code generation.
Principles
- AI should eliminate toil, not automate all engineering.
- Standardized protocols (MCP) are crucial for agent integration.
- Developer experience tools drive AI adoption and efficiency.
Method
Uber's agentic system uses an internal AI platform, context sources, industry tools, and specialized agents, managed via an MCP Gateway, Agent Builder for workflows, and the AIFX CLI for provisioning.
In practice
- Implement a central gateway for AI agent-data interaction.
- Develop no-code tools for internal agent creation.
- Provide a CLI for unified agent provisioning and updates.
Topics
- AI Agents
- Developer Workflows
- Internal AI Platform
- Code Generation
- Cost Optimization
Best for: AI Architect, CTO, Director of AI/ML, AI Engineer, Machine Learning Engineer, Software Engineer
Related on AIssential
Editorial summary, takeaway, and curation by AIssential. Original article published by The Pragmatic Engineer.