What Happens Now to All the Laid Off Tech Workers?

Episode Summary

Executive Summary: The episode is a follow-up discussion with Patrick McKenzie on why big tech hired so aggressively during the pandemic, why layoffs are now happening, and what that means for workers and the broader economy. He argues the boom was driven by extraordinary demand and cheap capital, while current cuts reflect normalization, performance review dynamics, and a need to rebalance after unusually rapid expansion—not necessarily an economy-wide collapse.

Main Topics: Pandemic-era tech hiring boom: McKenzie explains that fiscal stimulus, asset-price gains, and a sudden shift of commerce and work online created extraordinary demand, prompting tech firms to expand headcount rapidly. Why layoffs are happening now: The discussion emphasizes that growth rates have normalized, some pandemic-era hiring was overly aggressive, and companies are now reassessing which teams and products are core. How tech companies manage bloat and staffing: McKenzie breaks down how large firms scale recruiting, product teams, and management layers, and why some staffing excess is a natural byproduct of rapid expansion. Performance reviews and incentives in tech: The hosts and guest discuss how tech perf systems reward launching new things more than maintaining existing systems, which can distort internal priorities and staffing decisions. Job mobility and labor fungibility in tech: McKenzie argues that tech workers—especially early-career engineers—are relatively portable across roles and firms, and that layoffs do not imply the field is dead. AI, coding jobs, and future demand: The conversation closes on whether AI will replace coding jobs; McKenzie argues that tools like compilers historically expanded programmer productivity and likely increase overall demand, while the value chain around AI remains unsettled.

Key Arguments: Pandemic conditions produced a one-time demand shock: consumers stayed home, digital commerce surged, and tech revenue grew unusually fast. Companies hired aggressively because they expected the pandemic-era shift online to be durable and needed staffing to keep products and infrastructure running. When growth rates reverted closer to historical norms, the earlier hiring pace became unsustainable, leading to layoffs and hiring freezes. Some layoffs are about correcting cohort quality and organizational balance after unusually rapid hiring, not simply cutting the newest workers. Tech organizations naturally develop some bloat because recruiting, customer support, management, and product experimentation all expand with scale. Performance-review systems reward visible new launches more than maintenance work, pushing talented workers toward new projects rather than keeping legacy systems healthy. Layoffs are usually distributed across cohorts to avoid creating future skill gaps and operational problems. Tech labor is relatively fungible within broad job classes, so workers losing jobs can often find new roles without the sector being permanently impaired. AI may not reduce total programming demand; like compilers, it could raise productivity and expand the amount of software that gets built. The key question for AI employment is where value accrues: model-building at a few firms or productization across many companies.

Data Points: Stock Movers report length: 5 minutes or less - Promotional intro at the start of the episode. Tech sector headcount growth: 20%+ year-over-year at large firms - McKenzie says mature tech companies like Google, Amazon, and Facebook were hiring at this pace during the pandemic. Startup expansion: Multiples of pre-pandemic headcount - He describes early-stage firms as onboarding many times their prior workforce during the pandemic. Recruiter productivity: 25 hires per recruiter per year - Used as a back-of-the-envelope example for scaling recruiting staff. Typical engineering team size: 5 to 8 people - McKenzie says this is the basic unit of organization in many engineering groups. Typical number of problems per engineering team: 3 narrowly scoped problems - He describes the bandwidth of a small engineering team. Typical annual attrition in tech: About 10% of engineering staff - Used to explain ongoing backfill hiring needs. Company staffing target after cuts: 85% to 90% of current staffing - McKenzie estimates what many executives might consider an ideal level if they could adjust without consequences. Large-company technologists: 20% to 40% of employees - He notes that not most people at big tech firms are engineers; many are in non-technical roles.

Pivotal Quotes: "Structurally, tech companies are like sharks." — Patrick McKenzie: He uses the metaphor to explain why firms cannot stop hiring for long without harming the business. "If you only do great maintenance work for the next couple of years, you will be severely career limited here." — Patrick McKenzie: He is describing how performance systems reward new launches over sustaining existing products. "Reports of the field's demise were heavily exaggerated." — Patrick McKenzie: He cites the dot-com crash era to argue that current layoff fears should not deter people from learning engineering or coding.

Implications: The episode suggests tech layoffs are more a reset after pandemic-era excess than a sign the sector is collapsing. For workers, mobility remains strong, and for firms, AI and productization may create new demand rather than eliminate jobs.