Engineering managers operate at the intersection of technology, people, and business. Staying current across all three domains is challenging. Newsletters offer a practical way to receive curated insights directly in your inbox, saving time while exposing you to new ideas and proven practices. But not every newsletter is worth your attention. The best ones respect your time, provide actionable content, and address the specific challenges you face as a leader of engineers.

What to Look for in an Engineering Management Newsletter

Before building your subscription list, it helps to define what makes a newsletter useful for your role. The most effective newsletters deliver one or more of the following: original frameworks and mental models for leadership decisions, real world case studies from other engineering leaders, summaries of emerging research on team dynamics and productivity, or curated links to high signal articles you might otherwise miss. Avoid newsletters that rehash generic leadership advice or primarily promote a paid product with little substance. A good newsletter should leave you with at least one idea you can apply in the coming week.

Balance Depth and Frequency

Daily newsletters rarely have the time to produce deep content, while monthly ones may feel disconnected from your current challenges. Weekly or bi‑weekly publications strike a good balance. The best ones often send a single well‑crafted essay rather than a long list of links. Quality over quantity is the rule. If a newsletter makes you think differently about a problem or gives you a concrete template to use with your team, it is probably worth keeping.

Leading Newsletters for Engineering Managers

The following newsletters have earned strong reputations among engineering leaders. They are grouped by their primary focus, though many overlap categories. Consider subscribing to one or two from each group to cover the full spectrum of your responsibilities.

Newsletters Focused on Engineering Leadership and Management

The Engineering Manager by James Stanier, author of Become an Effective Software Engineering Manager, delivers thoughtful essays on the craft of management. Each issue explores a specific aspect of leading engineers, such as giving feedback, running one‑on‑ones, or building trust. The writing is grounded in both research and Stanier’s own experience leading teams at Shopify. This is one of the most cited resources in the engineering management community.

Rands in Repose by Michael Lopp, a veteran engineering leader at Apple, Palantir, and Slack, offers a long‑running blog that also produces a newsletter. Lopp writes about leadership, culture, and the human side of engineering. His posts often use storytelling to illustrate leadership lessons, making them both memorable and practical. The newsletter sends an update each time a new essay is published, usually a few times per month.

Irregularly Scheduled by Will Larson, author of An Elegant Puzzle and Staff Engineer, provides short, dense essays on engineering management and organizational design. Larson’s writing is direct and framework‑oriented. He shares mental models for sizing teams, handling compensation, and navigating management challenges at scale. The newsletter arrives roughly once per month and is best consumed slowly.

Levels of Insight by Thorsten Ball, a former engineering manager at Screenly, focuses on the transition from individual contributor to manager. Each issue covers one practical topic, such as how to stop doing your team’s work or how to run effective planning sessions. Ball’s style is honest and direct. The newsletter started in 2020 and has built a loyal following among new and aspiring managers.

Newsletters on Team Dynamics and Culture

Software Lead Weekly by Oren Ellenbogen curates a short list of links related to engineering leadership, software craftsmanship, and team culture. Ellenbogen adds a brief personal note to each link, explaining why he finds it useful. The newsletter is weekly and takes only a few minutes to read. It is an efficient way to discover high‑quality content from across the web without spending hours searching.

Leading Eng by Andrea Breanna and Alex Parmentier is a monthly newsletter that interviews engineering leaders about their experiences and lessons learned. Each issue features a structured Q&A with a CTO or VP of Engineering, covering topics like scaling teams, managing technical debt, and maintaining culture during rapid growth. The format gives you direct access to the thinking of seasoned leaders without the noise of a blogroll.

Habits for Great Engineering Teams by Zach Lloyd, former CTO of The Warbler Group, publishes short, actionable essays on team rituals, meeting formats, and decision‑making practices. Lloyd’s advice is concrete enough that you can test it with your team in the same week. The newsletter is weekly and stays tightly focused on team habits rather than abstract leadership theory.

Newsletters with a Technical and Industry Angle

The Pragmatic Engineer by Gergely Orosz covers software engineering at scale, with a strong emphasis on how top tech companies operate. Orosz analyzes product moves, engineering decisions, and organizational changes at companies like Uber, Netflix, and Stripe. The newsletter also includes deep dives into topics like interview processes, compensation, and layoff trends. It publishes weekly and is one of the most widely read engineering newsletters in the industry.

High Growth Engineer by Jordan Cutler, formerly an engineer at Twilio and Close, shares practical career and technical advice for engineers and managers who want to grow faster. Cutler often includes templates, checklists, and frameworks that you can apply immediately. The newsletter is weekly and covers topics like time management, code review culture, and effective communication with stakeholders.

Dev Interrupted by LinearB produces a newsletter and podcast that focus on developer productivity and engineering metrics. The content is data‑driven and often includes benchmarks from their research, such as typical cycle times or deployment frequencies. If you are responsible for improving team performance, this newsletter provides evidence‑based insights rather than opinions. The frequency is weekly.

Newsletters for Senior and Staff Engineering Leaders

StaffEng by David Grijalva curates a small set of links and original content aimed at staff‑plus engineers and the managers who work with them. The newsletter covers topics like technical strategy, architecture decision records, and influencing without authority. It publishes weekly and is particularly useful for managers who oversee senior individual contributors.

Engineering Enablement by Abi Noda, CEO of DX, focuses on developer experience and internal platform teams. Each issue presents research findings, case studies, and practical recommendations for improving how engineers feel about their tools and workflows. This newsletter is ideal for engineering managers who own or influence the developer experience on their team. It publishes monthly.

How to Choose Your Mix of Newsletters

Subscribing to too many newsletters leads to inbox fatigue and reduces the likelihood that you will read any of them. A better approach is to start with two or three that match your current growth area. If you are a new engineering manager, focus on the foundational leadership newsletters like The Engineering Manager and Levels of Insight. If you lead a team in a fast‑growing startup, The Pragmatic Engineer and Software Lead Weekly will keep you informed on industry trends and team practices. For experienced leaders dealing with organizational design, Irregularly Scheduled and Leading Eng offer the depth you need.

Review your subscriptions quarterly. Unsubscribe from any newsletter that you have not opened in the past two months. Your inbox should be a tool for learning, not a source of guilt. Replace a stale subscription with one that fills a gap in your knowledge or challenges your current thinking.

Practical Tips for Getting the Most Out of Newsletters

Reading a newsletter is only useful if you apply what you learn. Set aside a specific time each week to read your curated list, such as Sunday evening or Monday morning while you plan your week. Keep a simple note‑taking method, such as a dedicated Slack channel or a note in your personal wiki, where you capture one actionable takeaway from each issue. Share interesting articles with your team during standups or in a team newsletter of your own. This turns passive reading into a team‑wide learning habit.

Finally, consider starting a newsletter yourself. Many engineering managers begin by summarizing what they learned each week and sending it to their team. It is a low‑stakes way to practice writing, clarify your own thinking, and build a habit of reflection. Over time, you may find that curating knowledge for others is just as valuable as consuming it.