TL;DR
Get business pricing on networking and server gear
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
The Pragmatic Engineer published an interview with Will Larson on how engineering management expectations have shifted since the 2010s. Larson argues that middle managers may need to return to line management and rebuild technical skills, while AI is bringing more technical decision-making back to leadership. The interview also draws on his experiences at Digg, Yahoo and Stripe.
The Pragmatic Engineer has published an interview with Will Larson, CTO of Imprint, about how the unwritten rules of engineering management have changed since the 2010s. Larson argues that some middle managers may need to return to line management and refresh their technical skills as companies rethink how software teams work and AI reshapes engineering roles.
Larson draws on more than a decade in engineering leadership, including senior roles at Carta and Calm and earlier work at Stripe, Uber, Yahoo and Digg. He is also the author of books on engineering leadership, including An Elegant Puzzle, Staff Engineer and Crafting Engineering Strategy. The conversation examines how expectations for managers and engineers have shifted from practices shaped during the long period of low interest rates and abundant technology investment.
A central point in the interview is that middle management may be a less secure career path than it once appeared. The report says Larson recommends that middle managers return to line management and reskill, as he has done himself. The interview also asks whether some managers should consider retirement, but the supplied report presents that as a question for discussion, not a prediction that managers generally will be pushed out.
Larson connects these shifts to the changing route from engineering work to executive leadership. The episode covers how AI is changing engineering roles and, in the report’s account, bringing technical decisions back into leadership. It also discusses why career ladders still matter and why taking a step backward in a career can sometimes help someone move forward later.
Why Managers May Need Technical Depth
The discussion matters to engineering managers and senior engineers because it challenges the idea that management is a one-way move away from hands-on technical work. If leaders are expected to make or guide more technical decisions as AI changes software development, technical skills may need regular renewal rather than being treated as something a manager can leave behind.
That argument also has career implications. Returning to line management or rebuilding technical expertise could affect a manager’s responsibilities, status and prospects in the short term. Larson’s account does not establish that all companies will adopt this approach, but it raises a practical question for organizations: how should managers contribute when team structures, tools and expectations are changing?
For senior engineers, the interview offers a counterweight to the idea that advancement means working only on more interesting or prestigious problems. At Stripe, Larson led an organization of about 250 people and said some senior engineers sought more engaging work. He described the management challenge as directing effort toward difficult work the business needed, even when it was not the work individuals would choose.
Products Worth Considering

Samsung Galaxy Tab A11+ 11-Inch Tablet, 6GB RAM, 128GB Storage, Expandable, Gray

Samsung Galaxy Tab S7 11-inch Android Tablet 128GB Wi‑Fi with S Pen Mystic Black

Samsung Galaxy Tab A9+ 11-Inch Android Tablet, 64GB, Graphite
As an affiliate, we earn on qualifying purchases.
Lessons From Digg, Yahoo and Stripe
Larson uses earlier jobs to show how management practices and organizational incentives can shape engineering work. At Yahoo, where he worked from 2008 to 2010, he recalled having only two one-to-one meetings with his manager: one about another employee’s performance and another after he gave notice. The report presents this as an example of how infrequent manager check-ins could be in that period, rather than a claim about every workplace.
He also recalled a Yahoo server-approval process that required teams to justify purchases to cofounder David Filo. According to Larson’s account, the policy led to an informal exchange system: one engineer had 30 servers from a canceled project and traded them with colleagues who could not secure approvals. The episode illustrates how controls intended to improve accountability can create unintended workarounds.
At Digg, Larson worked during the company’s 2010 v4 rewrite, which the report describes as a troubled launch with performance and reliability problems that alienated users. Larson attributed technical problems to Python memory leaks introduced by developers less familiar with the language. But he does not say the rewrite alone doomed Digg: he argued that the company was already losing ground to Facebook and Reddit and had suffered a reported 60–70% traffic loss after a Google algorithm change.
“I only have suffering to offer, but this suffering is what’s going to make the business succeed.”
— Will Larson, recalling his response to senior engineers at Stripe
How Broad the Shift Will Be
The interview presents Larson’s views and experiences, not industry-wide data showing how many companies are changing management structures or requiring managers to return to hands-on work. The scale and pace of the shift remain unclear, as does whether these expectations will apply across different company sizes and types.
The supplied report also does not quantify how AI is changing engineering jobs or specify which management tasks will change most. Its discussion identifies AI as a force bringing technical decision-making back to leadership, but does not establish how quickly that will happen. Larson’s recommendation is not evidence that middle-management roles are disappearing, and the report gives no forecast for their overall number.
What the Interview Leaves Open
The immediate next step for readers is to hear or watch the full interview, which The Pragmatic Engineer says is available on YouTube, Apple and Spotify, with a transcript and timestamps on the episode page. Those materials may provide fuller detail on Larson’s reasoning and examples than the supplied summary.
Beyond the interview, the questions raised are likely to be answered company by company: whether managers are expected to refresh technical skills, how teams incorporate AI, and how career ladders recognize management and technical contributions. No policy change or industry-wide timetable is announced in the report.
Key Questions
What is the news about Will Larson?
The Pragmatic Engineer published an interview with Larson, Imprint’s CTO, about changing expectations for engineering managers and leaders.
What does Larson recommend for middle managers?
The report says Larson recommends that some middle managers return to line management and reskill, including by rebuilding technical capabilities. It does not establish that every manager should take that route.
How does the interview connect AI to engineering leadership?
The report says the conversation explores how AI is changing engineering roles and bringing technical decision-making back to leadership. It does not quantify the effect or set a timeline.
Did Larson say the Digg v4 rewrite caused the company’s decline?
No. Although he described the 2010 rewrite as troubled, Larson said Digg was already losing ground to Facebook and Reddit and argued the company would have faced the same fate without the rewrite.
Where can readers find the interview?
The Pragmatic Engineer lists the episode on YouTube, Apple and Spotify, and says a transcript and timestamps are available on the episode page.
Source: rss
