Building for Billions: 7 Leadership Lessons from Chris Slowe (Former CTO and Founding Engineer at Reddit)
“In thinking about an organization as an engine, strategy and culture are the knobs to adjust to get it working.”
What does it take to build and scale one of the world's largest online communities?
Former Reddit CTO and founding engineer Chris Slowe joined Enrich members for a conversation on engineering leadership, organizational design, AI, hiring, and scaling technology for billions of users. With a career spanning Reddit, Hipmunk, and a PhD in experimental physics from Harvard, Chris shared practical lessons learned from years of building products and organizations through periods of rapid growth.
1. Strategy and culture are the two levers of every organization
Chris offered a simple framework for thinking about leadership:
"In thinking about an organization as an engine, strategy and culture are the knobs to adjust to get it working."
Processes, org charts, and tooling matter—but leaders ultimately influence outcomes by setting a clear strategy and intentionally shaping culture. When those two elements are aligned, organizations move faster and make better decisions.
2. Remote teams need intentional time together
Although Reddit operates as a remote-first company, Chris emphasized that great distributed cultures aren't built entirely online.
His recommendation: every manager should spend two full days with their team every six months.
One day should be structured around planning, priorities, and work. The second should be intentionally unstructured, allowing teammates to connect as people rather than coworkers.
The goal isn't just collaboration—it's creating the kind of trust that's difficult to build through video calls alone.
3. Proven technology usually beats the newest technology
Engineering leaders often feel pressure to adopt the latest tools and infrastructure. Chris cautioned against chasing novelty for its own sake.
"As much as it's fun to choose bleeding edge technology because it's really clever, the bleeding edge can cut both ways."
He shared an early experience deploying Cassandra before it reached pre-release—a decision that became a costly lesson in stability and operational risk.
Innovation matters, but reliability matters more when you're building products at scale.
4. AI's biggest opportunity today is orchestration—not coding
Chris challenged some common assumptions around AI's impact on software engineering.
Rather than replacing engineers, he believes today's AI tools create the most value by orchestrating engineering work.
Examples include:
Drafting design documents
Breaking projects into executable tasks
Creating pull requests
Generating testing workflows
Improving communication across engineering teams
Engineering still requires judgment, system thinking, and an understanding of how software fits together. Those remain distinctly human strengths.
5. Leaders need both dashboards and direct conversations
Metrics tell one story. People tell another.
Chris encourages leaders to create two separate channels for understanding what's happening inside the organization.
The first is top-down: dashboards, KPIs, and reporting that provide an executive view.
The second is bottom-up: regular conversations with individual contributors.
Those conversations are often less efficient—and sometimes include plenty of complaints—but they surface context, friction, and emerging issues long before they appear in dashboards.
The "messy picture" is often the most valuable one.
6. Never reorganize without a clear purpose
Reorganizations are tempting solutions to organizational challenges, but Chris warned they're also one of the easiest ways to create confusion.
He shared an experience leading a reorganization before the team had clearly defined why it was necessary.
The result? More disruption than improvement.
The lesson: don't reorganize because it feels like progress. Reorganize only when the objective is explicit and measurable.
7. Executive hiring starts with radical honesty
When hiring senior leaders, Chris follows a simple approach. Interview remotely first, and meet in person before making a decision.
More importantly, be transparent about the challenges they'll inherit.
Rather than selling candidates on an idealized version of the role, Chris believes executive hiring works best when both sides fully understand the problems that need solving.
The right leaders aren't looking for perfect organizations—they're looking for meaningful problems they can help solve.
Final Thoughts
Throughout the evening, one theme surfaced repeatedly: scaling organizations isn't just about better technology. It's about making better decisions.
Whether discussing AI, hiring, remote work, organizational design, or engineering systems, Chris returned to the importance of clarity, intentionality, and leadership judgment.
As AI reshapes how teams build software, those human qualities may become even more valuable—not less.