He left a $65B payments empire to write about it. Then a million engineers showed up to read.
Gergely Orosz spent six years at Uber in Amsterdam building the plumbing that moves money for 60+ countries - $65 billion in annual transaction volume flowing through systems he helped architect. When Uber went public in 2019, his stock vested. When COVID reshaped everything in 2020, he started writing. In August 2021, he went independent. By April 2025, The Pragmatic Engineer newsletter had crossed one million subscribers.
That's the headline version. Here's the stranger version: he graduated top of his class from Budapest's oldest engineering school - a university founded in 1782, older than the United States Constitution - and then watched recruiters abroad squint at the institution name like it was a typo. He built Hungary's most popular cocktail website in high school. He once competed in the Modern Pentathlon, the Olympic sport that combines swimming, running, shooting, fencing, and horseback riding. He co-wrote gambling software for German casinos with his brother during university. He insisted on unit tests. His peers thought he was being ridiculous. Years later, the maintainers called it the smartest decision in the codebase.
He is - by his own honest accounting - a generalist. "I get bored if I do the same thing for more than a year," he has written. He was a software engineer at JP Morgan, then Skype, then Skyscanner, then Microsoft again, then Uber. Each transition was not restlessness but calibration. He was searching for a problem that would hold his attention long enough to matter.
I've specialized at being a generalist. Being a generalist, at least for me, is not a choice - it's an extension of my personality.
- Gergely OroszHe found it in a newsletter. Not because newsletters are glamorous - they're not - but because nobody was telling engineers what was actually happening inside Big Tech, in plain language, with enough specificity to be useful. The Pragmatic Engineer does not traffic in press releases or LinkedIn-optimized career advice. It publishes what engineering teams inside Meta, Google, Amazon, and Uber are actually doing: the org restructures, the hiring freezes, the technical debt that accumulates when growth becomes the only metric, the AI coding tools that 92% of developers were using by early 2026 according to the survey at his own summit.
He does this with zero advertisers. Zero sponsors. Zero affiliate deals. The newsletter runs entirely on paid subscriptions - $15/month or $150/year - and clears more than $1.5 million annually. That's not a newsletter. That's a media company with one employee who controls everything.
In 2018, Gergely walked into a 2-million-line codebase mid-project. The Uber Rider App. Four hundred engineers. A 3-to-4 month deadline that the team had already been told was impossible. He was promoted to project manager within weeks. He reorganized the work. They shipped on time. He has never described this as an achievement. He describes it as a good example of what "finishers" actually look like - the experienced engineers who show up not when the project is at 0% but when it's at 90%, knowing full well that the other 90% is still ahead.
Every Tuesday. Every Thursday. No filler. No sponsored content.
The Pragmatic Engineer publishes on Tuesdays (deep-dive educational long-form), Thursdays ("The Pulse" - timely industry news), and Wednesdays when there's a new podcast episode. In 2025, that meant 134 issues. The editorial calendar for 2025 was shaped by the things nobody else was covering with rigor: AI coding tools moving from experiment to standard practice, the engineering job market tightening in ways that didn't match the mainstream tech narrative, return-to-office battles inside companies that had built distributed cultures by necessity.
The podcast launched in 2024 and crossed 10 million downloads by year's end - an unusual number for a show that doesn't do weekly episode drops, doesn't obsessively optimize for charts, and doesn't book guests to fill airtime. The episodes are long and technical and assume you already know what a distributed system is.
In February 2026, Gergely hosted the first Pragmatic Summit in San Francisco - a one-day conference for 400 engineers and engineering leaders examining AI's actual impact on software development. The headline finding: 92% of developers were using AI coding tools at least monthly. The follow-up question nobody at the conference could cleanly answer: what does that mean for the next five years of the profession?
We're done with 90% of the project. Which means we only have the other 90% left to go. It's funny because it's true. It's also why experienced engineers are in-demand: they are the finishers.
- Gergely Orosz, on X/TwitterFour books. One that became an Amazon #1 Best Seller. All four written outside business hours at first.
The Software Engineer's Guidebook
40,000+ copies sold. Translations in German, Korean, and incoming in Japanese, Chinese, Mongolian, and Hungarian. The definitive career guide from entry level to staff engineer - four years in the making.
Building Mobile Apps at Scale
39 engineering challenges drawn from Uber's mobile infrastructure. The kind of book that exists because Gergely kept answering the same questions at conferences and eventually just wrote them all down.
Growing as a Mobile Engineer
Thirty pieces of specific, un-vague advice for engineers moving from mid-level to senior on iOS or Android. Not a career philosophy book. A career instruction manual.
The Tech Resume Inside Out
Free for developers out of work. Based on five years of hiring manager experience and input from 20+ recruiters. The antidote to resume advice written by people who have never actually hired anyone.
Eight employers in twelve years. Then, one of his own.
JP Morgan - Junior software engineer. Trading software. London and Edinburgh. The first real job after graduating top of his class in Budapest.
Skype / Microsoft - Software engineer in the UK, before Microsoft acquired Skype. Then inside Microsoft after it did.
Skyscanner - The flight search company. Pre-unicorn, when it still had the feel of something being built rather than scaled.
Microsoft - Returned as both engineer and PM. Built Skype for Xbox One. Helped ship Skype for Web. Two very different technical challenges, simultaneously.
Uber, Amsterdam - Engineering Manager. Uber Money. Payments infrastructure that would eventually process $65 billion annually across 60+ countries. Six years. The IPO. The pandemic. The exit.
The Pragmatic Engineer - Independent. August 25th, the newsletter launches on Substack. The financial runway: Uber stock that vested at IPO. The goal: never need an advertiser.
One million subscribers. Zero sponsors. Still writing every Tuesday and Thursday. Still the only person doing exactly this job exactly this way.
Reader-funded journalism inside a profession that runs on stock options and confidentiality agreements.
Most tech media is funded by the companies it covers. Press releases become articles. Advertorials run next to news. Conferences are sponsored by the platforms being reviewed. Gergely Orosz decided early that this structure was incompatible with the kind of reporting he wanted to do. The Pragmatic Engineer has never taken an advertiser. Not because he couldn't - at a million readers, the inbound is substantial - but because the independence is the product.
He is explicit about his revenue numbers. He publishes subscriber counts. He describes how the business actually works. This is not accidental. Transparency is a deliberate editorial choice - a signal to readers that the only entity he's accountable to is them. When he breaks a story about layoffs inside a major tech company before the official announcement, the story lands with weight precisely because there's no advertiser relationship at stake.
He is, by his own admission, protective of his time to the point of policy. As of early 2026, his now page - a personal website convention that tells readers what you're actually working on - explicitly lists what he no longer does: interviews, podcast appearances, mentoring sessions, coffee chats, AMAs, collaborations. This is not rudeness. It's math. At a million readers, even a 0.01% request rate is a thousand people asking for something each week.