If you work with backend microservices or distributed systems, you know that learning System Design is never really “done.” Between parsing through heavy engineering blogs, reading whitepapers, and studying foundational books, the sheer volume of information can be overwhelming.

Recently, I’ve completely changed how I organize my notes, case studies, and architecture deep-dives. Instead of scattering bookmarks and PDFs across my desktop, I’ve started using Google’s NotebookLM (now integrated as Gemini Notebooks) to build a personalized, AI-powered second brain specifically for System Design.

Here is exactly how I use it to study, and the features that make it an absolute game-changer.

1. Curating Specialized Knowledge Bases (The “Sources” Feature)

The core of NotebookLM is that it only “knows” what you feed it. It doesn’t hallucinate based on the open web; it grounds its answers strictly in the sources you upload.

I’ve segmented my learning into a few distinct workspaces:

• System Design — Real Company Incidents: I drop post-mortem URLs, engineering blogs, and incident reports in here. When I want to study how a massive load-balancing failure was mitigated, all the raw data is in one place.
• System Design Learning: A general workspace for my own notes, architecture diagrams, and concepts like caching strategies (Redis), database sharding (PostgreSQL), and distributed consensus.

The takeaway: You can upload PDFs, text files, Google Docs, and even YouTube URLs. It essentially builds a private language model trained exclusively on your study materials.

2. Grounded Q&A (Talking to Your Notes)

Once the sources are in, the magic happens. Let’s say I’m writing a new technical guide or prepping for a complex architecture discussion. I don’t have to control-F through 30 different engineering blogs.

I can just ask the notebook: “Summarize how different companies handled cache stampedes during traffic spikes, based on the incident reports.”

NotebookLM scans the exact documents I uploaded, synthesizes the answer, and most importantly, cites its sources. It provides little clickable footnote chips that take me directly to the paragraph in the original document. It feels less like searching and more like having a senior staff engineer summarizing documents for you.

3. Extracting Relevant Chunks for Blog Writing

As someone who regularly writes technical articles and creates educational content, synthesizing information quickly is vital. When I’m drafting a new post on scaling, I use NotebookLM to retrieve highly relevant chunks of my own research. It helps me bridge the gap between abstract concepts and high-level system architecture by finding connections across my notes that I might have missed.

4. Audio Overviews & Creating Short Form Videos

NotebookLM is famous for its “Audio Overview” feature — generating incredibly realistic, conversational AI podcasts based on your sources. I can take a dense whitepaper on distributed tracing, hit a button, and listen to two AI hosts break down the architecture while I’m commuting.

But what I’m really leveraging right now is using these synthesized notes to create short videos. By prompting the notebook to generate tight, 60-second educational scripts from my “Real Company Incidents” notebook, I can easily produce bite-sized content (like YouTube Shorts or Reels) explaining complex architectural failures and solutions without spending hours storyboarding.

Features I’m Planning to Try Next

While my current workflow is solid, I am just scratching the surface. In the coming weeks, I plan to experiment with:

• Collaborative Notebooks: Sharing my “System Design Learning” notebook with peers to see how NotebookLM handles a multi-contributor knowledge base where we all dump our interview prep notes.
• Code & Architecture Integration: Uploading more raw schema structures, API contracts, and snippet files to see how well it can cross-reference high-level design principles with actual implementation details.
• Advanced Formatting Outputs: Testing the limits of how NotebookLM can automatically generate presentation slides, study guides, and comprehensive FAQs directly from my curated sources.

Final Thoughts

Learning System Design isn’t just about memorizing patterns; it’s about understanding trade-offs. By curating my own specific notebooks, I can constantly query, cross-reference, and challenge my understanding of how scalable systems are built.

If you are prepping for interviews, trying to level up to a senior engineering role, or just love reading about large-scale architecture, I highly recommend giving it a try.