Five Years of Running a Systems Reading Group at Microsoft

In March 2026, a Microsoft engineer reflects on five years of running a systems reading group that started in 2021 after joining the Azure Databases team. What began as a small gathering of database enthusiasts has evolved into a cross-Microsoft community exploring the foundations of modern computing.

The group's origins were simple: a handful of people discussing Algorithms Behind Modern Storage Systems in an informal hour-long conversation. The format stayed consistent—everyone reads a paper independently, then meets to discuss—but the scope expanded organically. Early sessions covered database classics like WiscKey, LLAMA, and the Bw-Tree, but conversations naturally drifted to adjacent topics like memory hierarchies and consensus protocols.

By 2024, the group shifted from one-off papers to guided reading series, working through sections of the Red Book over multiple sessions. This structure proved transformative, allowing participants to build shared context and dive deeper into topics. The 2026 theme focuses on datacenter foundations, reading The Datacenter as a Computer to explore servers, racks, networking, and the infrastructure we take for granted when building distributed systems.

Several key lessons emerged from five years of organizing:

Consistency beats ambition. Meeting once a month without fail proved more sustainable than aiming for biweekly sessions that often got skipped. Habit building matters more than frequency.

Let curiosity guide scope. Insisting on "databases only" would have killed the group's momentum. Following interesting threads—from storage engines to memory chip architecture—kept discussions fresh and attracted participants from across Microsoft.

Series work better than singles. Multi-session deep dives on single topics created richer discussions than context-switching between unrelated papers. Shared context compounds over time.

Expertise isn't required. Some of the best sessions happened when the organizer admitted they didn't deeply understand the topic. Collaborative learning proved more engaging than lectures.

Co-organizers multiply impact. When a colleague reached out to restart the series during a quiet period, it made a huge difference. Shared responsibility keeps momentum when one person gets busy.

Make participation frictionless. Not everyone reads every paper, and that's fine. Starting with a quick 5-minute summary ensures meetings work even when people come unprepared.

The benefits extended beyond learning. The organizer connected with engineers, researchers, and scientists across Microsoft who share similar curiosities. Some connections led to useful conversations about real work problems; others were simply interesting people to talk to. The group became proof that Microsoft employs many people genuinely interested in systems fundamentals.

For anyone considering starting a reading group at their company, the advice is straightforward: don't overthink it. Post a paper, invite interested colleagues, and see who shows up. The rest can be figured out along the way.

Microsoft employees can find the group at aka.ms/msrg. The journey from a small database reading group to a thriving systems community demonstrates how simple, consistent gatherings can build lasting technical communities.