WhatsApp was, by almost any measure, the most efficiently run engineering organisation in tech history.
Jean Lee, engineer number 19 at WhatsApp and later an engineering manager at Meta, recently spoke on The Pragmatic Engineer podcast about what it was like to work inside the messaging giant before its $19 billion acquisition by Facebook in 2014. Her account offers a rare inside look at an engineering culture so stripped down it defies conventional wisdom — and still somehow worked.
“Even Meta, compared to other big tech — especially when I was at Meta — was pretty scrappy,” she said. “Not so much on writing documents. The “move fast and break things” model kind of allowed them to be a little bit more lean in terms of their process, at least while I was there. But WhatsApp was the ultimate lean company,” she added.
The numbers make the point sharper than any management philosophy could. By the time Facebook acquired WhatsApp, the app was serving 450 million monthly active users with fewer than 30 engineers — a ratio that has become something of a legend in engineering circles.
“By the time we were acquired, we only had 20-something engineers — under 30 people — serving 450 million monthly active users. So we didn’t have code reviews.”
What passed for a code review at WhatsApp was, by Lee’s account, a one-time event:
“The only time I got my code reviewed was the first time I made a commit. Brian asked to take a look at it before I committed it, and he asked me a bunch of questions, which I had to think through — kind of like a coding interview. But that was it,” she says.
After that first commit, engineers simply pushed their code to production on trust. There was no mandatory review gate. The informal substitute was the fact that, with only 30 people on the team, everyone could read each other’s commits — and often did, in WhatsApp group chats:
“After the first time, we didn’t really have a formal code review. But people read the Git commits because there’s only 30 engineers, so you can read other people’s code, and they would discuss it on the WhatsApp groups. So everyone was trusted — all engineers just pushed their code and merged it into production without a mandatory review. It was trusted that they would ask if they were unsure about something,” Lee says.
What Lee describes is less a gap in process and more a deliberate philosophy taken to its logical extreme. WhatsApp’s engineering culture was built on radical trust, radical smallness, and an almost monastic focus on doing one thing well. The team’s “just enough engineering” approach — using Erlang for concurrency, avoiding automation unless absolutely necessary, and keeping the product free of features that didn’t serve core messaging — meant there was simply less to go wrong, and fewer people to coordinate around fixing it when things did.
That trust-over-process model, however, had a ceiling. Facebook’s own engineering culture, while famously lean for a company its size, still required every code change to be reviewed before merging. Integrating WhatsApp’s cowboy-shipping culture into that structure was always going to be an adjustment — and the cultural friction didn’t stop at code reviews. Both founders eventually quit, reportedly over disagreements with Facebook on data privacy and advertising — the same principles of restraint and user focus that had made WhatsApp so operationally pure in the first place. Even WhatsApp’s early business head Neeraj Arora departed, leaving the original team essentially gone within four years of the acquisition.
It’s a pattern worth noting: the very things that made WhatsApp extraordinary at scale — extreme trust, minimal process, founder-led instinct — are precisely what made it difficult to absorb into a larger organisation. The question Lee’s account quietly raises is whether WhatsApp’s model was a blueprint, or simply a once-in-a-generation alignment of the right people, the right product, and the right moment.