Jan 6, 2019 · 41m · saastr
Successfully Managing The Hyper-Growth Stage
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
In this interview, GitHub Chief Strategy Officer Julio Avalos examines the operational realities of hypergrowth, sharing insights on evolving organizational governance, interrogating business assumptions, and scaling sustainably.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. How this is scored →
Jason as informed peer 2.4 Guest teaching 3.1 Guest disagreement 0.9 Jason pushing back 1.9
speaking balance: gold is Jason, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 30:40 Rejecting 'culture fit' as an ambiguous hiring fetish
Julio forcefully dismisses the common startup obsession with culture fit, describing it as an ambiguous, misused excuse to exclude qualified candidates without objective justification.
Hardest push from Jason ▶ 19:57 Pressing on past workplace harassment and cultural controversiesBlair presses Julio directly on GitHub's historical, well-publicized struggles with workplace culture, demanding substantive lessons for fast-growing startups.
Biggest teaching moment ▶ 17:10 Educating on the limits of developer-led sales in international marketsJulio provides concrete educational examples of why assuming international enterprise buyers share Silicon Valley's developer-centric mindset fails when pitching overseas procurement leaders.
Jason holds their own ▶ 16:02 Challenging checkbox assumption reviews in business strategyBlair challenges Julio on the practicality of reviewing core assumptions, pointing out that organizations routinely turn reflective exercises into superficial rubber-stamping.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | Jason as informed peer | Guest teaching | Guest disagreement | Jason pushing back | Why |
|---|---|---|---|---|---|---|
| Defining Hypergrowth as Systemic Stress | 1 | 2 | 0 | 0 | Blair prompts Julio on his definition of hypergrowth. Julio expands on the concept, explaining that true hypergrowth is defined by systemic strain and broken operational processes rather than arbitrary headcount doubling. | |
| Interrogating Growth Drivers and Centering the Developer | 2 | 3 | 1 | 1 | Blair asks how an organization identifies root causes of hypergrowth. Julio delivers an extended monologue critiquing Silicon Valley's reflexive worship of growth for its own sake and detailing GitHub's early assumptions. | |
| Interrogating Business Assumptions in Global Expansion | 3 | 4 | 1 | 2 | Blair pushes Julio on how leaders can genuinely interrogate foundational assumptions rather than treating the exercise as a perfunctory checklist. Julio illustrates the challenge using GitHub's international enterprise expansion into European markets where developer-centric messaging failed. | |
| Lessons on Workplace Culture, HR, and Diversity | 4 | 3 | 1 | 4 | Blair asks a direct, probing question regarding GitHub's past high-profile workplace culture and harassment issues. Julio responds candidly by deconstructing the pitfalls of unmanaged flat organizations and highlighting structural HR and diversity reforms. | |
| Balancing Organizational Structure with Startup Agility | 2 | 3 | 0 | 2 | Blair explores the tension between adding organizational process and retaining startup execution velocity. Julio details the confusion of consensus-by-emoji in early GitHub and the need for clear decision architecture. | |
| Operationalizing Hiring and Moving Beyond Culture Fit | 2 | 4 | 2 | 2 | Blair asks about balancing cultural coherence with hiring independent thinkers. Julio rejects conventional notions of 'culture fit' as an ill-defined fetish used to dismiss candidates arbitrarily and advocates for structured rubric-driven evaluation. | |
| Aligning Growth Strategy with Foundational Mission | 3 | 3 | 1 | 2 | Blair asks how founders can realistically resist pressure to grow fast after taking large venture rounds. Julio articulates why growth must remain anchored to an underlying mission rather than vanity metrics. |
Statements from this episode (12)
Avalos: GitHub operated with ~100 employees without managers, titles, or teams
“Where we were right around a hundred people, maybe a little bit over, no managers, Weren't going to have managers for another year and a half or close to two years, I think, from that point. And we didn't have titles. We didn't have managers. We didn't have re…”
Avalos: At least 90% of GitHub employees were technical in 2012
“I think probably 90% of the company at least was technical at the time.”
Julio Avalos: GitHub grew from 2.5–3M developers in 2012 to 25–26M in 2018
“We've gone from two and a half, three million people maybe back in 2012 to 25, twenty-six million people, developers using the site today.”
Avalos: GitHub had no sales or marketing functions in 2012
“We didn't have, say, we didn't have a sales function at the time. We didn't have a marketing function. We were primarily developers”
Avalos: Developer-first messaging fails with international enterprise buyers
“As we went to market outside of the United States, and maybe even outside of the Valley leading with a developer first kind of messaging, that wasn't always the right thing for your procurement, or your CIOs, or the CTOs, or the technical decision makers in In…”
Avalos: The next millions of software developers won't come from Silicon Valley
“The next several million software developers and users of all of our technology are not coming from the same places as where the last several million people came from. They're not coming necessarily just from Menlo Park and from Stanford. They're coming from D…”
Avalos: Keeping GitHub manager-free would have required far more bureaucracy
“If we had wanted to, and I'm not sure that we wanted to, we would have needed way more process, and way more bureaucracy than what we thought, ah, we had an appetite for. And that in some way, the lack of process, the lack of structure, leads to confusion with…”
Avalos: Ambiguous decision-making causes greater productivity loss than process
“Ah, I think that you end up having way more loss of productivity and confusion within your organization when people don't know where to go for answers. When people don't know who the ultimate decision rests on.”
Avalos: Tech hiring uses 'culture fit' to reject candidates arbitrarily
“Culture fit is a, ah, nobody knows what that means. It is a thing that too often gets used to bat down candidates for reasons that are unclear to you, unclear to them, and that you are not in a position to articulate necessarily.”
Avalos: GitHub wasted years and millions building custom HR software
“Do we want to be in the business of building out our own applicant tracking system, which we had? Do we want to be in the building business of building our own HR tools? Is this the right HR? Like, what do we know about any of these things? And that in a lot o…”
Avalos: GitHub built a billing engine unable to collect international taxes
“You're in a situation that, you know, that we found ourselves in where we built a billing engine that wasn't able to collect that in a particular jurisdiction, or you're not, you know, you're not creating, you're not collecting sales tax, whatever that happens…”