On April 2, 2022, a newsletter arrived in inboxes that nobody asked for - and 1 million engineers subscribed anyway. ByteByteGo didn't grow like a startup. It grew like a textbook people actually wanted to read.

Alex Xu drew the first diagram. The diagram had too many arrows. Engineers forwarded it to their colleagues. Their colleagues subscribed. The colleagues forwarded it to their teams. Now the whiteboard is just a formality - everyone's already seen the ByteByteGo version.

The system-design-101 GitHub repo launched with no fanfare and 18,000 stars in four days. GitHub's trending page hadn't seen growth like that since an open-source AI model dropped. Alex and Sahn weren't building a startup. They were doing something stranger: explaining the internet to people who built it.

The Two-Person Curriculum

ByteByteGo is split down the middle in a way most co-founder partnerships never are. Alex owns the newsletter, the books, the Twitter/X presence - the written word. Sahn owns YouTube, the production, the visual storytelling at scale. Neither steps into the other's domain. The result is a platform that feels simultaneously like a newspaper and a documentary series.

Alex Xu came out of Carnegie Mellon with an M.S. in Computer Science and proceeded to spend a decade building at scale - Oracle, then Zynga, then Apple, then Twitter. Not a startup hop. A methodical climb through systems that break in ways only production can teach. When he sat down to write System Design Interview - An Insider's Guide in 2020, he wasn't building a personal brand. He was filling a gap that no textbook had touched: the actual interview question, the actual approach, 188 diagrams, and nothing padded.

"Writing has always been something I love, and creating ByteByteGo felt like the perfect way to combine that passion with our professional interests."
- Alex Xu

Vol. 1 hit Amazon #1. It was translated into six languages. Somewhere between the Portuguese and Korean editions, Alex started a newsletter - and called Sahn Lam.

The Engineer You Need

Sahn Lam is harder to profile than Alex because Sahn's career reads less like a ladder and more like a map of everywhere distributed systems get weird. NetApp gave him enterprise storage management at the lowest level of the stack. Zynga gave him eight years of social gaming scale - and a CTO who sent Sahn toward whatever fire was burning hottest across the entire organization. Ubiquity6 gave him AR at scale. Discord acquired Ubiquity6 and gave him massively multiplayer networking plus computer vision in production.

When Ubiquity6 wrote a hiring post announcing Sahn's arrival, they described him as the engineering equivalent of "Bazooka-meets-Katana-meets-Yondu's crazy whistling arrow thing." Twenty-five years in, across five companies, never a generalist - always the specialist they didn't know they needed. He's the engineer who shows up when the architecture has run out of obvious answers.

"The best way to understand a complex system is to draw it."

ByteByteGo - the philosophy in six words

The Diagram Economy

There's a specific type of content that circulates in Slack channels at 9am on a Monday before a system design interview. A clean diagram. White background. Clear boxes. Arrows that don't cross when they don't need to. A title like "How Stripe Processes Payments." You've seen it. You've probably saved it. It came from ByteByteGo.

Alex's signature aesthetic - high information density, no visual noise, the diagram as first-class deliverable - has become so recognizable that engineers can spot a ByteByteGo diagram in a slide deck without seeing the logo. It's a visual language. A system design shorthand. The infographic evolved into a curriculum.

System design was always taught like a secret. You either knew someone at FAANG who walked you through it, or you guessed. ByteByteGo ended the guessing. Now the secret is just a Substack subscription.

One Million and a Model

The newsletter launched April 2022 on Substack. By under two years in, ByteByteGo had cleared 334,000 subscribers. By 2023, they passed 500,000. Then 1 million - in just over two years from launch. The growth curve doesn't flatten. The content never got worse. There are no viral stunts in the history, no influencer collabs, no growth hacks. Just a Saturday issue that arrives with a diagram that makes something complicated feel obvious in retrospect.

The business model behind ByteByteGo is unusually direct for a creator business. Free subscribers get the Saturday newsletter. Paid subscribers get Wednesday deep-dives, topic input access, a Discord community, and mock interview pairing. The books are sold through their platform at bytebytego.com alongside digital courses. The YouTube channel - where Sahn does most of his work - drives traffic back to the platform from engineers who want the visual first, the text second.

At $199/year, the subscription competes against a weekend of Leetcode frustration. The conversion math is not subtle.

The Book Shelf Nobody Reads - Except Everyone Does

Technical interview prep books have a reputation for sitting on desks unread until the night before the phone screen. The ByteByteGo books break that pattern. Vol. 1 has 188 diagrams across its 16 questions. Vol. 2 has 300+. The Machine Learning System Design Interview introduced a 7-step framework. The Generative AI System Design Interview - published November 2024, co-authored with Ali Aminian and Hao Sheng - brought the same treatment to LLM architectures, RAG systems, and GenAI pipelines.

Four books. Four areas where engineers interview poorly not from lack of intelligence but from lack of a framework. The ByteByteGo framework is almost stubbornly practical: what's the question? what's the scope? what's the system? draw it. trade-offs? capacity? done.

Why It Works

The secret isn't the diagrams. Plenty of technical blogs have diagrams. The secret is that Alex and Sahn are practitioners first, educators second. Alex built at Twitter. Sahn built at Discord. They've been in the room where the whiteboard actually had stakes attached. The ByteByteGo framework isn't theoretical - it's what engineers who survived production at scale reach for when they have to explain a system in 45 minutes.

Consistency also plays a role that doesn't get enough credit. The Saturday newsletter hasn't missed a week. The YouTube channel posts on cadence. The books arrive when announced. In a creator ecosystem where most newsletters go quiet after six months, two years of weekly publication is itself a differentiator. The audience trusts it because it shows up.

One million engineers, two founders, no outside funding anyone's found evidence of. The 2M+ audience across every platform - newsletter, YouTube, GitHub, Twitter, LinkedIn - was built from the ground up on the proposition that good technical writing, delivered consistently, is the rarest thing in engineering education. It still is. ByteByteGo just proved it works at scale.