Lessons in Leadership
summary
CTO journeys map to concrete practices: hiring ramps from 25→250 engineers by creating remote studios in Boston, Seattle and SF, using Slack/JIRA/Confluence/Zoom, holding two companywide summits a year, and confronting monolith pain so architecture matches distributed teams. Diversity moves include a Code2040 partnership, structured interview packs and panels, and progress metrics such as 35% women engineers and 40% of new hires people of color. A past integration shipped to spec with zero adoption underscores insisting on problem-first hypotheses and customer impact.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:49Career paths to CTO
- 2:54The evolving role of a CTO
- 5:30Understanding customers
- 8:56Building executive relationships
- 12:20Strategy and organizational growth
- 15:41Intentional D&I strategies
- 25:21Scaling through remote work
related talks
43mOne doesn't simply walk into a management position -what I learned...
59mTech leadership, one year after
24mFrom Developing Code To Developing People
16mThe secret to technical leadership
17mLessons in building great teams
32mPanel discussion: The journey to building effective engineering teams
51mTeaching and managing for technologists
23mTech leadership for everyone