Dev Interrupted: Assembling & Nurturing Engineering Teams

Episode Summary

Executive Summary: Noah Labhart argues that strong engineering organizations are built by hiring “developers” who own outcomes, not just “programmers,” and by pairing hungry career-changing engineers with senior mentors. He emphasizes autonomy, direct feedback, shared goals, and treating people like people to build collaborative, high-retention teams. His Variable org uses squads aligned to product lines and relies on engineering managers—not product managers—to drive execution.

Main Topics: Hiring career-changing engineers (Priority: 5/5): Variable intentionally recruits engineers who came from non-traditional or non-programming backgrounds, valuing their hunger, growth mindset, and ability to think like end users. Senior mentorship and team composition (Priority: 5/5): Career-changing engineers perform best when paired with experienced technical leaders who can teach architecture, provide feedback, and create room for learning. Collaboration, autonomy, and accountability (Priority: 5/5): Labhart stresses high autonomy with high expectations, early code ownership, and direct feedback when performance slips, while avoiding micromanagement. Defining “developers” vs. “programmers” (Priority: 4/5): He distinguishes developers as people who own product outcomes across design, QA, strategy, and customer context, unlike programmers who simply execute code tasks. Squad-based operating model (Priority: 4/5): Variable organizes engineering into squads aligned to product lines, with subject-matter ownership and supporting backbone teams like core platform and core UI. Leadership growth and succession (Priority: 4/5): The company promotes from within by identifying people with leadership or architectural potential and growing them into future managers and architects. Feedback culture and hard personnel decisions (Priority: 5/5): Labhart describes learning to shorten the leash when performance issues persist and says letting someone stay too long can hurt the whole team.

Key Arguments: Career-changing engineers bring end-user perspective and motivation that improve product quality and customer alignment. A startup benefits when less-experienced engineers are paired with senior staff who can mentor and establish technical standards. High autonomy works only when expectations are clear and feedback is direct; otherwise collaboration and performance degrade. Engineering hiring should prioritize ownership, collaboration, and pride in the product over narrow coding ability. Squads work best when engineers are true subject-matter owners and can help shape what should be built, not just receive tasks. Engineering managers should be able to lead across disciplines, not only within a single technical specialty. Delayed accountability can damage team productivity, morale, and product quality, so leaders must address misfits sooner rather than later. Treating feedback as a shared problem-solving exercise, rather than boss-versus-employee conflict, improves trust and performance. Helping employees pursue their long-term career goals builds stronger retention and a healthier culture.

Data Points: Branches analyzed: 3.6 million - LinearBee 2023 engineering benchmarks report mentioned in the sponsor segment Dev teams analyzed: Over 2,000 - LinearBee 2023 engineering benchmarks report Countries covered: 32 - LinearBee 2023 engineering benchmarks report Estimated team mix: 25% computer science / 75% career-changing engineers - Labhart’s approximate current Variable composition for discussion purposes Delay in performance decision: 6 months longer than it should have been - Example of an early hire kept on too long Startup team size example: Handful of career-changing engineers plus founder-led technical leadership - Variable’s early days when Noah was providing foundational guidance Squad size: Biggest squad is 10 to 11 individuals - Variable’s squad structure

Pivotal Quotes: "It's us facing our shared goals." — Noah Labhart: Describing how he frames feedback and accountability as a team problem rather than a boss-versus-employee conflict "We hire developers, not programmers." — Noah Labhart: Explaining Variable’s preference for people who own product outcomes across strategy, design, testing, and customer context "Treat people like people; actually care about their well-being." — Noah Labhart: His closing advice on building strong teams and supporting career growth

Implications: Engineering leaders should build teams around ownership, collaboration, and coaching—not just technical output. Hiring for potential, pairing with mentors, and acting quickly on misfits can improve product quality, retention, and organizational resilience.