What Gergely Orosz thinks about team size
Writes The Pragmatic Engineer, the software-engineering newsletter, and wrote The Software Engineer's Guidebook. Formerly an engineering manager at Uber, and at Microsoft/Skype and Skyscanner before that.
Gergely Orosz did not write this page.
We collected these quotes from things they published elsewhere, and every quote links to where it was said. They have no account here and have not endorsed this site. Quotes are word for word; the short line under each one is our own restatement, not their wording. Their own site. Is this you? Claim it or ask us to remove it. Or tell us what is wrong here.
Filter team size · Newest first
40 more topics
Only Gergely Orosz on team size. See everyone on team size
5 dated positions, 2026, in their own words. Our reading of what Gergely Orosz has said — not written or endorsed by them.
-
Our readingAI is making everyone build much faster
Their wordsAI is making everyone (small teams or big) build much faster…
- 3 days earlier
-
Their wordsTheir business model is to run products with very very small teams vs before.
- 3 weeks earlier
-
Their wordsTheir business depends on co’s not having enough in-house dev capacity, and thus “renting” devs from them.
-
Our readingWith AI tools, in-house development teams can do more and need less rented developer capacity.
Their wordsBut with AI tools, in-house dev teams can do more, and need less “renting”
- 2 weeks earlier
-
Their wordsa healthy oncall schedule needs 6+ engineers if every alert is to be taken seriously by an engineer whose main focus is oncall and systems stability.
↗The Pulse: Meta wanted to reduce teams by 60% because of AIblog.pragmaticengineer.com