Engineering Career Scaling Playbook Goes Viral
A new playbook for scaling from managing 10 engineers to leading 100+ is gaining traction, detailing the transition from problem-solving to org-driving roles. The guide by Thiago Ghisi identifies where most engineering careers stall and provides frameworks for breaking through. Multiple posts are also warning against rushing into management without proper preparation.
A core element of Thiago Ghisi's advice is the "Engineering Manager Archetypes," a framework for understanding leadership styles. It plots managers on two axes: their focus on people versus execution, and their inclination towards stability versus change. This creates four main archetypes: the "Operator" (stability and execution), the "Guide" (people and stability), the "Driver" (execution and change), and the "Catalyst" (people and change). Each archetype has both a productive and a "shadow" mode. For example, a "Guide" can be a nurturing "Mentor" or a pampering "Comforter," while a "Driver" can be an inspiring "Finisher" or a punishing "Dictator." The framework encourages leaders to understand their natural tendencies and adapt their style to what their team needs at a particular moment. Ghisi argues that this self-awareness is crucial for scaling leadership effectively. The transition from a hands-on engineering role to a management position is a significant career shift, not just a promotion. Many new managers struggle because the skills that made them great individual contributors, such as deep technical focus and independent problem-solving, do not directly translate to leadership. The new role demands a completely different skill set focused on communication, conflict resolution, and team development. One of the most common challenges for new managers is letting go of coding and technical decision-making. There's often a tendency to fall back on familiar technical tasks when faced with the ambiguities of management. This can lead to micromanagement and prevent team members from taking ownership and growing. The manager's new "product" is the team and its output, not their own code. The shift in how success is measured is also a major hurdle. Engineers are used to concrete feedback on their work, such as code reviews and bug counts. For managers, success is less tangible, defined by the team's overall output and long-term growth, which can feel unproductive and disorienting at first. This difficulty is compounded by a lack of formal training. Many engineers are promoted into management without guidance on how to conduct effective one-on-ones, give constructive feedback, or manage performance. This lack of preparation is a primary reason why the transition can be fraught with challenges, leading to burnout for the manager and a negative impact on their team.