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,471engineers' worth of capacity,
nobody hired
Rows come to +2,462, the index reads +2,471. 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.
OpenAI
Capacity vs pre-AI
15.9x
+389 engineers
12.01 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+25.9%
Work mix
Features
30%
Maint
8%
Tests
41%
Docs
5%
Fixes
17%
Microsoft
Capacity vs pre-AI
7.5x
+781 engineers
10.12 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+153.6%
Work mix
Features
28%
Maint
10%
Tests
47%
Docs
3%
Fixes
13%
Vercel
Capacity vs pre-AI
5.1x
+168 engineers
7.88 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+92.8%
Work mix
Features
30%
Maint
12%
Tests
38%
Docs
7%
Fixes
13%
Capacity vs pre-AI
3.5x
+228 engineers
3.25 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+41.2%
Work mix
Features
30%
Maint
14%
Tests
36%
Docs
6%
Fixes
15%
Meta
Capacity vs pre-AI
3.8x
+494 engineers
2.71 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+116.4%
Work mix
Features
33%
Maint
20%
Tests
28%
Docs
3%
Fixes
16%
Cloudflare
Capacity vs pre-AI
5.0x
+403 engineers
2.09 ETV / dev / mo
Avg. dev performance / month (90-day MA)
+53.2%
Work mix
Features
31%
Maint
11%
Tests
32%
Docs
15%
Fixes
11%
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
turborepo
Vercel · 1 dev
Features 22%Maintenance 23%Tests 52%Docs 1%Fixes 1%22.5
ETV / dev · 7d
- 2
vscode
Microsoft · 36 devs
Features 24%Maintenance 7%Tests 54%Docs 2%Fixes 13%7.9
ETV / dev · 7d
- 3
ai
Vercel · 6 devs
Features 31%Maintenance 8%Tests 39%Docs 10%Fixes 12%7.0
ETV / dev · 7d
- 4
pyrefly
Meta · 7 devs
Features 37%Maintenance 20%Tests 19%Docs 2%Fixes 22%6.9
ETV / dev · 7d
- 5
guava
Google · 1 dev
Features 37%Maintenance 20%Tests 40%Docs 2%Fixes 1%5.5
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
openai-agents-js
OpenAI · 1 dev
Features 16%Maintenance 2%Tests 54%Docs 12%Fixes 15%36.1
ETV / dev / mo
- 2
turborepo
Vercel · 3 devs
Features 37%Maintenance 14%Tests 35%Docs 2%Fixes 11%29.1
ETV / dev / mo
- 3
openai-agents-python
OpenAI · 2 devs
Features 20%Maintenance 2%Tests 51%Docs 14%Fixes 13%21.9
ETV / dev / mo
- 4
vscode
Microsoft · 54 devs
Features 28%Maintenance 8%Tests 49%Docs 2%Fixes 13%17.9
ETV / dev / mo
- 5
zerocopy
Google · 2 devs
Features 48%Maintenance 5%Tests 18%Docs 18%Fixes 11%16.1
ETV / dev / mo
Your turn
Where does your team stand?
The index measures public repositories. The same measure runs on private ones.