Founders as DevRel | DevRel Almanac

Some founders and CEOs perform much of their company’s developer-relations work. This can work well when the founder has relevant technical expertise and participates directly in product and community discussions.

The examples below show why founder-led DevRel can work unusually well, and where the same concentration of authority becomes a liability.

Why founder-led DevRel works

Three structural reasons:

The founder can explain decisions directly. When founders write about their own engineering or product decisions, the author and decision-maker are the same person.
Founders can change product behaviour fast. Community feedback that reaches the founder can ship as a product change in days, not quarters. The feedback loop is short and visible.
Founders can speak for company strategy. They can explain how company priorities inform product decisions.

Why it eventually has to stop being the only DevRel

Founder-led DevRel does not scale. As a company grows:

The founder cannot personally engage with every developer.
Community decisions need delegation.
The founder’s voice can become a single point of failure (departure, burnout, controversy).
The team needs structured operations the founder doesn’t have time to build.

A founder can remain one public participant while a team owns programmes, operations, and other public communication.

Notable founder-as-DevRel figures

Patrick Collison (Stripe)

Co-founder and CEO of Stripe since 2010, with a sustained developer-facing public role.

Sustained developer-facing public presence through Stripe’s developer blog, conference appearances, and his personal site (patrickcollison.com).
Substantial engagement in public technical discussions on X, Bluesky, blog comments, and HackerNews.
Stripe’s documentation culture is widely described as “what happens when the founders care about docs.” Multiple senior Stripe alumni have credited Patrick and John Collison’s hands-on engagement with docs quality during the company’s growth.
Stripe Press. Patrick’s broader intellectual project, publishing books that have shaped how the tech industry thinks about technology, history, and engineering.

John Collison (Stripe)

Patrick’s brother and co-founder; less public-facing than Patrick but substantial in customer-facing communications, Sessions keynotes, and developer-focused public conversation.

Jeff Lawson (Twilio, until 2024)

CEO of Twilio from founding (2008) until 2024.
SIGNAL keynote presence anchored the conference for over a decade.
“Software people” framing: Lawson popularised the idea that software companies should be run by people who understand software, which aligned with the developer-first culture Twilio built.
His book Ask Your Developer (HarperBusiness, 2021) made the developer-as-decision-maker case to a non-technical executive audience.

Mitchell Hashimoto and Armon Dadgar (HashiCorp)

Co-founders of HashiCorp (2012); both deeply technical co-CEOs / co-CTOs through the IPO.
Conference presence. Mitchell’s many talks on the open-core business model and on individual products (Vagrant, Packer, Terraform, etc.). Armon’s keynotes particularly noted for architectural depth.
Mitchell left HashiCorp in 2023 and began open-source work on the Ghostty terminal emulator.
IBM acquired HashiCorp in 2025.

David Heinemeier Hansson (DHH) and Jason Fried (37signals / Basecamp / HEY)

Creator of Ruby on Rails. DHH has remained publicly involved in the Rails community for two decades through writing, talks, and technical decisions.
37signals (now mostly Basecamp / HEY). Running founder-led writing through their company blog, the REWORK book (with Jason Fried), and DHH’s personal site.
Notable. Periodic controversy around DHH’s political and corporate-culture posts has illustrated the risks of founder-as-DevRel: the founder’s reputation and the product’s reputation are inseparable.

Linus Torvalds (Linux Foundation, kernel maintainer)

Creator of Linux (1991) and Git (2005). Not a CEO, but a founder and maintainer with a long-running public role in kernel development.
Kernel mailing list presence for over thirty years has been the operational community-management of the project.
His communication style has produced lasting community-cultural effects, for better and worse.

Guillermo Rauch (Vercel)

Co-founder and CEO of Vercel. Substantial public-facing developer presence through X / Bluesky, Vercel’s launch announcements, and Next.js Conf keynotes.
Significant alignment with the Vercel DevRel team (Lee Robinson, Delba de Oliveira); founder and DevRel-head co-produce major launches.

Amjad Masad (Replit)

CEO of Replit. Frequent public-facing developer engagement, particularly around the Replit AI Agent product launches.
Substantial X presence and willingness to engage with founders building on Replit.

Tobi Lütke (Shopify)

CEO of Shopify. Significant public-facing developer-platform presence; long-time Ruby and Rails community member.
Public developer communication. Lütke discusses Shopify’s platform and his own technical work with developers.

Paul Copplestone (Supabase)

Co-founder and CEO of Supabase. Highly visible build-in-public approach, regular product-update content, conference and podcast presence.
Launch Weeks at Supabase are co-produced by founder, team, and community in a tight loop.

Harrison Chase (LangChain)

Founder of LangChain. Primary public face; effectively LangChain’s senior DevRel-equivalent voice through the period 2022 to 2024 before broader team built around him.

Clem Delangue (Hugging Face)

Co-founder and CEO of Hugging Face. Sustained engagement on X / Hugging Face Forums; central voice in open-source ML community.

Jensen Huang (NVIDIA)

CEO of NVIDIA since 1993. GTC keynotes, particularly the AI-era spring events, have become marquee industry moments rivalling Apple’s WWDC presentations.
Developer-facing role. Although his title is not in DevRel, Huang presents NVIDIA’s technical direction to developers through GTC keynotes and product announcements.

Eric Migicovsky (Beeper, Pebble, founders generally)

Migicovsky communicated directly with developers during Pebble’s original run and again during the platform’s 2024 to 2026 revival through Beeper.

Mike Krieger (Anthropic, formerly Instagram)

Chief Product Officer at Anthropic. Substantial executive-as-public-developer-voice role, especially around Claude’s product evolution.

Aja Hammerly (Firebase Studio / Google)

Although not a CEO, Hammerly leads Firebase Studio and communicates publicly about Google’s AI developer tools.

Failure modes of founder-as-DevRel

When the pattern goes wrong, common failure modes:

Founder controversy hurts the product. When the founder’s public profile produces controversy, the product’s developer relations is collateral damage. (Multiple high-profile examples across the field.)
Founder bottleneck. Decisions queue at the founder; developers expect personal responses that don’t scale.
Founder departure. When the founder leaves or steps back, the DevRel function collapses unless a real team was built underneath.
Founder-only product narrative. If the founder is the only voice, the product appears to be a one-person show, which limits enterprise adoption and partnership credibility.
Less direct communication. As a company scales, a founder’s public communication can become more controlled and less candid.

When the founder-as-DevRel pattern fits

It fits when:

The founder is genuinely technical and was once the kind of developer the product serves.
The product is developer-led at every level.
The company is at a stage where a senior founder voice has more effect than scaled team coverage, typically before Series C.
The founder is willing to engage in the inbound direction as well as the outbound: taking community criticism without becoming defensive.

It does not fit when:

The founder cannot or will not engage publicly at the technical depth required.
The product serves a non-developer audience.
The company is at a scale where the founder’s personal time is needed for board-level work, not developer engagement.