AI-Native Development in Big Tech in 2026
Microsoft, GitHub, Google, Amazon, Meta, Uber, Stripe, Netflix
Slide contents
1. AI-Native Development in Big Tech in 2026
Microsoft, GitHub, Google, Amazon, Meta, Uber, Stripe, Netflix
2. 00. AI Joins Engineering Process
3. A New Operating Model
AI joins delivery system
AI becomes operating-model layer
Metrics move beyond adoption
DORA: 90% AI use; 80%+ gains
Processes matter more than permission
4. Metrics Are Evolving
5. 01. Microsoft & GitHub
6. AI Code Review at Company-Wide Scale
7. Coding Agent as Part of the Platform
8. 02. Google
9. Velocity as the Key KPI
Source: Google AI workplace examples
30% — Of new code is generated with AI assistance
10% — Estimated engineering velocity improvement
12% — Duplicate bugs automatically handled by an AI agent
10. Key Principle
11. 03. Amazon & AWS
12. The Language of Economics
Source: AWS DevOps Blog
450,000+ hours — Reduced waiting for technical answers via Amazon Q
4,500 dev-years — Saved on AI-driven software transformations
15.9% — Year-over-year cost reduction in 2024 through end-to-end improvements
13. CTS-SW: Cost to Serve Software
14. 04. Meta
15. Ranking Engineer Agent (REA)
16. 05. Uber
17. uReview: Production Scale
Source: Uber Engineering
90%+ — Of weekly ~65K diffs analyzed by AI
75% — Of comments rated useful by engineers
~1,500 hrs/wk — Estimated time savings
18. AI Across All SDLC Stages
19. 06. Stripe & Netflix
20. Goal: 2× Engineering Velocity via LLMs
21. Platform → Evals → Scaling
22. 07. AI-native planning has four layers
23. Adoption → Throughput → Quality → Economics
24. 08. AI-Native Becomes Operating Model
25. Key Takeaways
Humans become orchestrators
Key question: delegated scenarios, flow impact, economics
AI becomes a standard participant
AI-native becomes operating model
26. References and Materials
Key sources used in this presentation
DORA; Microsoft; GitHub.
Google; Amazon CTS-SW.
Meta REA; Uber uReview.
Stripe benchmark; Netflix scaling.
27. Thank You!
AI-Native Development in Big Tech
For more materials on this topic, visit the "Book Cube" channel — all links are collected there
Alexander Polomodov, Technical Director & Fellow, T-Technologies
@Book_Cube