TL;DR
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
The Pragmatic Engineer published an interview with Will Larson about changing expectations for engineering managers and the shifting route to technology leadership. Larson argues that middle managers may need to return to line management and rebuild hands-on technical skills, while AI is bringing technical decisions closer to leadership. The interview is commentary and personal experience, not a formal study or industry-wide measure.
The Pragmatic Engineer has published an interview with Will Larson, CTO of Imprint, on how the unwritten rules of engineering management have changed since the 2010s. Larson argues that middle managers may need to return to line management and rebuild hands-on technical skills as companies reconsider leadership roles and AI brings technical decision-making closer to engineering leaders.
The conversation examines a shift from management practices Larson associates with the long post-financial-crisis period of low interest rates to tighter expectations for engineers and managers today. The episode’s host frames the discussion around whether middle management has become a less secure career path and whether the traditional route from engineering management to executive roles is changing. These are topics and arguments raised in the interview, not findings from a broad survey.
Larson recommends that some middle managers return to line management and reskill, a move he says he has made himself. The interview also addresses AI’s effect on engineering work, including the possibility that technical decisions will again become a larger part of leadership roles. The source does not specify a particular AI system, quantify its effect on jobs, or offer a timeline for these changes.
Larson draws on experience at Digg, Yahoo, Stripe, Uber, Carta and Calm, as well as his current role at Imprint. The interview revisits Digg’s 2010 relaunch, the role of incentives in infrastructure decisions, and the challenges of giving senior engineers work that serves business needs. Larson is also the author of books on engineering leadership, including An Elegant Puzzle and Staff Engineer.
Why Management Roles May Shift
The discussion matters to working engineers because it questions the assumption that a manager’s career should progress mainly through larger teams and broader administrative responsibility. Larson’s recommendation points instead to a possible cycle: managers may need to return closer to day-to-day team work and refresh technical skills. For people considering management, that is a reminder that the role’s expectations can change with company needs.
The interview also connects management choices to company economics. Larson’s examples describe how approval systems, deadlines and incentives can produce unintended outcomes, from unused servers to a risky product rewrite. These accounts underline that management is not only about org charts or career ladders; it also shapes how teams allocate resources and respond to business pressure. The claims are grounded in his recollections rather than independent evaluations of those companies.
AI adds a current question to that debate. If tools alter how software is built, leaders may need to make or review more technical decisions, as the interview suggests. But the source does not establish that AI will remove management jobs or that all managers must become hands-on engineers. Larson’s argument is a perspective for teams to weigh, not a universal forecast.
As an affiliate, we earn on qualifying purchases.
From Digg to Today’s Teams
Larson’s Digg account provides one example of the decisions he uses to discuss management. He worked at the company during its Digg v4 relaunch, which the source describes as a rewrite delivered against a deadline set by then-CEO Kevin Rose. The new version alienated users and had performance and reliability problems. Larson said the engineering team found Python memory leaks among the technical issues.
The source also reports that Digg was already losing traffic to Facebook and was affected by a Google algorithm change associated with a 60–70% traffic loss. That figure is presented in the report as part of Larson’s account; it is not accompanied by a measurement period or independent documentation. Larson’s view, as summarized by The Pragmatic Engineer, is that the rewrite did not alone cause Digg’s decline: he believes the company would have been overtaken by competitors regardless.
At Yahoo, Larson recalled that a requirement for the cofounder to approve server purchases led teams to trade spare machines informally. At Stripe, he led an organization of about 250 people and encountered senior engineers seeking more engaging assignments. The episodes help explain his broader point: management rules and incentives affect behavior, sometimes in ways leaders did not intend.
“I only have suffering to offer, but this suffering is what’s going to make the business succeed.”
— Will Larson, as quoted in The Pragmatic Engineer interview
What the Interview Cannot Establish
The interview offers Larson’s experience and analysis, not a representative account of engineering organizations. It does not provide data showing how many companies are reducing middle-management roles, how common a return to line management is, or whether the conventional path to CTO has changed across the industry.
The effects of AI on engineering roles remain unresolved in the source. It gives no forecast of job losses, adoption rates or which leadership tasks are most likely to change. The Digg traffic figure also lacks a stated time window and comparison baseline in the supplied report, and the account of the relaunch is not independently assessed there.
How Leaders Apply the Advice
The source identifies no formal follow-up study, policy change or scheduled milestone. The next developments will depend on how individual companies structure engineering teams and whether their managers are expected to maintain technical skills alongside people and organizational responsibilities.
Readers can treat Larson’s recommendation as a prompt to examine role expectations rather than as a settled rule: companies may need to clarify what managers own, how technical decisions are made and how senior engineers are assigned work. The interview also notes that Imprint is hiring for engineering management roles, but it does not detail how those positions will be designed or how they will use AI agents.
Key Questions
What is the main news in the interview?
The Pragmatic Engineer published an interview in which Will Larson discusses changing expectations for engineering managers and argues that some may need to return to line management and rebuild technical skills.
Who is Will Larson?
Larson is the CTO of Imprint and a former engineering executive at companies including Carta and Calm. He has also worked at Stripe, Uber and Digg, and has written books on engineering leadership.
Does Larson say all middle managers should become hands-on engineers?
No. The report presents his recommendation that middle managers consider returning to line management and reskilling. It does not establish this as a requirement for every manager or company.
What does the interview say about AI and management?
It argues that AI is changing engineering roles and may bring more technical decision-making back to leadership. The source does not quantify the effect or predict how many jobs could change.
Did the Digg v4 rewrite cause Digg to fail?
The report says the relaunch had user, performance and reliability problems, but Larson does not believe it alone caused Digg’s decline. He argued that competition from Facebook and Reddit would have challenged the company regardless.
Source: rss
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
