The engineering-management resource landscape is noisier in 2026 than at any prior point. This is a curated list of resources that hold up — material that improves judgment, not material that produces excitement. The structure: what it covers, why it is worth your attention, and when it is most useful.
Newsletters
The Pragmatic Engineer (Gergely Orosz)
Long-form, evidence-based reporting on engineering practice at large tech companies. Covers compensation, technical decisions, layoffs, and process at companies that rarely talk publicly. Most useful when you are sense-checking whether your org's pattern is normal or pathological.
Lenny's Newsletter (Lenny Rachitsky)
Product-leaning but consistently relevant to engineering leadership. Especially useful for the cross-functional sections — engineering managers spend more time with PMs than the engineering literature suggests, and Lenny gives you their vocabulary.
Software Lead Weekly
Curation rather than original reporting, but the curation is unusually good. A weekly digest of the better essays in the engineering-management corner of the internet. Most useful as an antidote to algorithm-curated reading lists.
Refactoring (Luca Rossi)
Engineering management essays with an emphasis on practical patterns and lightweight frameworks. Most useful when you are introducing a new ritual and want to know how others have tried it.
Books
An Elegant Puzzle — Will Larson
The most-recommended engineering-management book of the last decade, and for good reason. Best read as a reference rather than a manual: the structural insights about org design and team size compound the longer you sit with them.
Resilient Management — Lara Hogan
The clearest writing about the human side of engineering management. Especially valuable in 2026 because the AI-tooling transition has made the human dimensions more important, not less.
The Manager's Path — Camille Fournier
Still the best stage-by-stage progression book for new and mid-career engineering leaders. The chapter on managing teams that include staff engineers is worth the cover price by itself.
Staff Engineer — Will Larson
Not strictly a management book, but essential reading for managers because it makes the staff-IC track legible. Engineering managers who understand the staff archetype delegate better.
Team Topologies — Skelton & Pais
A structural model for thinking about team boundaries and cognitive load. Most useful when your org is reorganizing or when you are setting up new teams from scratch.
Reading About the Problem Is Step One
Every resource on this list points at the same gap: distributed teams lose state between shifts. StandIn is the governance layer that closes it — handoffs, decisions, and authority captured from the tools your team already uses.
See the Workflow →Podcasts
The Pragmatic Engineer Podcast
The audio companion to the newsletter. Long-form interviews with engineering leaders at known companies. Most useful for understanding the texture of how decisions actually get made at scale.
Manager Tools
Outside the tech bubble and consequently more useful than most tech-specific management podcasts. The fundamentals of 1:1s, feedback, and delegation translate cleanly into engineering contexts.
Software Engineering Daily
Less management-focused but useful as a window into the technical decisions your engineers are reading about. Most useful for keeping your context current without reading hundreds of blog posts.
Engineering Enablement (Abi Noda, DX)
Conversations about developer experience and engineering effectiveness, often featuring leaders from companies running real programs. Most useful when you are building or refining a developer-experience function.
Communities
Rands Leadership Slack
The longest-running engineering-leadership Slack. Variable signal-to-noise but the leadership-specific channels are durably useful. Best for asking questions that benefit from many partial perspectives.
The Pragmatic Engineer Slack and Forum
Newer, more focused. Higher signal-to-noise than most engineering-leadership communities in 2026.
LeadDev community
The community surrounding the LeadDev conferences. Active on Slack and Discord, with regional meetups. Most useful when you want IRL connections in addition to online discussion.
Talks and conferences
LeadDev (London, New York, others)
The most consistently relevant engineering-leadership conference. Talks are short, practical, and unusually honest. Most useful in years when you are looking for fresh patterns.
SREcon
Not management-focused but essential reading for managers in operations-heavy orgs. The cultural patterns at high-functioning SRE teams transfer to engineering management more directly than most realize.
Newer voices worth following
Several writers have built engineering-management audiences in the post-2023 wave: writers focused on AI-agent governance, on staff-IC archetypes, on remote-management patterns. Rather than name specific individuals here, the more useful advice is to follow the citation graphs from the established voices above — they tend to surface the next generation of credible writers.
Resources to skip
Generic management books written for non-tech audiences rarely transfer well to engineering. Algorithm-curated LinkedIn engagement content is a net negative. Vendor-published "state of engineering" reports are useful for ranges of statistics but should not be your primary reading.
Frequently asked questions
Which single resource matters most for a new engineering manager?
An Elegant Puzzle by Will Larson, read slowly, with notes. The structural insights compound the longer you sit with them.
Is there an AI-agent-specific reading list yet?
The canonical reading list is still forming. The Pragmatic Engineer's coverage of agent adoption inside known companies is the best current synthesis.
How does StandIn fit alongside these resources?
StandIn is the operational counterpart to the literature: it is where the patterns these resources describe — structured handoffs, explicit authority, queryable decision records — become actual practice inside your team.
Get async handoff insights in your inbox
One email per week. No spam. Unsubscribe anytime.
Ready to eliminate your daily standup?
Distributed teams use StandIn to start every shift with full context — no standup required. Engineers post a 60-second wrap. The next shift wakes up knowing exactly what to work on.