Table of Contents
- Background: Twelve Years of Big Tech Experience
- Leaving Uber: The Pandemic as Catalyst
- Growth Timeline
- Content Strategy: The Insider's View of Big Tech
- Business Model: Pure Subscriptions, Zero Ads
- Growth Engine: Zero Marketing Spend
- The Team: From Solo to a Small Crew
- Three Key Lessons
- The Big Picture
- References
🌏 中文版
In August 2021, Gergely Orosz hit "publish" on Substack from his home in Amsterdam. Six weeks later, he had 1,000 paying subscribers. Four months later, The Pragmatic Engineer was the #1 technology newsletter on the platform.
This wasn't a flash startup. He'd spent twelve years writing code at major tech companies and six years building a blog before reaching that point.
Background: Twelve Years of Big Tech Experience
Gergely Orosz was born in Hungary and graduated top of his class from Budapest University of Technology. His career spanned four companies over twelve years:
JP Morgan (2009): Built equity derivatives trading systems in London and Edinburgh.
Skype / Microsoft (2010–2013): Joined Skype before the Microsoft acquisition, then helped ship Skype for Xbox One and Skype for Web — products with over 400 million users at the time.
Skyscanner (2012): Launched Skyscanner TravelPro, a corporate travel booking solution. Signed TransferWise as the first customer — but the product ultimately didn't reach product-market fit.
Uber (2015–2021): Spent six years at the Amsterdam office, rising from engineer to payments team lead. He managed mobile, web, and distributed systems teams, overseeing payment infrastructure that processed over $65 billion in annual transaction volume across 60+ countries. Those six years took him through Uber's IPO and the pandemic.
In 2015, while still at Skyscanner, he started the PragmaticEngineer.com blog — inspired by Jeff Atwood's (Coding Horror, Stack Overflow) writing philosophy. It started with fewer than 1,000 monthly visitors. By 2019, he'd launched a monthly email digest that grew to about 9,000 subscribers.
Those six years of "side hustle writing" turned out to be the single most important asset for his full-time venture.
Leaving Uber: The Pandemic as Catalyst
In March 2020, global lockdowns hit and Uber's rideshare business collapsed overnight. The company laid off roughly 15% of staff — a quarter of the people on Gergely's team were let go. That was the trigger.
In October 2020, he resigned. The plan was to spend six months finishing The Software Engineer's Guidebook, a book he'd been thinking about for years. Uber stock that vested after the IPO gave him a financial runway.
But while working on the book, he noticed his email digest kept growing, and readers kept asking the same types of questions: What actually happens inside Big Tech? How do engineering teams really operate? Nobody was answering these questions in plain language with enough specificity to be useful.
On August 25, 2021, he officially launched The Pragmatic Engineer on Substack, importing those 9,000 existing subscribers and going paid from day one.
Growth Timeline
| Date | Milestone |
|---|---|
| 2015 | Started the PragmaticEngineer.com blog |
| 2019 | Launched monthly email digest, 9,000 subscribers |
| Oct 2020 | Left Uber |
| Aug 25, 2021 | Launched on Substack |
| Oct 2021 (~6 weeks) | 1,000 paying subscribers; Top 10 tech on Substack |
| Dec 10, 2021 | Launched "The Scoop" exclusive content for paid subscribers |
| Dec 2021 (~4 months) | #1 technology newsletter on Substack |
| Apr 2022 | Substack's recommendation feature drives major free subscriber growth |
| Aug 2022 (year one) | 150,000+ subscribers (free and paid); income exceeds Uber salary |
| Nov 2022 | 200,000+ subscribers |
| 2023 | Published The Software Engineer's Guidebook — #1 on Amazon |
| 2024 | Podcast launched; surpassed 10 million downloads by year-end |
| Apr 2025 | Crossed 1 million subscribers |
| Late 2025 | 1,073,929 subscribers; 200,000+ added during the year |
| Feb 2026 | First Pragmatic Summit (San Francisco, 400 attendees) |
He reached 1,000 paying subscribers in six weeks. At launch, he gave himself roughly 50-50 odds of success.
Content Strategy: The Insider's View of Big Tech
The Pragmatic Engineer runs on two fixed content pillars, published every Tuesday and Thursday:
Tuesday Deep Dives: Long-form educational articles with a 2–3 week production cycle. Topics include engineering culture teardowns at specific companies (Uber, Stripe, Microsoft, Apple), technical debt trade-offs at high growth, and real-world AI tool adoption inside engineering teams.
Thursday The Pulse (formerly The Scoop): Timely industry news and exclusive stories. Gergely taps his industry network to get insider information from employees at major tech companies — some transmitted via self-destructing messages, anonymized before publication.
This "insider perspective" is his moat. He's not rewriting TechCrunch or The Verge headlines — he sources first-hand information directly from inside engineering teams. Forbes and the LA Times cite his exclusives.
His most popular article types include:
- Practical engineering topics (shipping processes, system migrations, incident reviews)
- Deep dives into specific companies' engineering cultures
- Career advice and Big Tech insider knowledge
- Salary data investigations
A 2024 reader survey (2,395 responses) showed: 85% are software engineers or engineering managers, 5% are product managers, 33% are in the US/Canada, 24% in Europe, 15% in India. A highly vertical professional readership — 95% hold a bachelor's degree or above.
He still writes code — building APIs, side projects like TechPays, a salary comparison tool — to make sure he doesn't become "a commentator who left the front lines years ago."
Business Model: Pure Subscriptions, Zero Ads
The Pragmatic Engineer's business model is radically simple and radically committed:
The only revenue source is reader-paid subscriptions.
- $15/month or $150/year
- Reduced rates for non-US/Western Europe regions and students
- Group subscription plans for teams
- All best articles stay free; paid subscribers get 4x more in-depth content weekly
What he deliberately does not do:
- Zero ads, zero sponsors: Even the podcast's sponsors have no editorial influence. His logic: if advertisers pay, you inevitably serve advertisers, and content direction gets distorted.
- Zero affiliate deals or paid placements
- Stopped venture investing: To eliminate conflicts of interest, he proactively quit startup investing. He quotes a VC partner: "Being independent is like being Switzerland — all parties trust you more."
- No public company stock holdings: Maintains a public ethics statement and discloses any residual interests.
Beyond subscription revenue, his other income streams include:
- Books: ~$100K in the first year; The Software Engineer's Guidebook has sold 40,000+ copies
- Job board: A hiring board operated through Pallet
Annual revenue of $1.5M+ — 100% from readers' wallets, not advertisers' budgets.
Growth Engine: Zero Marketing Spend
The Pragmatic Engineer has never spent a dollar on marketing. All growth is organic:
Free subscriber sources (ranked by contribution):
- Substack's recommendation / discovery features (~70%)
- His six-year-old engineering blog
- Twitter / X (grew from 27,000 to 115,000 followers)
- Google search
The key to paid conversion: Substack recommendations brought the most free subscribers, but his six-year blog was actually the highest-converting source for paid signups. This runs counter to the typical Substack experience, where Twitter usually drives the most paid conversions.
Hacker News sent massive traffic — 10+ front-page posts per year — but converted at just 1%.
His own summary of what drives growth: "Nothing beats interesting, in-depth writing."
The Team: From Solo to a Small Crew
The Pragmatic Engineer team is deliberately lean:
- Gergely Orosz (founder / full-time writer)
- Elin (tech industry researcher, joined ~2024; previously at Spotify and Google)
- Dominic (editor, former journalist with a decade of media experience)
He guards his time fiercely. As of early 2026, he publicly declines interviews, podcast guest appearances, mentoring, coffee chats, AMAs, and most collaboration invitations. Not out of arrogance — out of bandwidth. Between writing, the podcast, and books, time is the scarcest resource to protect.
Three Key Lessons
Write for yourself first, and the pressure disappears. His writing principle is to answer questions he's genuinely curious about, rather than chasing traffic. This mindset removes the anxiety of "what should I write that people will read" and paradoxically improves quality.
A niche audience can be plenty big. "Writing for software engineers" sounds small, but there are tens of millions of them worldwide, and they're willing to pay. When you serve a community that mainstream media ignores, scale follows. As he puts it: "The paid newsletter model is a viable model for publications which mainstream media would never fund."
Independence is the ultimate asset. Quitting investments, refusing ads, holding no stock — these decisions look like "leaving money on the table" in the short term. In the long term, they build trust. Once readers know you have no hidden conflicts of interest, every word you write carries more weight.
The Big Picture
Gergely Orosz's success rests on several hard-to-replicate foundations: twelve years of big tech experience across JP Morgan, Microsoft, and Uber (not an ordinary résumé), six years of blog writing (not a cold start), and Uber stock vested after the IPO as a financial cushion (no pressure to earn from day one).
But what's most worth studying is his business model choice: pure subscriptions, zero ads. In the newsletter world, conventional wisdom says "grow the audience first, then monetize with ads." Gergely did the exact opposite — charging readers from day one and letting content quality, not traffic volume, drive revenue.
This choice creates a structural advantage: his customers are his readers. There's no conflict of interest between advertisers and audience. He can write "what big companies don't want you to know" precisely because no big company is paying him ad money.
For anyone considering a knowledge-based newsletter, the biggest takeaway from this case is: six years of free writing isn't wasted — it's foundation. Without those 9,000 subscribers who already trusted him, nobody would have paid on Substack launch day. The moat doesn't start when you announce a paywall. It starts years before.
References
- The Pragmatic Engineer Newsletter
- More than one million readers (Gergely Orosz, milestone post)
- My learnings a year into writing a paid newsletter (Gergely Orosz, year-one retrospective)
- The Pragmatic Engineer in 2025 (annual review)
- Leaving big tech to build the #1 technology newsletter (Lenny's Podcast interview)
- How Gergely Orosz Built the #1 Technology Newsletter in 3 Years (Growth In Reverse analysis)
- Gergely Orosz — YesPress profile
- Becoming a Full-Time Creator as a Software Engineer (Gergely Orosz)
- The Software Engineer's Guidebook
Loading...