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 Imprint CTO Will Larson about how engineering management expectations have changed since the 2010s. Larson argues that middle managers may need to return to line management and rebuild hands-on skills as AI reshapes engineering work; 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 engineering management has changed since the 2010s and why some managers may need to return to hands-on technical work. The discussion examines a shifting career path for engineering leaders as companies reconsider management layers and AI tools bring technical decisions closer to leadership.
Larson, who has held engineering leadership roles at Stripe, Uber, Carta and Calm, argues that the expectations placed on managers have changed since the period when low interest rates and abundant investment helped shape technology companies. The interview contrasts those earlier conditions with a present-day environment in which organizations face different business pressures and engineering roles are changing. The source describes this as a discussion of broader trends, not a new policy announced by Imprint or a quantified industry survey.
One central recommendation is that middle managers return to line management and reskill, including by rebuilding technical fluency. The interview raises the possibility that managing people without direct technical involvement could become a less secure career path, while stopping short of establishing how many managers face that risk. Larson has been learning to work with AI agents, and the conversation explores how those tools could alter software teams and bring technical decision-making back into leadership roles.
Larson also uses earlier jobs to illustrate how management systems can produce unexpected results. At Yahoo, he recalled, a requirement that teams justify server purchases led engineers to trade unused servers informally. At Digg, he worked on the v4 rewrite, which launched with performance and reliability problems and alienated some users. He said memory leaks contributed to the technical trouble, but argued that the rewrite alone did not cause Digg’s decline: the company was already losing ground to Facebook and Reddit, and a change to Google’s algorithm had cut traffic, according to the source’s account.
A More Technical Management Career
The interview matters to engineering managers and the people who work with them because it challenges the assumption that a management career moves steadily away from technical work. If organizations expect managers to understand AI-enabled software development and make closer technical judgments, some leaders may need to refresh skills they have not used regularly. That could change how teams divide responsibilities and how companies assess management experience.
Larson’s recommendation is a perspective from one experienced executive, not proof that all companies are reducing management roles or that returning to line management is right for every leader. Still, the discussion offers readers a concrete way to think about career resilience: management practices depend on business conditions, incentives and the work teams actually need done. The examples underline that formal processes can have unintended effects, while a manager’s job includes making necessary work meaningful even when it is not the most attractive assignment.
AI development tools for engineers
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Lessons From Digg, Yahoo and Stripe
Larson’s earlier experiences give the conversation its historical frame. At Yahoo, where he worked from 2008 to 2010, he recalled having only two one-to-one meetings with his manager. He described infrequent manager check-ins as common at the time. He also recalled a server-approval process associated with cofounder David Filo that encouraged informal exchanges between teams unable to obtain new equipment through official channels.
At Stripe, Larson led an organization of about 250 people, the source says. He recalled senior engineers seeking more engaging problems and said he sometimes had to explain that difficult or unglamorous work was what the business needed. Those stories connect individual management choices with company priorities. They also show why the interview is framed around unwritten rules: practices that once seemed normal can change as organizations grow, face new constraints or adopt new technology.
The Digg account is presented as a retrospective, not as a finding that the v4 rewrite was harmless. The launch had real reliability and performance problems, and the source says users were alienated. Larson’s view is narrower: Digg’s competitive and business difficulties predated the rewrite, so he does not believe the rewrite alone determined the company’s fate.
“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’s interview
technical management books for engineers
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
How Widely Will Roles Change?
The interview does not quantify how many engineering-management jobs may change, which companies are reducing management layers, or how quickly those shifts are occurring. It also does not establish that AI will eliminate management roles or specify which technical skills managers should prioritize. Larson’s views are based on his experience and analysis, rather than a representative study of employers.
The source says AI is changing engineering work and returning some technical decisions to leadership, but it offers no performance data or detailed account of how Imprint is deploying agents. Its mention of Larson hiring engineering managers at Imprint does not provide role descriptions or establish how those positions will differ from conventional management jobs. The scale and practical effects of the proposed reskilling remain open.
engineering management training courses
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Managers Face Practical Tests
The next test will be how engineering organizations turn these ideas into day-to-day practice: whether managers are expected to contribute directly to technical work, how AI tools change team responsibilities, and how employers support leaders who need to refresh their skills. The interview does not announce a timetable or formal changes at Imprint.
Readers can watch for further discussion from Larson and other engineering leaders, as well as concrete examples from teams adopting AI agents. For now, the report offers a set of recommendations and historical lessons rather than evidence that one new management model has become standard. The question is whether companies’ changing needs will make technical involvement a lasting expectation for managers or one approach among several.
software engineering leadership books
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the news about Will Larson?
The Pragmatic Engineer published an interview with Larson, Imprint’s CTO, about changes in engineering management and the skills leaders may need as AI reshapes software work.
What does Larson recommend for middle managers?
As summarized in the source, Larson recommends that some middle managers return to line management and reskill, including by rebuilding hands-on technical abilities. The interview does not present this as a universal rule for every manager.
Does the interview say AI will replace engineering managers?
No. It discusses how AI may change engineering roles and move some technical decisions closer to leadership, but it does not claim that AI will replace managers or provide data on job losses.
What does Larson say about Digg’s v4 rewrite?
Larson recalled that the rewrite had performance and reliability problems and alienated users. He said technical issues included Python memory leaks, while also arguing that Digg was already under pressure from competitors and a Google algorithm change.
When was the interview published?
The supplied source does not state a publication date, so the timing cannot be confirmed from the material provided.
Source: rss
Halloween Picks
halloween
As an affiliate, we earn on qualifying purchases.
