How to Stay Technical as Manager

To stay technical as a manager, particularly as an engineering manager, involves maintaining a deep understanding of technology and its applications, even when hands-on coding decreases. This technical proficiency is crucial for effective leadership, enabling managers to guide teams, make informed decisions, and understand the challenges faced by individual contributors. While the role shifts from direct implementation to oversight, continuous engagement with technical discussions and developments is essential for career development and fostering technical leadership.

The Value of Technical Proficiency for Engineering Managers

Maintaining technical proficiency is crucial for engineering managers to effectively lead teams and make informed decisions. This proficiency allows managers to understand codebase architecture and identify technical bottlenecks, which is distinct from direct coding contributions. For example, understanding the details of a system enables an engineering manager to better assist their team with both people and tech-related issues. This technical depth helps in earning the team's respect and trust, as managers are seen as knowledgeable leaders rather than just administrators.

Technical managers also need to bridge the gap between engineering and broader business objectives. This includes understanding macro trends affecting engineering and supporting senior engineers by navigating the breadth versus depth of technical knowledge. While the role shifts from hands-on work, technical acumen is necessary for providing guidance and fostering a challenging environment where teams can operate independently. As Camille Fournier notes in The Manager's Path, neglecting technical aspects can lead to issues like micromanagement or a complete detachment from the team's core work. Therefore, technical proficiency ensures that an engineering manager can effectively mentor, make critical prioritization decisions, and handle escalations.

Defining Technical Proficiency for Managers

For an engineering manager, technical proficiency moves beyond the ability to write code or contribute directly to the product roadmap. It primarily involves understanding codebase architecture and identifying technical bottlenecks. This differs significantly from the hands-on coding an individual contributor performs. For instance, a proficient engineering manager can understand the underlying details of a system, enabling them to assist their team effectively with both personnel and technical challenges. This architectural understanding is key to earning team trust and respect, positioning the manager as a knowledgeable leader rather than solely an administrator.

The focus shifts from direct implementation to a broader comprehension of how systems are built and interact. This includes grasping macro trends affecting engineering and supporting senior engineers in navigating the balance between technical breadth and depth. While the manager may not be "at the coalface" doing hands-on work, their technical acumen is vital for providing guidance, making critical prioritization decisions, and handling escalations. As James Stanier notes, "People management is necessary, but no longer sufficient on its own." This emphasizes that a manager's technical understanding is foundational to effective team leadership and strategic decision-making within a technical environment.

Challenges in Maintaining Technical Skills as a Manager

The transition from an individual contributor to an engineering manager presents several challenges to maintaining technical skills. A primary difficulty is the significant reduction in hands-on work. Managers often shift from 100% focused engineering to only 30-50% technical involvement, or even stop coding entirely, becoming full project managers. This change pushes individuals out of their comfort zone, and without proper guidance, they may struggle to adapt, leading to micromanagement or complete detachment from the team's core technical work.

Engineering managers face a demanding workload that includes coaching teams, bridging gaps between engineering and business, making critical prioritization decisions, and handling escalations. This constant pressure can lead to a disconnect from technical details. For instance, the sheer volume of management responsibilities can make finding time to engage with new technologies or deepen understanding of existing systems difficult. This can result in managers becoming less aware of specific technical needs or emerging trends, impacting their ability to provide effective guidance or support to their teams. Managers are also expected to lead based on knowledge, interpersonal communication skills, and business acumen, which require dedicated attention and practice, further diverting focus from purely technical aspects.

Practical Strategies for Sustaining Technical Engagement

Engineering managers can actively maintain their technical proficiency through several actionable methods. Participating in code reviews is a direct way to stay current with the team's codebase, understand implementation details, and identify potential issues. Engaging in architectural discussions allows managers to contribute to high-level system design and decision-making, ensuring their technical understanding aligns with the project's direction. Another effective strategy is to participate in on-call rotations, which provides direct exposure to system operations, incident response, and the real-world performance of the software. This hands-on involvement, even if not coding, ensures a practical understanding of technical challenges. Building internal tools for other functions within the organization is also a viable approach, enabling managers to apply their technical skills to solve operational problems. These activities help bridge the gap between management responsibilities and the need for ongoing technical engagement, supporting continuous professional development.

Balancing Technical Work with Management Responsibilities

Effectively integrating technical activities with management duties is crucial for engineering managers. One key strategy is to allocate dedicated time for technical engagement, even amidst a demanding workload that includes coaching teams, strategic planning, and handling escalations. Gilad Naor, an ex-Meta and Amazon manager, emphasizes that managers need to know product and business, but also support senior engineers by navigating breadth versus depth in their technical understanding. This balance means understanding codebase architecture and identifying technical bottlenecks, rather than necessarily contributing directly to the product roadmap. For example, a manager might set aside specific hours each week to participate in architectural discussions or review pull requests, ensuring they remain familiar with the team's technical challenges without micromanaging. This approach fosters mutual trust and respect within the team, as managers can provide informed guidance and support, sharing in the team's success rather than solely focusing on individual task completion.

Frequently Asked Questions

Conclusion

Staying technical as an engineering manager isn't just about personal growth; it's fundamental to effective leadership and team success. By strategically integrating technical engagement into your management routine, you can foster a high-performing team, make informed decisions, and maintain credibility. This balance ensures you remain a valuable technical resource while excelling in your leadership role.

Sources & References

• Should you Stay Technical as an Engineering Manager?
• How to stay technical as a software engineering manager
• Staying technical as an engineering manager
• Q&A on The Manager‘s Path with Camille Fournier - InfoQ
• 3 Questions for Accelerating your Technical Career as a Manager
• Engineering Managers Share the Advice That Helped Them Break Into Management | Built In
• Stay Technical as an Engineering Manager With These 3 Tips
• How Technical Should an Engineering Manager Be?
• Transition from Technical Specialist to Manager | Pryor Learning