How Top Engineering Teams Actually Perform
A live index of the industry's leading engineering orgs. Every commit is weighted by the work it represents, not the lines it touched, and reported as ETV per engineer.
+2,692engineers' worth of capacity,
nobody hired
Rows come to +2,685, the index reads +2,692. They are not meant to agree. Why?Hide
Capacity added since the index's own first reading, measured from shipped output. How to read itHide
How fast did it happen?
ETV per engineer, rolling 90 days. Each series starts from its own pre-AI baseline, so read a curve against where it started, not against its neighbours.
Where does each org stand?
Same measure, one card per org. Headcount is not the story, the multiple per engineer is.
Microsoft
Capacity vs pre-AI
8.0x
+846 engineers
10.85 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+128.6%
Work mix
Features
27%
Maint
9%
Tests
49%
Docs
2%
Fixes
13%
OpenAI
Capacity vs pre-AI
12.8x
+319 engineers
9.65 ETV / dev / mo
Avg. dev performance / month (90-day MA)
-14.9%
Work mix
Features
30%
Maint
11%
Tests
37%
Docs
4%
Fixes
18%
Vercel
Capacity vs pre-AI
5.7x
+187 engineers
8.77 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+107.7%
Work mix
Features
30%
Maint
12%
Tests
39%
Docs
6%
Fixes
14%
Capacity vs pre-AI
3.9x
+265 engineers
3.69 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+73.5%
Work mix
Features
31%
Maint
13%
Tests
36%
Docs
5%
Fixes
15%
Meta
Capacity vs pre-AI
4.8x
+642 engineers
3.45 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+150.8%
Work mix
Features
30%
Maint
20%
Tests
32%
Docs
3%
Fixes
15%
Cloudflare
Capacity vs pre-AI
5.4x
+427 engineers
2.25 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+33.6%
Work mix
Features
29%
Maint
10%
Tests
34%
Docs
14%
Fixes
12%
Speed tells you how much a team ships. It doesn't tell you what.
Direction
Faster at what?
The same amount of output can be new features, or fixes to work that already shipped. The mix is the decision.
Performance Composition
How each org's ETV splits across features, maintenance, tests, docs, and fixes.
Patterns
Where does the output come from?
The same measure one level down, at the codebases the output is actually made in. Ranked by per-engineer ETV, this week against the full quarter.
Top 5 Repositories · last 7 days
Highest per-engineer Engineering Throughput Value (ETV) shipped in the last 7 days. Not normalized to a month.
- 1
zerocopy
Google · 1 dev
Features 58%Maintenance 5%Tests 26%Docs 9%Fixes 1%41.2
ETV / dev · 7d
- 2
agents
Cloudflare · 1 dev
Features 25%Maintenance 9%Tests 52%Docs 3%Fixes 10%35.3
ETV / dev · 7d
- 3
vscode
Microsoft · 31 devs
Features 28%Maintenance 10%Tests 46%Docs 2%Fixes 14%7.8
ETV / dev · 7d
- 4
pyrefly
Meta · 8 devs
Features 22%Maintenance 39%Tests 18%Docs 4%Fixes 17%7.2
ETV / dev · 7d
- 5
TypeScript
Microsoft · 5 devs
Features 10%Maintenance 5%Tests 70%Docs 1%Fixes 15%7.1
ETV / dev · 7d
Top 5 Repositories · last 90 days
Highest per-engineer Engineering Throughput Value (ETV) over the trailing 90 days, normalized to a 30-day calendar month.
- 1
zerocopy
Google · 2 devs
Features 51%Maintenance 5%Tests 20%Docs 16%Fixes 8%22.9
ETV / dev / mo
- 2
vscode
Microsoft · 54 devs
Features 27%Maintenance 8%Tests 50%Docs 2%Fixes 13%19.4
ETV / dev / mo
- 3
openai-agents-js
OpenAI · 1 dev
Features 10%Maintenance 5%Tests 48%Docs 11%Fixes 25%18.5
ETV / dev / mo
- 4
turborepo
Vercel · 5 devs
Features 37%Maintenance 13%Tests 37%Docs 2%Fixes 11%17.3
ETV / dev / mo
- 5
agents
Cloudflare · 4 devs
Features 32%Maintenance 8%Tests 41%Docs 8%Fixes 11%14.4
ETV / dev / mo
Your turn
Where does your team stand?
The index measures public repositories. The same measure runs on private ones.