Scaling a company is only half the battle; scaling your own career in lockstep is the harder, more enduring challenge. I’ve seen high-growth environments reward those who adapt early and often, which is why the arc of Mike Boufford’s journey resonates deeply with me as a product leader.
Mike Boufford, CTO of Greenhouse, an applicant tracking system and recruiting platform.
He wrote the first line of code at Greenhouse in May 2012, and he’s still there — over a decade later.
This isn’t the typical path of non-co-founding engineers, who usually get layered or leave to start their own ventures.
Drawing on his story, I zero in on how founders build an environment that makes early employees want to stay, and importantly, how leaders can build the career skills and self-awareness they need to succeed at a startup long-term. In my experience, that combination—healthy culture plus relentless personal development—is what keeps top talent growing rather than going.
How his own motivation changed over time and how he managed his relationship with the company’s co-founders. I’ve learned that motivations naturally evolve—from creation and ownership, to scale and stewardship, to legacy and leverage. Naming those shifts early helps you reset expectations with co-founders before friction builds. Practically, this means recurring check-ins on roles, decision rights, and the tradeoffs you’re willing to accept as the organization matures.
The techniques he used to prepare himself for every next phase of growth and how his role would have to change in 18-24 months. I encourage leaders to keep a running “future job description” and refresh it quarterly. Ask: What will break at our next order of magnitude? Which systems, skills, and successors must I develop now so that I’m qualified for the job I’ll have in two years? This future-back planning keeps you ahead of the curve as the startup compounds.
Why he read two books on every other executive’s area of the business when he joined the leadership team. That habit builds cross-functional fluency fast. In my teams, this kind of immersion reduces friction with peers, sharpens strategy, and anchors debates in shared constraints—exactly what product and engineering leaders need to operate credibly at the executive level.
For a nuanced perspective on retention and healthy team evolution, I recommend reading: Why This Engineering Leader Thinks You Shouldn’t Aim for Zero Regrettable Attrition. Embracing the right amount of change—especially at senior levels—can unlock growth for both the organization and the individual.
If you’re navigating startup leadership, product management leadership, or the IC to manager transition, take this playbook to heart: anticipate the next phase, invest in cross-functional competence, and renegotiate your role before the org structure forces it. That’s how you scale with your startup, not in spite of it.
Inspired by this post on First Round.
Leave a Reply