Skip to main content

The Rise of Google, Part 4: The Founding

The Founding

🎬 Prefer to watch? Here's the 60-second version:

Watch on YouTube ▶

📚 The Rise of Google — a 20-part series. See all parts »  |  « Part 3: From BackRub to Google

By the summer of 1998, Larry Page and Sergey Brin had a problem that most graduate students would kill for: their side project was too good to stay a side project. BackRub had become Google, PageRank was quietly outperforming every commercial search engine on the market, and—as we saw in Part 3—a Sun co-founder named Andy Bechtolsheim had just handed them a $100,000 check after a ten-minute demo on a Palo Alto porch. There was only one catch. The check was made out to “Google Inc.,” and Google Inc. did not exist.

A check that forced a company into being

For roughly two weeks that check sat in a desk drawer while Page and Brin scrambled to do the one thing they had been avoiding: turn a research prototype into a real business. You cannot deposit money to a company that has not been incorporated, and so on September 4, 1998, Google was officially registered as a privately held company in California. Page was 25. Brin was 24. Both formally took leave from their Stanford PhD programs—a “temporary” pause that would turn out to be permanent.

Incorporation unlocked more than a bank account. With a legal entity in place, the founders could finally gather the informal promises floating around Silicon Valley into an actual seed round. Bechtolsheim’s $100,000 was joined by money from Stanford professor David Cheriton, from Sun co-founder–turned–angel Ram Shriram, and—famously—from a young Amazon founder named Jeff Bezos, who liked Page and Brin and wanted in. By the time the round closed, the two students had assembled close to $1 million in initial funding. Not bad for a company whose entire product still lived on borrowed hardware.

The garage on Santa Margarita Avenue

A company needs an office, and Google’s first one was not an office at all. In September 1998 the founders moved out of their Stanford dorm rooms and rented a garage—plus a few spare rooms—in a house on Santa Margarita Avenue in Menlo Park. The rent was about $1,700 a month, which the fledgling company could suddenly afford, and the landlord was a Stanford friend named Susan Wojcicki. She was newly married, carrying a mortgage, and figured renting out the garage would help cover it. She had no way of knowing she was leasing space to the company that would define the next two decades of the internet—or that she would soon quit her own job to join it, eventually rising to run YouTube.

The garage was cramped, freezing when the door was open and stifling when it was closed, and stuffed with the cheap, cobbled-together servers Page loved to build from spare parts. A ping-pong table doubled as a desk. The refrigerator was stocked, the hours were brutal, and the whole operation ran on the conviction that search was a problem worth obsessing over. It was, in every cliche and also in truth, a garage startup.

Employee number one

The founders’ first hire was another Stanford PhD student, Craig Silverstein, who became Google’s first employee and would spend more than a decade there as a director of technology. In those early months the line between “founder,” “employee,” and “friend who showed up to help” was blurry. There was no HR department, no org chart, no polished mission statement—just a handful of people who believed the messy, link-tangled web could be organized, and who were willing to sleep near their servers to prove it.

What makes the founding remarkable in hindsight is how little of it was planned. Page and Brin had spent two years trying not to start a company—they had even tried to sell the technology and go back to their studies. Incorporation happened almost by accident, forced by a check they couldn’t cash. But once Google Inc. existed, the momentum was undeniable. Within a year the garage would be too small, and the company would decamp to a real office at 165 University Avenue in Palo Alto, then to Mountain View, growing faster than anyone inside it could quite believe.

They had a name, a company, a million dollars, and a garage full of humming machines. What they did not yet have was a way to make money—and a distinctly unusual idea about how a company should behave. Next time: the three words that became Google’s conscience—“Don’t be evil.”


🔗 Explore more from Syncster

Comments

Popular posts from this blog

Cursor AI Review: Is the AI Code Editor Worth It?

I've been using Cursor as my main code editor for a while now, and enough people have asked whether it's worth switching to that a proper review felt overdue. Short version: for me, yes — but with caveats. What is Cursor? Cursor is an AI-first code editor built as a fork of VS Code. That means every extension, theme, and keybinding you already use in VS Code works here, but with AI woven directly into the editing experience instead of bolted on as a plugin. It's made by Anysphere and can run models from OpenAI and Anthropic under the hood. What I like Tab completion is uncanny. Cursor predicts your next edit — not just the rest of the line, but the next change across the file. Once you get used to hitting Tab, going back to a plain editor feels slow. The Composer / Agent mode. You describe a change in plain language and it edits multiple files at once, showing you a diff to accept or reject. For refactors and boilerplate, this saves real time. It unde...

MacBook Pro M5 vs M5 Pro: Which One Should You Actually Buy?

Apple's latest 14-inch MacBook Pro comes in two very different flavors: the base M5 and the step-up M5 Pro . On paper they look similar — same gorgeous Liquid Retina XDR display, same design — but under the hood the gap is bigger than the names suggest. Here's a clear, no-hype breakdown, with concrete use cases so you can match the chip to your work. Quick spec comparison Spec M5 M5 Pro CPU 10-core (4 performance + 6 efficiency) Up to 18-core (6 performance + 12 efficiency) GPU 10-core Up to 20-core Neural Engine 16-core 16-core Memory bandwidth 153 GB/s 307 GB/s (roughly double) Unified memory 16 / 24 / 32 GB 24 / 48 / 64 GB Max storage Up to 4 TB SSD Up to 8 TB SSD Battery (video playback) Up to 24 hours Up to 22 hours Media engines Single encode/ProRes engine More encode/ProRes engines (higher configs) What actually changes between them More cores — the M5 Pro nearly doubles CPU cores and adds GPU cores, so sustained, multi-threaded work finishe...

How I used Google Sheets and Apps Script

Google Sheet is one of the most powerful spreadsheet application that exists online, rivaling with Microsoft's Excel. One of the main strengths is its strong support for collaboration with other users, much easier and popular than collaboration tools with Microsoft Office. Aside from plain spreadsheet, it also supports extensions such as macro. If you are familiar with macros on other office tools, they work almost the same. However, the most extension I use and tinker with is the Apps Scipt . Apps Script Extension One of the challenges I faced recently is how do I track or monitor reports in our department if they are submitted on time or worst, forgotten due to lack of better monitoring tools. So I thought if there can be simple applications that can be deployed or use by a more general user to allow reminding periodically what reports are approaching due dates or those that are past dues. Then I looked for a way, instead of creating a full blown app from scratc...