Becoming an Engineering Manager Without Losing Your Technical Soul

Item: Becoming an Engineering Manager Without Losing Your Technical Soul
Rating: 4
Author: PostSingularity Institute

by Paul Williams

Humanities, Social Sciences & Thought Economics & Finance KJMManagement and management techniques KJMBManagement: leadership and motivation

🎙 Paul Williams 👥 227K 📅 August 13, 2026 ⏱ 60 min 👁 124 📄 expert opinion 🧭 2026-08-13

Available in: English (current) Français

Keywords

engineering managertechnical skillsleadershipcode reviewmentoring

Summary

In this talk at NDC Toronto, Paul Williams, an engineering manager at Bloomberg, shares his personal reflections on transitioning from a hands-on coder to a technical leader without losing one’s technical identity. He begins with his background, starting to code at 15 and progressing through various technical roles, emphasizing his deep love for coding. He then recounts a memorable debugging incident involving a real-time data issue in the Bloomberg terminal, which turned out to be caused by anti-malware software intercepting internal TCP/IP signals. This story illustrates how technical depth across all levels of an organization can be crucial. Williams poses six questions about the value of engineering managers, addressing fears of losing technical skills and identity. He argues that managers bring value through project management, people management, mentoring, recruiting, scaling, empowering teams, solving problems together, designing systems, advocating for the team, and setting vision. He emphasizes the importance of retaining technical knowledge to effectively guide and empower teams, and shares a quote from Larry Page: ‘Put the best people on the most important work and get out of the way.’ He also discusses the balance between writing code and managing, and the importance of letting go of the critical path. The talk concludes with practical advice on how to stay technically engaged while leading, such as participating in code reviews, debugging, and system design.

224 words

Critical Evaluation

Value of the Information & Strength of the Argument

The talk provides valuable insights into the role of an engineering manager, drawing on the speaker’s extensive experience. The argumentation is coherent and persuasive, using a real-world case study to illustrate the importance of technical depth. The speaker effectively addresses common concerns about losing technical identity and offers practical advice on maintaining technical skills. However, the arguments are largely based on personal anecdotes rather than empirical evidence, which may limit their generalizability.

Scientific Rigor, Source Quality, Title Accuracy

The talk is based on the speaker’s personal experience and does not cite formal sources. The title accurately reflects the content, which focuses on the transition to management while retaining technical skills. The speaker mentions a podcast with Larry Page but does not provide a specific reference. The talk is well-structured and the content is credible given the speaker’s background, but the lack of citations reduces its scientific rigor.

156 words

Title / Content Match

The title accurately reflects the content, which focuses on how engineering managers can maintain technical depth and identity.

Quality & Reliability

7/10

The talk is based on 20 years of personal experience as an engineering manager, providing practical insights and a real-world case study. However, it is largely anecdotal and lacks formal citations or empirical data.

Key Moments

Markers derived by PSI from the transcript: the creator did not define chapters.

Cited Sources

NDC Conferences — Conference website where the talk was recorded.
NDC Toronto — Specific conference event page.

Concurring Sources

Larry Page on leadership — Reference to the quote about putting the best people on important work.

Contribution & Novelties

The talk offers a personal perspective on maintaining technical skills as an engineering manager, illustrated with a compelling real-world debugging story. It provides practical advice on balancing management and technical work, and emphasizes the importance of technical depth at all levels of an organization. The speaker’s 45 years of coding experience adds credibility.

Pour aller plus loin :

Engineering management — Overview of the field.
Technical leadership — Concepts and practices.
Mentorship — Importance in professional development.

77 words

Radar Profile

The radar profile shows high scores in quantity and quality of information, moderate technical level, and slightly lower reliability due to lack of formal citations. This indicates a well-informed but anecdotal talk.

Reliability 6/10