The Revised Rules Of Engineering Management With Will Larson

TL;DR

Buying for a business?Offer from Amazon

Get business pricing on monitors, keyboards and dev gear

• Business-only prices and quantity discounts
• Tax-exempt purchasing
• Multiple users, one account, clear invoices

Create a free Business account →Free to register

As an affiliate, we earn on qualifying purchases.Hide

In an interview published by The Pragmatic Engineer, Imprint CTO Will Larson describes how engineering management expectations have changed since the 2010s. He argues that middle managers may need to return to line management and rebuild technical skills as organizations reassess leadership roles and AI changes software work.

Will Larson, CTO of Imprint, says the unwritten rules of engineering management have shifted since the 2010s, with middle managers facing pressure to reskill and in some cases return to hands-on technical or line-management work. In an interview published by The Pragmatic Engineer, Larson discusses how tighter business expectations and AI are changing engineering roles and the route from engineer to executive.

Larson’s central argument, as summarized by the publication, is that management roles that expanded in the long period of low interest rates and abundant technology investment are now under different expectations. The interview asks whether middle management has become a less secure career path and whether managers may need to refresh technical skills rather than rely on an established progression into executive roles. Larson recommends that middle managers consider returning to line management and reskilling, including learning to work with software agents.

The conversation also looks at how senior engineers and leaders are expected to choose work. Larson recalled leading an organization of about 250 people at Stripe, where some senior engineers sought more engaging problems. He described his eventual response as: “I only have suffering to offer, but this suffering is what’s going to make the business succeed.” The account illustrates a tension between individual career interests and work the organization considers necessary.

Larson also discussed earlier management practices and his own career. At Yahoo, where he worked from 2008 to 2010, he said he had only two one-to-one meetings with his manager. He recounted a separate server-approval system that led employees to trade unused machines informally. At Digg, he worked during the troubled 2010 relaunch; the interview describes performance and reliability problems after its v4 rewrite, while Larson’s view, according to the report, is that the redesign did not alone determine the company’s decline.

Pressure on the Management Career Ladder

The discussion matters to engineering managers and companies because it challenges the assumption that management is a one-way move away from technical work. If organizations expect managers to regain technical fluency and work more closely with teams, some may need to alter their career plans or develop skills they have not used recently. Larson’s comments are a perspective from an experienced engineering executive, not evidence that every company is making the same change.

The interview also links the debate to the use of AI agents in software development. The source says AI is bringing technical decision-making back toward leadership, but it does not establish how widely that is happening or how quickly jobs will change. For readers, the practical point is that expectations for managers may be shifting alongside the tools and economics of software teams.

From Low-Rate Growth to Reskilling

The interview frames the change against management practices shaped during the years after the financial crisis, when low interest rates and investment supported growth at many technology companies. It contrasts that period with current expectations for engineers and managers, though the supplied report does not quantify how many organizations have reduced management roles or changed reporting structures.

Larson brings experience from several stages of the industry. He is CTO of Imprint and previously held the same role at Carta and Calm, and worked in engineering leadership at Stripe and Uber. He has written books including The Engineering Executive’s Primer, Staff Engineer, An Elegant Puzzle, and Crafting Engineering Strategy. His examples—from sparse manager check-ins at Yahoo to the difficult Digg relaunch—provide personal accounts of how incentives and operating conditions can shape management practice.

““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

How Broad Is the Shift?

The report does not provide data on how many companies are reducing middle-management roles, asking managers to code, or changing promotion paths. It also does not establish that AI is already producing a uniform shift in engineering leadership; the discussion presents Larson’s assessment and observations.

Some details in the source are personal recollections rather than independently documented findings. The supplied material also gives no publication date for the interview, so the precise timing of the discussion cannot be confirmed from it. The future effect on engineering careers, including whether reskilling will preserve management roles or lead some people to leave them, remains unsettled.

Managers Face a Skills Test

The next test will be how individual companies define engineering management as they adopt AI tools and review team structures. Managers can watch for changes in job descriptions, expectations around technical decision-making, and whether organizations offer routes back into line management. Larson’s advice is to treat reskilling as an active career choice rather than assume seniority alone will protect a role.

The interview also mentions that Larson is hiring for engineering manager positions at Imprint, with the stated aim of using agents to rethink how software teams work. The source does not provide details about the roles or a timeline for that work. Further evidence about whether the broader management path is changing will depend on how companies organize teams and evaluate managers over time.

Key Questions

What is the main point of Will Larson’s interview?

Larson argues that expectations for engineering managers have changed and that some middle managers may need to return to line management and rebuild technical skills.

Does Larson say all engineering managers should return to coding?

No. The report describes his recommendation that middle managers consider returning to line management and reskilling. It does not say this is necessary for every manager or every company.

How does AI feature in the discussion?

The interview considers how AI agents may change software teams and says technical decision-making is moving back toward leadership. The source does not quantify the scale or pace of that change.

What remains unknown about the management career path?

The report offers no industry-wide figures on management cuts, technical reskilling, or changing promotion routes. It is not yet clear how broadly companies will adopt the changes Larson discusses.

Source: rss