The Pragmatic Engineer - Building WhatsApp with Jean Lee

Episode Date: March 18, 2026

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:• How Meta built Threads• How Big Tech runs tech projects and the curious absence of Scrum• Performance calibrations at tech companies• Software engineers leading projects—Production and marketing by ⁠⁠⁠⁠⁠⁠⁠⁠https://penname.co/⁠⁠⁠⁠⁠⁠⁠⁠. For inquiries about sponsoring the podcast, email [e-mail]. Get full access to The Pragmatic Engineer at newsletter.pragmaticengineer.com/subscribe

Gene Lee was engineer number 19 at WhatsApp. She joined when hardly anyone in the US had heard of it, saw it grow to 450 million users, and was sitting at her desk with noise-canceling headphones on when news broke that Facebook bought them for $19 billion. In today's conversation, we discuss how WhatsApp built natively eight different platforms with a team of 30 engineers.

Why the founders said no to almost every feature request for years? How WhatsApp's team operated with no code reviews, no stand-ups, no sprint planning. and many more. If you want to understand how a tiny team with almost no process built, one of the most successful products in history, and what today's AI-native startups can still learn from them, this episode is for you. This episode is presented by Statsig,

the Unified Platform for Flags, Analytics Experiments, and more. Check out the show and we'll still learn more about them and our other season of sponsors, Sonar and WorkOS. Gene, welcome to the podcast. It is amazing to meet you. You have quite the story, early engineer at WarkOS. WhatsApp. But before we get into WhatsApp, how did you get into tech? I've always been a small town girl. My dad was an OG hipster. He was really into brewing beer. So he decided to get a PhD in

beer. In brewing. In brewing. So I moved to San Francisco in 1999, and that's when I got really exposed to all the different tech roles. Growing up, I didn't really even think about engineering as a job. Of course, I used computers and I thought it was really cool to be able to use Yahoo and search things online, but beyond that, my first exposure to Silicon Valley and tech came from living here. I got to meet a lot of people who work in tech. I dabbled around with coding when I was a teenager, but not too seriously. But I did think it was really cool that you can just write a few lines and it will just do things for you over and over and over. It was almost magical. I love the feeling of creating something that actually runs and debugging something and fixing it and

runs again. That was really joyous. And I didn't really get into like super into coding until I went to college. But one of the reasons why I decided I wanted to go into coding was I talked to different people. So I thought maybe I want to be a designer. Maybe I want to be an architect. Maybe I want to be an engineer. And I talked to different adults who work in the industry. After talking to a lot of adults, I realized people who were 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 encouraged. And they were like,

oh, don't become an architect. Don't become a designer. So that was one of the influences for me early on. I studied computer science at USC. And one of my first internships, actual like coding internships was at a small company. It was a three-person startup, started by one of the new grads from USC. And you'll probably understand it was a video sharing website. But it was not like YouTube, but there were so many versions of YouTube back in the days before what YouTube was dominant, right? So you probably remember dozens of these video sharing platforms.

They were everywhere. And one of the issues of having so many options is that you have to be, visiting 12 different sites to search for new things. So we had a website where you can aggregate all the different types of videos from different sources, which is actually kind of funny because lately I've been seeing a lot of AI platforms where you can just switch between the models, very similar to that. Yeah. How did you get into IBM? I really loved working for a small three-person startup because I got to work with engineers. We had engineers overseas in China, So I got to work with them.

I got to also do a little bit of coding myself, but I was coming up with the design docs, like the features list, and I was calling a lot of the shots. And I could also directly see the impact of my code immediately on the website. And I thought that type of ownership and speed and the visibility was really exciting, that I get to see the impact of my work immediately. But one thing I wish I had was a little bit more mentorship,

because we were all new grads and in college, I felt like we were just shooting things to see which sticks. And I thought maybe for my first job out of school, I would like a little bit more mentorship and training. And I started looking at more bigger companies, more traditional companies. And that's how I ended up at the time it was literally the biggest company in the U.S. At what point did you decide that you wanted to leave or try out something else?

Did you even decide or something just came up? One of the reasons why I wanted to go to a more, more traditional company with more structure was so that I could get more mentorship and training. And IBM was excellent for that. There were so many veterans, they had so much experience and they were willing to share with me because they were 20, 30 years ahead of me, right? But one thing I really missed was the small team environment. It was just so big.

There was a lot of meetings, a lot of process, and I missed seeing the impact of my work. I couldn't quite understand how my work was concerned. contributing to the overall company. So then I decided to take some time off and explore and have some fun. Yeah. And what time was this? What year was this? So I started working 2007 and I left by 2009, which was actually in retrospect,

I was really brave because it was in the midst of economic downturn. My thought process at the time was I was only 22 or 3 and I figured even if I take a year off, I can still catch up, which I did. And what happened from there? How did you eventually get to WhatsApp? That was years later, right? Yeah, so I took some time off to try out different, like, classes. I took a lot of classes.

I did a little bit of nowadays, you call it the gig work, but I did all kinds of work. So whatever I needed to, you know, make a living while taking all these classes and exploring and really finding out, what kind of environment or what kind of career do I, envision for myself. And after I took those time off, I decided that I want to go back to Silicon Valley, but this time I do want to work for a startup, but maybe with people who are a little bit more experienced, maybe not new grads, and maybe not a three-person startup, but a little bit more stable startup where I can possibly get both the autonomy and the impact of the work, but also a little

bit more mentoring because I was still in my 20s. Okay, so how did you find this startup? which of course happened to be WhatsApp. In 2012, WhatsApp was still early. They started in 2009, and they did still have a lot of users, but they're mostly in Europe and in India. They were not very known in America.

Were you a WhatsApp user back then? I was not, but my wife and her friends were, or back then my girlfriend. But some of my friends were using it on and off. It was kind of starting to be big in Europe. It wasn't as massive just yet. Exactly. I was lucky because I actually lived in New York for a little bit before moving here.

And a lot of people in New York were using it because it's an international hub. So I had used the product in the past and I saw the job posting on LinkedIn. And then you applied? What was the interview like? I don't think we did any lead code until way, way later, until when we started hiring interns and new grads. most of the interviews were talking about, I guess you can call it system design interviews. We would talk about how would you design this?

How would you design that? Like, tell me about your past experience building this product. And I recall talking to Jan about different messaging apps. And being Korean, I told him a lot about cacao talk and how it worked. Yeah, that was my interview. Just like that, you got an offer, I guess it's startup, right? Things move fast. I assume it must have been quick turnaround offer, and then you have to decide, right?

How did you decide that you're going to join this relatively unknown startup that is building some cool messaging that you kind of thought was cool? But it was much information about that. In fact, their glass door rating at the time, I remember, had one star. It had one review, one star someone saying, oh, I don't like working here or who knows if that was even a real employee. But that was their glass door. Oh, that's so interesting. I don't remember looking up. I must have looked up glass door.

But I was really lucky because I actually had another offer from a different company, but they were a little bit sore. One company was taking weeks to get in an offer letter. Another founder closed the deal in person the very next day. Speed matters and not just in hiring. This leads us nicely to our season sponsor, WorkOS. AI startups are reaching enterprise customers faster than ever, sometimes just months after launch.

And in the moment that happens, the requirements change. Customers wants SSO, SCIM, audit logs, and granular permissions before they'll deploy. Building that infrastructure yourself takes months. Workerwas gives you APIs to ship it in days. Authentication, SSO, SCIM, R-Back, audit logs, and more all designed to integrate directly into your product. Skip the rebuild. Keep shipping. Visit Workwise.com.

And now, let's get back to Gene and how the other company could not get her written offer as quickly as WhatsApp did. It was not a startup, and they said, oh, hey, like, you have my verbal offer. I am going to give you a written offer soon. But then it took them a while. And meanwhile, Yon called me a few days later after the interview. And he said, come into the office right like today or tomorrow. And then he asked me, what would it take for you to take the offer right now?

Love it. What did you say? I mean, I wasn't looking for that much. I mean, I was in my 20s. So I just told him, oh, like a few things I would like to have. then sure, I'll take the offer and I signed the offer the following day. And I did actually hear back from the other company. On the first day I started WhatsApp, they called me.

And I was like, oh, I just started a new company. That's it with startup. You move faster or otherwise, don't be surprised. So you were engineer or you were employee number 19 at WhatsApp, right? Was engineer number 19? Engineer number 19 at WhatsApp. And you told me something really interesting that you were the youngest person, And even though you were like by this time at your mid-20s or so.

I thought about that. So I recall there were about four of us under the age of 30. So I was not the young guest, but there were two people who were new grads. And then myself and one other person who were in our late 20s. But they are like 15 or so people above 30 at a start-up, which is kind of unheard. What do you think this was? This is so interesting. That is true.

Is it still rare nowadays? Like, good question. I think these days it might not be as rare, by the way. I think so because I think I read some kind of statistics from investors that actually when they look at the success rates of startups, they found that older founders tend to do better. Yeah. And what's that? I guess, you know, like Jan and Brian, they started this at like mid-30s or so after they

spend like more than a decade working at Yahoo and other places. Exactly. Yep. So I guess they must have been able to hire like their network whatnot. Yeah. The first 10 or so engineers, a lot of them came from Yahoo. Some came from Europe. You mentioned the story when Jan reached out to you.

Jan used to do that. He would just look up who is the expert in this field and reach out to people. And we had a lot of contractors in Europe. And then we had some like mostly from personal connection, like, from Stanford because Brian went to Stanford. And then we had some referrals from Sequoia because they invested in WhatsApp. That is fascinating because the way we connected actually is both of us know Jan. I mean, you've worked with him.

But I had an in-mail in my inbox from him, I think six months before you joined WhatsApp, where I got a message from him and saying, hey, I built a windows full-nap at the time together with my brother called Cocktailflow. And it was a beautiful Windows Funap. And it was labeled Career Opportunity. So what you're saying is there's a alternative timeline where if I said, like, yes, I'm interested, which in hindsight, if a founder reaches out, you probably should at least talk to them. Don't make the mistake that I did, which is just saying, like, I'm sorry, I'm busy. I might have been a contractor from Europe. So like, it sounds like that. That was a strategy. And that was a smart strategy. Yeah, we had many contractors in Europe and they were all very experienced people. They were basically managing themselves. We had people all over the world working with us. What was a tech stack like at WhatsApp?

Before Gene walks us to one of the most unusual text stacks in startup history, we're talking about eight platforms and a handful of engineers. Let's talk about keeping your code base healthy with our senior sponsor, Sonar. Sonar, the makers of Sonar Cube, helps you automate code review and verify the quality and security of your code across your entire stack so bugs don't make it to production, whether you've got one platform or eight. As agents take over the development process, Sonor has introduced the agent-centered development cycle framework, ACDC,

a new software-development methodology designed for the unique scale and speed of AI-generated code. It's a move towards a more intentional four-stage loop that gives agents the guardrails they actually need. The four phases being guide. First, agents need to understand the canvas on which they're being asked to create so that the output fits with what the developer and organization require. Generate. The L-LM-based tool generates the coded believes will achieve the desired outcome within the right context. Verify.

Next, the agent is deliberately required to check its work, ensuring that it actually achieves the desired outcomes and is reliable, maintainable, and secure. Solve. Finally, any issues identified are provided to a code repair agent to fix. To power this, Sonor has significantly strengthened this offering, introducing products and capabilities like Sonar Context Augumentation, Sonar Cube Agentic Analysis, Sonar Cube Architecture, and Sonar Cube Remediation Agent. Head to SonarSourSourcom

to learn more about the latest with Sonar and how it's empowering organizations to embrace the agentic era. And with this, let's get back to Gene and all the different tech stacks at WhatsApp had. We were actually pretty unique.

I don't think any startup ever really does this, but we had seven different stacks. We had, I actually looked it up because it's hard to count them all. We had, of course, everybody has iPhone and Android, but we also had BlackBerry and Windows phone, which is also pretty common, but we also had Nokia S40, S60. We had a thing called KaiOS for a while, but not for a long time, and we had the web client. So it's actually eight.

So you have, of course, you know, we know that iOS is Objective C, Android was Java back in a day. And then all of these, like the BlackBerry, the Nokia, they all had, I think Nokia was Symbian C++. They all had like their own different language. And then we've not talked about the back end, right? And the back end was Erlang. Erlang. Can you tell us about Erlang? Because this, that is one of the most exotic tech stack.

I've heard Erlang in telecommunications context at Erickson, again in Europe. It is popular with the telcos. But startup wise, I'm not sure I heard anyone else use Erlang. You might be right. They do have an Erlang conference. I think it's called Erling Factory. There's a really great talk. one of our engineers, Rick Reed, if you're interested in learning more about it.

We'll link it in the show notes below. I'm pretty sure it's still on YouTube. I haven't looked up recently. But he gave a really great talk about why they started working with Erling and it was a perfect choice. And he describes it as trying to maintain the engine of an airplane while is flying 24-7. Because if you imagine like WhatsApp is so international, we can't take a break, right? we have to continuously keep running and it's always busy. Someone's, it's 8 a.m. somewhere in the world, right?

And Erling was a really robust language that was really good at concurrences. And they stumbled upon it because they were using this other tool that happened to use Erling and decided this is the perfect language. And I guess at the core of WhatsApp, what was the core engineering challenge? Was it like so many messages being kind of coming in, needing to be seated out and send to different, you know, platforms. Yeah, that was one of the main challenges. Like, for example, for New Year's or Christmas,

because everyone's saying Happy New Year at the exact same moment, that was always our biggest challenges every year. And we would celebrate, hey, we didn't go down after New Year's. So the interesting thing about the seven different mobile platforms specifically is the conventional wisdom before and after has been like, look, if you want to support all those platforms, don't be silly. Do cross-platform, either build your own layer that is cross-platform or use, you know, there's all sorts of frameworks. Why did WhatsApp not do this? Do you remember the discussions of like why hire seven, including some really hard-to-hire people like for Nokia and Symbian?

And you mentioned the contractors in Europe, I mean, sounds a bit of a nightmare. Why? So Jan used to always say, I want a grandma in a remote countryside to be able to use our app. So what does that mean? They may not have the new assessment. iPhone, the shiniest phone with the biggest memory, right? In the countryside where a grandma is using it, you need the app to be lightweight, you need it to work on any kind of device, and you need the app to be simple. So those were our goals and priorities, and that's the thought process that went into our decision to build seven different platforms. And then inside WhatsApp, how did you get things done? Do you remember, like how a project got done or what?

was the concept of projects and kind of what engineering processes people might have followed, especially, you know, later you worked at meta compared to like how, you know, like more kind of, you know, standard startups work. Because I have a feeling WhatsApp was not exactly a standard startup, was it? Not really. Even meta compared to other big tag, especially when I was, at meta was pretty scrappy. Like not so much on writing documents, for example. 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 like the ultimate lean company. By the time we were acquired, we only had 20-something engineers, so under 30 people serving 450 million monthly active users. So we didn't have code reviews. The only time I got my code reviewed was the first time I 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 a lot, like a kind of like a coding interview. But that was it. After the first time, we didn't really have a formal code review. But, I mean, people read the Git commits because there's only 30 engineers that you can read other people's code and they

would discuss it on the WhatsApp groups. So everyone was trusted. All engineers, that they just push their code to, they merged it into production, pushed it to production without a manager review. And it was trusted that, you know, they would ask if they were unsure or something like that. Exactly. Okay. And it worked. It worked. What about the release process? Like if you tell me 450 million people, the first thing I'm going to say is like, okay, did you do canarying? Did you do feature flagging? Did you do experiments?

Did you do, you know, what kind of safety next did you have, right? We didn't do much of that. But we were really big on. dog fooding. So every time we were about to do a release, we would all internally use it ourselves. Jan, I think he might still say it on his LinkedIn. If you look up Yon, he said just quality engineer. His title, when he messaged me, because I didn't know who is CEO, it said Chief QA officer. Qua officer. And I didn't know what that meant. I thought it was some sort of weird joke from the outside. So now it makes sense. So he. He was going around.

He was making sure that it worked. He would try to break things as much as he can. And then if he finds a bug, he will really try to break it. And then he'll come to and say, hey, like, I found this bug. And you also said that Jan said no a lot. He did say no. Almost, as I recall, 99% of the time he would say no. Which I thought, again, as a young engineer, I was very confused because when you look at all these other apps,

There were like a dozen different messaging apps at the time. Like, WeChat is notorious for having everything, right? They have so many features. And I was so confused, like, why don't we build all these features? These are the newest, coolest things that we should have because at the time when I joined, we didn't have groups. We launched groups shortly after I joined. We didn't have voice calls, video calls. We didn't have any of these, no stories, you know.

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 at any given time. What's up held back features for years until they were absolutely sure about quality. They worked on video calling long before they shipped it. This leads us nicely to our presenting sponsor, Statsig. Today, you don't have to choose between speed and confidence. Statsi lets you see features behind flags, experimented at real users, and only roll out broadly when data shows that you're ready.

Here's what it looks like in practice. You ship a change behind a feature gate and you roll out gradually, say to 1% or 10% of users at first. You watch what happens. Not just did it crash, but what did it do to the metrics you care about? Conversion, retention, error rates, latency. If something looks off, you turn it off quickly. If it's trending the right way, you keep rolling it forward.

And the key is how the measurement is part of the workflow. You're not switching between three tools and trying to match up segments and dashboards after the fact. Feature flags, experiments, and analytics are in one place using the same underlying user assignments and data. This is why teams that companies like Notion, Brex, and Atlassian use Statsic. Statsic has a generous free tier to get started and pro-pricing for teams starts at $150 per month. To learn more and get a 30-day enterprise trial, go to Statsic.com slash pragmatic. With this, let's get back to how Gene and the WhatsApp team ship quality code with close to zero formal processes.

So it sounds like WhatsApp had very, very little process. This was very, very interesting because when I worked at Skype, at the same time as you joined WhatsApp and I also joined 2013, I joined Skype and you joined WhatsApp in 2012. Skype was very proud that they sent everyone to scrum training. I was a scrum master, other people with Scrum Master. So here we were with all the scrum, all the consultants, all the everything, and WhatsApp Al competed us with like a lot smaller team. And no scrum, no TDD, no agile.

1,000 engineers. Wow. That's a lot of people. Yep. I mean, when you have a thousand people, you kind of need these. Yeah. And in all fairness, like, for example, one thing that this whole scrum thing solved for a little bit is we had more than 100 teams and everyone was working on different things. And because of all this organization, we had a prioritized list of which teams are the most important and those got all the support.

So I guess one lesson might be that when you're just big, it's just big. It's just so much harder to move fast and a small team can outcompete you. Yeah, it just takes a long time even just to communicate with everyone. Being inside of WhatsApp, how did it feel to see this massive growth, not in your team size, but in the product usage, the people, the media, the feedback? We didn't have much media. Like, nobody knew about WhatsApp. One interesting thing you told me about the office is you had countdown displays.

Can you tell me about them? What were these? What did it display? Yeah. So you asked me a lot about metrics. And I think really the only metrics we track, like we didn't really pay too much attention to media or Skype's usage numbers or other messaging apps usage numbers. But the one metric we counted down was number of days, like X number of days since the last outage. Wow.

No pressure. Well, the numbers started to go up over time. Maybe that helped to have it visibly there. And when an outage happened, do you remember what happened after? Because these days in the tech industry, it's all about blameous post-mortems. If an outage happens, you know, we first mitigated, then we get together, then we write a document where we try really hard to not say who push caused this, but we come up with why the system is like this and so on. How did you go about like dealing with outages and also following up and ensuring that they don't, they won't happen again? So they, I know they did these discussions in the server group chat.

But I wasn't in the server group chat, so I can't really say for sure. I mean, for sure, we did not have documentation. It sounds like a lot of things are pretty simple. You talk with people. If you have a problem, you try to fix it. Don't over-document things for no reason. And it seemed to just work. And then have the key thing.

Like, I guess if you put out days since outage, people will know, like, okay, I should do what I can to not have an outage. And everybody knew exactly who was working on what. So we didn't have to blame any one, everyone just knew. WhatsApp was a massive success. What do you think made it so successful in the early years? And especially for the product itself, you know, you've seen cacao, you were aware of some of the competing messaging app. What did WhatsApp do that others did not?

There is a little bit of the networking effect. It's like the thing about messaging app is that if you use it, you need your friends to use it. And if your friends use it, you need to use it. And WhatsApp was the first to be on the market. That certainly helped. But there was a lot of competition. But again, I think a lot of other apps and messaging apps were chasing features, thinking about adding the shiny as newest features.

Whereas WhatsApp was very intentional, they actually worked on video calling for a very long time. We were probably working on it by the time you joined Skype when your founder said we have video. We were working on it, but we just didn't launch it until much later when we were actually like 100% sure about the quality of the feature.

So we often held onto features until we felt really sure before launching them. Interesting, because that is a little bit of a different than the conventional advice, which is if you're a startup, launch early, get feedback, improve it and iterated. It sounds like you did the opposite. It's like polish it,

and then do when you have full conviction. Yeah, we did use it internally. Internally, we used the voice and the video calling features with our families. So we had like a list, okay, like I have family members. These are all my parents and my brother and sister's numbers. Let's enable it for this beta group. And we used it for a very long time before we launched it with the public. Two years into working at WhatsApp in 2014, Facebook announces their biggest ever acquisition,

WhatsApp for $19 billion. What do you remember of this? time? How unexpected was it? And what kind of feelings, what kind of emotions went through you and the team around you? I actually journaled soon after the acquisition. So I looked up my journal around this time 2014. So it's been over 10 years. But I looked at my journal and I remember I was coding. I had this Spotify playlist with noise canceling headphones. I had this playlist called Let Me Think. This is the one I listened to when I want to focus. And again, Again, like we were in a pretty small office where I can see everything.

I was sitting in pretty central locations. So I could see people bustling and hustling, which was a little bit weird, but I tried to tune it out so I can code. But then from the side, I saw Niroj, who was the head of business at the time. He was just like waving his arms. He was a pretty tall guy so I could see it. He was like, like, stop, whatever you're working on right now. come into the we had one meeting room

come into the meeting room and I was like what is happening? We never have meetings so you didn't have meetings I mean we we have scheduled meetings every now and then but we rarely have

like we have never had unscheduled meetings and we rarely have meetings at all so I was confused and I dropped whatever I was working on and I went into the conference room And then they asked, like, turn off your phones. WhatsApp, turn off your phone.

That's kind of weird, right? And I thought, oh my gosh, what's happening? Like, did we go out of business? I was one thought. I thought, are we getting another raise of fun, like round of funding, like a new investor coming on board? It can't be that we sold the company because Jan used to say he will never sell the company. He used to actually say, selling your company is like, sold your baby.

And I remember we were waiting for quite a while because there was one person missing. Oh. And it turns out she was getting her eyebrows done. With her phone. It's like the way. Yeah, she came after the announcement, but the news was about to hit the public and they wanted to tell us before the news hit. And I noticed that Jan and Brian were making this face and I couldn't tell what it was. And then they made the announcement, WhatsApp has been acquired by Facebook for $19 billion.

And I realized, oh, that was them trying to hide their excitement. That was a face. Kind of smiley but not smiley. And that was a really exciting moment. And I kind of zoned out for a little bit because I was trying to remember, hey, like, how many shirts did? Like, again, it was my first startup ever. I didn't even negotiate my equity. and honestly I couldn't remember how much equity I had.

And I was trying to think, how much is a billion dollars? That seems like a lot of money. And how much is like 1% of 19 billion? I couldn't do the math. And I remember sitting there thinking, like trying to do the math. And then I thought, you know, no matter how the math works, I think one thing is clear, I'm going to be rich. And then Zuckerberg walked in. It's Zuckerberg walked in to the meeting.

Yeah. Wow. And then you had like a Q&A or something. We did. We did. Yeah. What kind of questions can you ask at this point? Or what kind of questions did people ask?

There was a mix of excitement and nervousness, right? Are we going to have to change everything? Like, because I think a lot of the engineers were more experienced. And they talked about how when Yahoo acquired companies, they changed 100% and lost the, what is it? The essence of the business. So there were a lot of questions around that. And Mark is actually very charismatic in person. And I thought he had great answers at the time.

He made sure everyone feels assured that nothing's going to change. And he will try to maintain it as much as possible. At least that was the messaging at the time. Clearly, this was an amazing exit. And to this date, it's not really been repeated. Maybe a few companies might have come close, but definitely not with such a small team. How did you and your colleagues deal with the fact that, wow,

you've just got an amazing financial exit? But I guess the company kind of continues inside of meta. Like it seems like, you know, two things at the same time. Like, okay, I have this like amazing financial exit, but there's also work. How do I balance? How did you balance? How do you decide what next? That's two folds.

So the finance side in terms of that. aspect. We actually got a lot of support. Our business person organized many meetings with like the accountants or even a financial advisor. We invited a professor who was the founder of Wealthfront and he gave us an hour of finance advice and he recommended books. I read the random walk down Wall Street, which is a great book. I recommend people read it if you're interested in financial management. And I read several other books to really educate myself to be able to manage this new wealth that I came across as a young 29-year-old.

Yeah. What changed the day-to-day once you officially became part of Facebook? Did you have to move offices? Did you get a new title added to like the meta org chart, that kind of stuff? The changes were very slow in the beginning. We didn't even move into the meta. where at the time it was called Facebook headquarters, Menlo Park, until at least a couple years after the acquisition.

So in the beginning, everything was same as usual. We still had our old office. Well, we did actually move to a little bit nicer office, a slightly bigger office. But other than that, it was business as usual. It was John and Brian. And we were hiring, but not, you know, at our similar, like, so steady pace.

And I think not until when we actually moved into the Facebook office, we started seeing a little bit more cultural influence and merging. Like we started using their, like, HR services, we're recruiting services and things like that. But it was a very gradual change over time. And then when WhatsApp became part of Facebook, as I understand it, It still is even to the date his own organization, like inside of Facebook, I understand

there's organizations like Messenger or like there's the Facebook group, et cetera. So like did WhatsApp rein his own kind of organization a little bit shielded from the rest of Facebook? We had our own area. Yeah. Or you're right. And in the beginning, we even had like our own chairs and our own whatever like walls and decorations that we were using. We brought them all over.

But over time, you know, there was. more and more mixing. After the acquisition, how did you start to hire more people? How did the projects change? Did things become more ambitious? Did you start to add more features? Because clearly, like you were about 30 of you. And then in a few years, there was hundreds of people working on WhatsApp. These days, it must be thousands of people. And like with those people, like, what new work came because again, originally WhatsApp was so minimalist, right? And kind of so scrappy. I guess we were choosing to be small, not that there was not enough work for us to do. So one of the reasons why we also tried to remain small was actually Brian and Jan did not want to raise too much money.

And it actually costs a lot of money to serve so many users. You have to pay for the servers. You have to pay for the SMS registration codes. Every year, Jan and Brian would do an all-hands meeting. So we did have meetings. Once a year? And Brian was very transparent. He will walk through our earnings and expenses.

Oh, interesting. Yeah, well, I had a lot of information around this. So the three main buckets of our spending was server cost, was about a third, and then about a third on salaries for the engineers, mostly. And then a third, the rest was for the SMS fee. When you try to register, you get that code, and we have to pay that 10 cents or whatever, how much it costs to send up international. messaging, those numbers, I mean, they add up when you have millions of people using your

app. So they actually didn't want to grow too fast because it gets very expensive. WhatsApp was free for the first year. And then after that, WhatsApp was charging $1 for every year. But they were only using it in certain countries really to suppress growth because they don't want to grow too fast. Fascinating. Because I remember in Europe and In the U.S., there was this $1 cost, which I think people were like, yeah, whatever. I don't think we realized that this was a growth suppression tactic. Fascinating. And then when Facebook acquired, I guess they got rid of it.

Yeah, Facebook said we don't need the dollar. We can grow as much as we can because they had the funding for it. And then growth just, did it speed up? Do you remember? It did, yeah. Incredible to you sale. Using payment to slow down growth. The lesser known detail about the $1 is that that, that,

$1 was enough to pay for all of these. The server cost the salaries and the SMS code. Per per year. So you were roughly break even. Break even. We did have funding from Sequoia, but we never touched that money. Incredible.

Yeah. Brian explained it as how his dad was a business owner, and they would wake up in the middle of the night, worried, what if I cannot pay the salaries for the employees tomorrow? And he explained that he, He took the funding from Sequoia as like a backup. And I think it was $8 million of funding, if I recalled, if I looked at that backup. Yeah.

So we never touched that money. The $1 paid for everything. And it's slowed down growth enough to be manageable. Yeah. When you joined Facebook, what title did you get and how did your career change? So the thing about Facebook is that everyone's actually software engineer. I'm pretty sure they still don't have titles. They don't have titles, but they have levels.

What was leveled did you come in at? So being one of the five youngest people, I got leveled as a junior engineer. No, you did not. Yeah. L3 or L4? L3, yeah. No. I had to like climb all over again.

Oh my gosh. That must have been a bit awkward. I was not too happy about it, but what's the alternative? Do I want to give up best thing the rest of the shares? And eventually I got promoted. But it was within WhatsApp. So you got promoted. pretty quickly. How many times did you get promoted there? A few times. I mean, I eventually

became an engineering manager. And then as you became an engineering manager, at some point, you decided to help and start a new office in London. How did that decision come and how did you go about it? That was actually an ask from Facebook headquarters. So they said, hey, like, we're actually running out of space in Manlo Park and also WhatsApp is so big in Europe. So why not have a presence there. It'll be much easier to hire engineers because everybody actually uses WhatsApp. So let's start a new office there. And we didn't have that many engineering managers, right? I was very lucky because I got asked to go along with a couple other engineering managers. And all three of us actually became managers around the same time. We actually even trained together. We were relatively

new managers when we got asked to go there. But I think we were the only ones who could go because, you know, people have children and they have to think about school and they couldn't go. I remember one, the director that I was working with, he couldn't go because his wife says she doesn't want to move with the children. It makes perfect sense. You arrived in London. You landed with these two or three other engineering managers. How did you start to grow the office?

From a practical perspective, what can I imagine? Like, you know, like how did you start hiring or leasing space or what are the other things that you had to do that, you know, like, we're maybe a little bit of, unexpected for you. A lot of the logistical part was taken care of for us because Facebook already had an office there. So we kind of moved in. We got our own section. And it wasn't big because at the time, again, we had a lot of contractors in Europe. So we had one contractor already in England. So we turned, we converted them full time. And then we had one in Scotland. We also converted him full time. So he would commute from Scotland every now and then. So we had two engineers.

plus three managers and we started hiring there. I think the hiring part was something that took longer to set up. We worked very closely with the Facebook hiring team, which was really great that we already had people who were familiar with the local recruiting logistics there. So one thing we focused on a lot was really letting engineers know, hey, WhatsApp is hiring in Europe now? Come apply because we were hiring from all over Europe and also a lot

from India. Do you feel it was easier to hire for WhatsApp in Europe just because people knew about it? Do you get more excitement, more applicants? 100%. You wouldn't believe. Like, I used to do a lot of university recruiting. And when I used to go to Stanford, maybe 2013, like, anytime before the acquisition, I would say, hey, like, people will come up to the booth and I would say, hey, do you want to

give me your resume? And they would be like, tell me about your company first. Because they have never heard of WhatsApp. What is this company? I'm not even going to give you my resume. I'm not going to give you my resume. I have only 20 of these. Exactly.

Versus in Europe, people were actually excited to talk to us. What were the good and bad things of working in what basically is a remote office? Like, yes, London was a big office, but H.Q was in California, Menlo Park. That's eight hours of time zone difference, a lot less overlap. There's probably some good things about this and downside. It helped because the three of us were from Menlo Park and we actually had great relationships with other teams and other engineers and other managers. And we also traveled back to Menlo Park every quarter.

And then we had the leadership from Menlo Park also travel to London almost every quarter. So there was a lot of back and forth to really strengthen the relationship in the beginning. Your growth went to like being, I guess, the one of the best. the most junior people in WhatsApp, which is crazy to say because you were experienced as well, but then you were also L3 and Facebook, which I still cannot believe. But you went and became a manager. What pushed you to actually say, I actually want to try to manage people? I actually never asked for it myself. Someone on my team begged my manager, hey, can I please report to Jean? And that's how I became a manager. Wow. Okay. What did you think this person saw in

you, they wanted to report you when you were not a manager. I was the tech lead, so I was already managing the project. So it was sort of a natural transition for me. And when you become a manager, what parts of the job came naturally to you and what parts were hard that you had to learn or get mentorship for? You know, I started reading books. I love reading books. So whenever there's a new challenge, I like to read, learn, and research, there actually at the time weren't a lot of courses on how to become a manager. and not a lot of books. Like I still don't think

there are too many books about how to become a manager. There's a little bit more now. There's like three or four good ones, but they all came out after like 2015 or 2016. Yeah, the resources were pretty limited. But I did what I can to read as much as I can about leadership and I think I read actually a lot

about communication and psychology. There's several books. Like I love the book surrounded by idiots. read that one. It talks about the disc personality, the different types of personalities. And I try to really understand, like, what motivates people, how do you communicate with people in a way that makes sense to the other person? And also, I reflected personally, like, what were some good managers and bad manager in my experience? Because you hear the saying that people don't leave companies, they leave managers, right? Your manager can really break or make your career.

They can make your life miserable if you're matched with someone you don't vibe with. What are the traits that you found, as you recalled, what were things you said, like, I think this makes a good manager, I want to do more of that. And I think these were terrible managers or bad managers, and I want to avoid doing that. Do you remember some things that stuck out? Yeah, I try to really understand each individual person. So, for example, like one person that I had on my team really loves going deep into problems or debugging and finding out how to improve things, right?

Whereas another person really loves building new features. And you cannot ask this person who loves to build new features to go debug 10 bugs, that that person will go nuts, right? And then like one person who was really good at building new features was not so great at mentoring new colleagues. So I try to really look for their strengths. And of course, you also want to set them up for challenges. they can learn as well, but you want to balance them out.

So I try to really understand by asking them a lot of questions to understand, like, how do they want to be challenged? When do they feel excited about their work? Or what are the things that they're really good at? What are the things they want to improve on? So I spent a lot of time really talking to them. As a manager, you were part of calibration meetings, right? Now that you're not at, not at WhatsApp, not at meta, can we talk honestly about what are those meetings? like, you know, what are maybe the good things about them? How can you prepare? And what's the

kind of reality? Because I feel outside of a small group of managers who are in there, it's not many people know, like, how these things go. So people, number one biggest mistake people make is they think your manager is the one giving you a promotion or a salary boost. Like, as a manager, middle manager, right? Like, I have no authority to give you a promotion. You have no budget. Typically, directors have a discretionary budget sometimes to be able to give a reward, but not even promotions. They even they cannot give, right? Right. And the bonuses are tied to your performance review, right? So at meta, for every level, there's exact percentages lined up by the confit team. Like, I have no control over it. The only control I have is, I think of myself as

the lawyer representing my clients. Wow. Yeah. I'm making a case for them. why they deserve to get a certain performance review rating or a promotion. And obviously, like, I want my clients to do well. I want my team to get, you know, the recognition that they deserve because I know they worked hard. But it's not up to me. All the other managers also have to agree. That is the nature of performance reviews. And being specific, on a performance review, like, who were the people that you

you saw the engineers who got these high performance reviews from this committee? What kind of taxes did you see? What were there things were like, well, some managers kind of like, you know, politics where they kind of like they're calling in favors for each other and pushing someone up? Or was it mostly meritocracy, meaning this engineer was actually doing great work that a lot of managers saw and they just naturally agreed that, you know, this person who's on, on jeans team is actually they should be above my great person and I kind of agree with that. Because there's bucketing, right?

Lesbuker is bucketing. You're going to have buckets and you need to put like, I don't know, X people in the top bucket, middle bucket, bottom bucket and so on. Yeah. When I was coaching engineers, I learned that different companies have different ways of self-promotion. So like, for example, I heard some companies use emails. Like they send mass emails every time they do a new release or launch. Or like at WhatsApp, we use Wi-Fi.

we use WhatsApp groups for everything. But at Facebook, they used Facebook workplace, which is like Facebook groups, where you have a group for team, your org, and everything has a different group. And I noticed, as I'm representing my clients during performance reviews, the people who post the most often, who have the most visibility, usually get the easiest consensus. because it's just like all very natural. Like if I have no clue what you worked on and your manager tells me you're great, maybe, but how would I know?

I don't know anything about you. So I'm less likely to be inclined to agree with your manager. Maybe your manager's right, but I don't know. Whereas if you have been actively posting and telling me indirectly or directly what type of work you have done and what type of impact that has made and what are the the lessons that you learned and what type of people you work with, then I already know, oh, okay, like when your manager tells me you're ready, then I say, yeah. And then in terms of what for this, this was actually like it's more than just groups. It was like this Facebook feed where, you know,

like it's a bit like LinkedIn, right, just to make it. So you see these posts come across the company and sometimes you'll hit like. And what you're saying is like, if you've seen this post from this engineer on some other team saying, oh, we've launched this feature, here's an interesting thing. We've learned that we're using for Facebook and I hit like. like I now remember it. And then when performance review comes like, oh, I remember that person. They wrote that. Exactly.

And I might even have some questions, right? Maybe like if your manager tells me, I might be like, well, what about this? What about that? But if you make a post, I can just ask you directly through the comments, right? There's a lot of engagement happening in the comments. I might ask, have you thought about this other thing? Have you thought about this thing? And you might give me answers.

And I think, oh, okay, yeah, he's thought about it. He's really good. It's amusing because it sounds like simplifying a little bit. But to be successful at Facebook, you need to also be good inside of the Facebook app. And do interesting work and not hide it, actually make it visible. That's interesting. Now, stepping up a step back, and you were a manager at Facebook, you saw a lot of engineers. Outside of the performance review and people posting about it, what traits that the best engineers that you remember share?

Like, what made them so good? I struggle with this question a little bit because there's a difference between, like how do you measure skill? How do you measure what a good engineer is? Is a good engineer someone who can bang out new features? Is a good engineer someone who can design a complicated system? Is a good engineer someone who can communicate all of this and explain it to non-technical people? I struggle a little bit with the definition of a good engineer because I can have a definition of a good engineer,

but it may be different for every culture, different company might have different definitions. A good one. At Facebook, what was the definition? I remember that a lot of it went down to just a very simple characteristic impact, right? Definitely. And I think the way, like there are many ways to measure impact. And definitely at Facebook, their way of measuring impact was through these posts.

If I know about your work and you tell me you have impact and I agree, that's impact. So going back to when you were in London office and start to go, at what point did the London office start to feel less of a startup, a scrappy startup, and more of a big tech? I remember her time. After about a year and a half or so, I realized I don't know who that person is or I don't know their name. That was a turning point.

And at what point did you actually start to think of leaving Facebook? I think I really enjoyed the internet. environment. So I appreciate being able to, like at WhatsApp with 30 engineers, I knew everyone's names. I knew where everybody lived. I knew their spouses and their children and their dogs' names, right? I really like that type of intimate environment. We still hang out. We have a pretty strong bond. And I feel like when I even, when I don't even know this person's name, I just feel less connected. Now. So was this the point? where you decided that maybe it's time for you to leave and do something else.

Oh, so, okay, I was in London on a contract. So I had a two-year contract. They said, hey, like, go start this office. And then once the contract ended, I had the option to either stay there to continue working in the London office or I could come back to Middle Park. But then at that point, I had been working there for eight years. And honestly, I think I was pretty burned out. I'm the type of personality who likes to get like A plus on everything I do every single time. So it was pretty tiring after eight years.

I needed a break. Yeah. And when you left WhatsApp, what did you decide to do? I say WhatsApp, but it was Facebook at that point. Yeah. I actually, because I know my personality, I don't take breaks. So I actually had a goal. It's simple, but I.

that I will do nothing for the next six months. I'm going to challenge myself to do nothing for six months. Did you manage? I did it. I did it. I did read a lot. I exercised. I went on long walks.

I did multiple meditation retreats. But that was my challenge to myself to not work for six months. So after six months of successfully doing nothing, after setting yourself that goal, what did you do to figure out what next? So initially, I thought maybe I thought maybe I, I want to go start a new company or join another startup because I like working. I love building things. So I decided, okay, I'm going to start talking to other founders or people who are hiring or people who are looking to start a new company.

So I actually talked to 100 founders. I have a spreadsheet. Wow. To really see, like, is there any interesting opportunities that I might feel passionate about joining or building? And then after talking to 100 startups, I realized I wasn't really passionate. about joining any of them. And I thought, like, what would I feel more passionate about?

And what was the thing that I liked the most about working at WhatsApp for the past eight years? And I realized I actually really liked being a manager because I felt like I was creating a culture of, like, support so that other people can really be learning and thriving and, you know, be able to do things freely without people breathing down your neck. There are many things that make for a happy career, but I found it really gratifying to be able to find that from each person and really try to help them out and create whatever that is. It might be different for different people and trying to unblock them so they can really flourish. And I thought, well, if that's what I really want to do, I don't have to start a new company. I'll just do that part. But I started exploring, like mentoring people. I did a little bit of coaching.

I don't do anymore. and making videos on YouTube, writing all of that to see, how would I find the best way to support other people? And on YouTube and on LinkedIn, you have been sharing a lot of your learnings, your observations. What pushed you to just start sharing way more than before? I think you started to do this publicly after you left Facebook. I was actually writing a blog about this.

So I actually just hit 100K subscribers on YouTube, like last week, thank you. And I was reflecting, I almost gave up doing YouTube because I was really not comfortable being seen in public. And I've been thinking a lot about this. Like, my grandma's from North Korea. She escaped during the war.

And in that culture, like you do not speak publicly. You don't want to be seen because it's dangerous. And I think there's just, generations of that still kind of installed in me. The fear of speaking up is real. I felt really uncomfortable. So I almost stopped doing YouTube. Once one of my videos went viral from early on, and I feel really uncomfortable. But luckily, I was talking to a mentor of mine and she said, hey, it's okay to do something that you enjoy doing. Just give it a shot. So then I stuck with it. I'm so glad I did. Speaking of the thing that is happening, of course, right now, AI.

You spoke about this on your YouTube channel as well. But from your vantage point, how is AI changing, how engineers work, how managers work? I do find it really interesting how with AI we're seeing smaller teams emerge. I know that a lot of teams are saying, well, we're small because of AI. But I wonder if it's independent from AI, when you're small, you're just more efficient. because WhatsApp did not use AI, but we were efficient because we were small. And I almost feel that even today,

I cannot really point to too many teams that are as small as WhatsApp and have that kind of impact. And traffic might come to mind, but I think even they're bigger. So I wonder if there is a, maybe just going back to basics with all of us. maybe AI allows to do the way most companies would have wished they operated. Yeah, and I think there's also a shift in the mindset.

Like I remember back in the days, people, when you go to networking events, people would brag about, oh, like, we've hired like a thousand new engineers or were growing X times bigger. And that was like a point of brag. And investors also thought that was a good thing. You need to grow. You need to hire more engineer. That was a sign of healthy engineers. environment. Whereas nowadays, investors actually think smaller is better, right? Like,

they don't necessarily push you to hire more people. And I think as a byproduct of hiring less people and staying lean, they have found this new, found efficiency and they happen to equate it with AI. Well, the AI, I think, it's clear it makes engineers a lot more efficient. Well, we think it makes them efficient because it can generate a lot of code. You can work on more things parallel is happening with agents. How are you seeing the role of software engineers change and also the rule of engineering managers? Yeah, I mean, I love AI tools. I use it every day.

As a thought partner, I often ask chatypiti, hey, like be my executive coach or be a hardware trained futurist and help me find the next trends. Or, you know, there are various ways of really using AI to its full potential. I feel like engineering management is less affected by AI because it requires a lot of like people to people like asking questions and learning about your engineers. AI can maybe help you with that, but I don't see AI replacing that part. But again, because the teams are much smaller, if you were the type of engineering manager who was doing a lot of these like OKR and process and writing documentation, a lot of that part is going to be gone. And I'm kind of glad it will be going on because I don't think it's really necessary. Yeah, for example, a lot of performance management of gathering the impact.

It can probably be done by asking agents to gather all these things. I remember as an engineer manager I used to go through gathering all the work that my engineers have done. So on the calibration meeting, I could fairly represent them. And then it turns out that the managers who showed up without doing that, I had an advantage. But that was not fair for the engineers, by the way, right? Maybe I will get rid of this advantage. Yeah, AI will do a lot of the grunt work, more tedious work that maybe engineering managers or even software engineers had to do manually back in the days. Like, we had an engineer who was just there to add comments.

I think that is something AI can do really well. If you had to give career advice to a new grad who says, I would like to build a durable career in software engineering in this kind of AI native world, what would you suggest they focus on? I say foundations. You know, tools come and go, languages come and go, but foundations don't go anywhere. We mentioned at WhatsApp. WhatsApp was very small, very efficient. What do you think today's AI or AI native startups could still learn from WhatsApp that made WhatsApp successful and it could probably help them as well?

I think of AI. So we went through several trends. Like when I first got my first internship ever, it was very, video sharing website. And I've seen how there were dozens of video sharing websites and how the ecosystem changed over time. And then I saw with WhatsApp, there were dozens of other messaging app competitors and how that kind of settled down over time. I think we're living through something similar. There are so many new AI startups and new tools and so easy to get distracted by all the different options. And it can feel quite overwhelming. There are too many options. And you can feel

the decision paralysis, but really, again, go back to the core foundation. Think about, like, if you're a builder, think about what you're building, why you're building. If you're learning, think about why you're learning, what you want to learn. And if you have clear goals of where you want to go, it will really ground you because otherwise you're just going to be all over the place. And you might work really hard and end up nowhere. Do I understand correctly that you're saying, what's out was successful? Because the goal was clear, Jan said no, the distractions and all the, all the

ideas but was very clearly marching, whereas all the other competitors, even, all the messaging apps, they got distracted building, oh, let's do like, oh, this cool video feature. Let's do stories. Let's do all of these things. They saw traction and they did a lot of these things. But WhatsApp was very good at doing the core thing well and then slowly adding things that were a value at. Is that a fair summary? Yeah. And also I noticed this when I started advising and coaching startup founders as well. And also for any engineers who want to join new startups, this is a great way to evaluate new founders. Like some founders, if you're the opposite of yon saying no to things, I call it removing distractions, right? You're prioritizing ruthlessly.

If you're the opposite of that, imagine what type of startup you end up. You say yes to everything. Maybe it might feel really nice as a 20-something year old if I were to go back in time. and I go to the founder with all my great ideas and he says, that's a great idea, Gene, let's build it. But imagine, like, he said that to every single idea that I had. The company will be all over the place. In terms of the long-term growth, it's not a very ideal situation.

Looking back, what are some kind of like pre-AI or not as modern practices that you did at WhatsApp that were really good, that today's very modern AI native teams or whoever could benefit from? Yeah, of several things come. to my mind, I think one of it is by having lean teams, you get several benefits. You get to remove a lot of the distractions and process. And through that, you get two really incredible benefits, which is ownership and the really like the freedom to build things, right?

Because Jan was always, like, Jan and Brian were always very specific about what we're building. But how we're building it was up to debate, right? I mentioned earlier that the only time we did an actual code review was the first time I made my Git commit, Brian reviewed my code and asked me a bunch of questions. So Jan and Brian were both like so technically adapt. They were really excellent at doing this. They would ask, we're trying to achieve this. Like, what is the problem here? Or what is the best way to solve this issue? What are like different ways we can approaches. Tell me. So do I understand correctly that, of course, the small teams help with a lot of things, but then having the founders push people they hire especially early on, they almost

like push them to excellence, right? Is it fair to say that by Brian doing that super detailed code review with you the first time, it just ups your game and later he didn't even have to do anything, right? Yeah. And there's like multifold, right? Like one is to really challenge me to think critically. And then I took, I learned a lot just from that conversation. And then also, like from then on, he never checked my code again. So I know I am responsible, right? And I do believe when you give responsibilities to people, people will step up. I mean, not everyone, but most people will. But I think this might be a bit underrated. I wonder if we've had a little bit of two over-babying of engineers.

I remember for a long time, there was a talk in the, you know, in the past five to 10 years, and the, as engineering manager is like, well, I have a new grad. It will take the months to onboard.

I need to sign them a mentor for at least six months, maybe even a year. And were we over-babying these very capable adults? You know, they're adults, right? Even if, even if they're 18,

but they're typically 20-something because they came out of college. And they're hungry and they're ambitious. And maybe we don't need to do that. much of it, always. Yeah, I think as long as you hire smart people, it's kind of like a mold, right? If you make a mold too small, that's only the limit of how far they will grow. Yeah, if the mold is too small, you have to throw away a lot of things that could have made excellent material.

Finally, you're a reader. What are some books that you would recommend for software engineers or people wanted to grow professionally or in a personal sense? I love reading books. I did, so while I challenged myself to do nothing, I actually read. I actually took a year, but I did read 100 books during that time. That was my doing nothing. Anyways, it kind of depends on what your goals are, but you gave me some specific things like for your career. I think for me, what was really helpful was what color is your parachute that helped me really understand my strengths and my goals and priorities in my career and life. I mentioned the book, Surrounded by Idiots. I know the title's kind of funny, but it's an excellent book if you want to learn more about how to really communicate and work with different people. If you want to understand finance, I mentioned earlier, the random walk down Wall Street. It's a great book for understanding how to manage your money.

Yeah, I would recommend those books to start with. And any fiction books? Hunger Games was one of my favorite books. I read the whole series. I read it as well, and I almost like the movies as well, but I love the books. Yeah, yeah. I love the story of like this woman overcoming her challenges. And everyone else and winning in the end. Several times.

Gene, thank you so much. Yeah, thank you. Thank you for having me on the channel. This is a great conversation. I hope you enjoyed this rare conversation with Gene. One thing that stuck with me was Gene's point about why WhatsApp had almost no process and why it worked. Processes exists for audits, for accountability, and for tracking who did what. But when you have 30 people and everyone can see what everyone else is working on, you don't really need a paper trail. You just walk over and talk.

This is a good reminder that most processes exist to solve problems that are created by scale and not by the work itself. I also found the Skype contrast really surprising. A thousand engineers scrum certifications, two-week sprints, and a dedicated scrum master for every team, I was one of them at Skype, and WhatsApp with 30 people and zero-former methodology was shipping faster and growing faster on every method. that mattered. This is a much needed reminder that organizational discipline and actual shipping speed are just not the same thing. And I was in the middle of this at Skype and Gene was at the middle of it in WhatsApp. Finally, it was interesting as a former manager to hear how Jean described performance reviews as a manager herself. She described herself as a lawyer representing her clients. As in, she doesn't control the promotion, she just makes the case. And the engineers who had the easiest time getting promoted were not necessarily the best engineers. They were the ones who made. made their work visible. They posted about their launches in the internal Facebook workplace. They engaged in comments, answer questions publicly.

And the managers in those calibration rooms are making decisions about people that they might have never worked with directly. So visibility is not just vanity. It's how the system inside larger companies actually works. This is an uncomfortable truth, but I think every engineer at a big company needs to hear it. If you've enjoyed this podcast, please do subscribe on your favorite podcast platform and on YouTube. A special thank you if you also leave a rating on the show. Thanks and see you in the next one.