Before AI Made Small Teams Cool: WhatsApp's Efficiency Playbook

Gergely Orosz chats with Jean Lee, who joined WhatsApp as its 19th engineer when it was still a small company with barely any formal processes. She played a key role in scaling it to hundreds of millions of users, experienced the $19B acquisition by Facebook, and later continued her career at Meta.

Here are the standout sound bytes and interesting facts from the talk:

Why Jean got into tech: "After talking to a lot of adults, I realized people who are in tech were the only ones who were really excited about their jobs. So in Silicon Valley, when you ask people like tell me about your work, people are often very hopeful for the future and very proud of what they're building. Compared to many other adults that I spoke with, they were not so encouraging. They're like, "Oh, don't become an architect. Don't become a designer.""

On process: "We didn't have code reviews... The only time I got my code reviewed was the first time I made a commit."

On product focus: "99% of the time he (WhatsApp co-founder Jan Koum) would say no... All the cool features were missing in my mind, but that was by design because we really wanted to prioritize again the quality of a grandma in a remote town being able to use our app."

On hiring speed: "What would it take for you to take the offer right now?" (Jan Koum closed the deal in person the day after the interview while another company took weeks)

On AI efficiency: "WhatsApp did not use AI, but we were efficient because we were small."

Tiny team, massive scale: WhatsApp had only ~30 engineers serving 450 million monthly active users at the time of the Facebook acquisition.

Multi-platform native: They built and maintained eight different native platforms simultaneously (iPhone, Android, Blackberry, Windows Phone, Nokia S40, S60, Symbian, Web) rather than using cross-platform frameworks to ensure lightweight performance on low-end devices.

Exotic backend: The server stack was built in Erlang, a language rarely used in startups but common in telecommunications (Ericsson), chosen specifically for its ability to handle massive concurrency and "maintain the engine of an airplane while it's flying 24/7."

Intentional growth suppression: The $1 annual fee wasn't just for revenue—it was a "growth discretion tactic" to slow user acquisition because the founders didn't want to raise too much money. The fee covered all costs (servers, salaries, SMS verification) and kept growth manageable without touching the $8M Sequoia funding.

No outages metric: The office had a physical countdown display tracking "X number of days since the last outage" as their primary metric, rather than user growth or media mentions.

Zero documentation for outages: There were no formal post-mortem documents or blameless culture processes; server issues were discussed in group chats and fixed through direct communication.

The acquisition moment: When Facebook bought WhatsApp for $19B, Jean was wearing noise-cancelling headphones at her desk and initially thought the company was going out of business when summoned to the meeting room. Zuckerberg walked in during the announcement.

Demographics: Despite being a "startup," the team was unusually experienced—Jean was engineer #19 at age ~27, but most of the other 15+ engineers were over 30, many hired from Yahoo.

Feature discipline: They worked on video calling for two years internally (using it with their own families) before shipping it, refusing to launch until 100% sure of quality.

Career reset at Meta: Despite being a founding engineer at WhatsApp, Jean was leveled as an L3 (junior engineer) at Facebook and had to "climb all over again," eventually becoming an engineering manager and opening the London office.

Visibility = Promotion: At Facebook, engineers who posted frequently about their work on internal Workplace groups got promoted more easily than those who didn't, as calibration meeting managers often didn't know the engineers personally and relied on visible impact.