AI Summary
5 min readJean Lee joined WhatsApp as its 19th engineer in 2012, when it had limited US recognition but strong traction in Europe and India. With a team that peaked at around 30 engineers before Facebook's $19 billion acquisition in 2014, WhatsApp served 450 million monthly active users across eight native platforms, emphasizing simplicity, reliability, and minimal processes.
Tech stack and platform decisions
WhatsApp built separate native clients for iOS (Objective-C), Android (Java), BlackBerry, Windows Phone, Nokia S40/S60 (Symbian/C++), KyOS, and a web client, avoiding cross-platform frameworks. The backend used Erlang for its concurrency and fault tolerance, likened to maintaining an airplane engine in flight, to handle constant global traffic peaks like New Year's messages. Founders prioritized lightweight apps for low-end devices, targeting "a grandma in a remote countryside," over unified development.
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
Never miss an episode of The Pragmatic Engineer
Get every new episode summarized in your inbox — free, ~5 minutes to read.
No spam. Unsubscribe anytime.
What you'll learn
- 1 `* (00:00) **Episode Intro and Jean's Early Career**`
- 2 `* (06:53) **Joining WhatsApp as Engineer #19**`
- 3 `* (13:05) **Unique Tech Stack and Multi-Platform Strategy**`
- 4 `* (18:20) **Ultra-Lean Engineering Processes**`
- 5 `* (23:17) **Monitoring Growth, Outages, and Success Factors**`
- 6 `* (28:06) **Facebook Acquisition Experience**`
- 7 `* (35:34) **Post-Acquisition Scaling and Business Model**`
+ Full timestamped outline available in the app
Show Notes
Brought to You By:
• Statsig — The unified platform for flags, analytics, experiments, and more.
• Sonar – The makers of SonarQube, the industry standard for automated code review
• WorkOS – Everything you need to make your app enterprise ready.
—
How did a tiny team of 30 engineers build the world-famous messaging app more than a decade ago, and what can dev teams learn from that feat today? Jean Lee was engineer #19 at WhatsApp, joining when the company was still small, with almost no formal processes. She helped it scale to hundreds of millions of users, went through the $19B acquisition by Facebook, and later worked at Meta.
In this episode of Pragmatic Engineer, I talk with Jean about what it was like building WhatsApp. When Facebook bought WhatsApp in 2014, only around 30 engineers supported hundreds of millions of users across eight platforms.
We discuss how the founders kept things simple, saying “no” to most feature requests for years. Jean explains why WhatsApp chose Erlang for the backend, why the team avoided cross-platform abstractions, and how charging users $1 per year paid everyone’s salaries, while keeping growth intentionally slow.
Jean also shares what the Facebook acquisition was like on the inside, how she dealt with sudden personal wealth, and what it was like transitioning from an IC to a manager at Facebook – including the reality of calibration meetings and performance reviews.
We also discuss how AI enables smaller engineering teams, and why WhatsApp’s experience suggests ownership and trust might matter more than tools.
—
Timestamps
(00:00) Intro
(01:39) Early years in tech
(06:18) Becoming engineer #19 at WhatsApp
(13:53) WhatsApp’s tech stack
(18:09) WhatsApp’s unique ways of working
(25:27) Countdown displays and outages
(27:07) Why WhatsApp won
(28:53) The Facebook acquisition
(33:13) Life after acquisition
(39:27) Working at Facebook in London
(44:07) Transitioning to management
(47:27) Performance reviews as a manager
(53:29) After Facebook
(58:53) AI’s impact on engineering
(1:02:34) Jean’s advice to new grads and startups
(1:06:45) Empowering employees
(1:08:17) Book recommendations
—
The Pragmatic Engineer deepdives relevant for this episode: