Engineering managers have a new job description

2026-07-27 · Source: LeadDev · Field: Technology & Digital — Software Development & Engineering, Artificial Intelligence & Machine Learning, Corporate Strategy & Leadership · Depth: Intermediate, medium

Summary

The engineering manager role has significantly evolved by July 2026, shifting from a pure coordination function, as seen in 2022, to a "player-coach" model where 37% of leaders are now deeply hands-on. This transformation, predicted by Gergely Orosz in 2024 and aligning with LeadDev's 2026 Engineering Leadership Report, merges people and team management with technical depth previously reserved for staff engineers or tech leads. The author's experience at Zenjob in 2025 exemplifies this, requiring direct code contributions and leveraging AI tools like Claude Code and MCP servers to quickly understand complex, unfamiliar systems such as invoicing architectures. A decision framework guides this hands-on approach: managers tackle small, unplanned work and investigate complex unplanned issues, while planned work remains with the team. This new paradigm fosters trust and improves team dynamics.

Key takeaway

For engineering managers adapting to evolving expectations, you must cultivate a "player-coach" mindset by actively engaging with code. Leverage AI tools to quickly understand new technical domains and contribute to unplanned work, like bug fixes. This hands-on approach builds deeper team trust and improves technical discussions. Prioritize investigating complex issues yourself, but protect your team's capacity for planned roadmap work.

Key insights

The engineering manager role is evolving into a technical "player-coach" model, requiring hands-on coding and leveraging AI tools.

Principles

• Engineering managers must maintain technical depth.
• Trust builds through proximity to technical work.
• AI tools accelerate technical skill acquisition.

Method

Engineering managers should contribute to small, unplanned work using AI tools, and investigate complex unplanned issues to understand systems before delegating or planning.

In practice

• Use AI tools (e.g., Claude Code) for code investigation.
• Tackle bug fixes and support tickets directly.
• Prioritize understanding complex system issues.

Topics

• Engineering Management
• Technical Leadership
• Player-Coach Model
• AI-Assisted Development
• Role Evolution
• Software Development Workflow

Best for: VP of Engineering/Data, Director of AI/ML, Software Engineer

Related on AIssential

• How to Thrive as an EM in the AI Era — Engineering Managers must evolve leadership and technical acumen to thrive in the AI-driven landscape.
• AI Isn’t Replacing Programmers — It’s Compressing Teams — AI increases individual developer leverage, compressing team sizes and shifting focus from code execution to judgment and problem-solving.
• The Business Engineer in the Era of AI — The Product Manager role is forking into a "Builder-PM" focused on future AI capabilities within autonomous, taste-driven cells.
• Building Trust and Credibility is the New Moat for Engineering Leaders — Engineering leaders' influence and career growth depend on establishing trust and credibility, especially amidst AI adoption pressures.
• Podcast: Beyond Code: How Engineers Need to Evolve in the AI Era — Engineers must evolve beyond pure coding to embrace AI, business context, and human empathy for sustained value.
• Managers play critical role in a company's AI transformation - and they know it — Middle managers are pivotal for successful AI transformation, driving adoption and addressing skepticism through relational change.

See Counsel's argued verdicts on the open AI decisions leaders are weighing →

Open in AIssential →

Editorial summary, takeaway, and curation by AIssential. Original article published by LeadDev.