Preface: The Accidental Engineering Manager
The reality of the Vietnamese tech industry is harsh. If you are a Senior Engineer, a Tech Lead, or a Software Architect here, chances are you will eventually be pushed into management. And when that happens, you will be entirely on your own.
There is no formal education for Engineering Managers (EMs) in Vietnam. There are no structured training programs or standardized certifications that teach you how to transition from writing code to leading people.
Instead, organizations focus their training budgets on pure technical courses - like Cloud Architecture or System Design - or they send you to generic soft-skills workshops. These workshops are often taught by business professors who have never written a line of production code. They do not understand the brutal reality of technical debt, the stress of high change failure rates, or the pressure of a broken deployment pipeline.
As a result, becoming an EM in Vietnam is an accidental and self-taught journey. You are handed a title, given a team, and expected to figure it out. You are forced to survive through a brutal cycle:
flowchart TD
A[1. Self-initiation] --> B[2. Self-research]
B --> C[3. Self-experience]
C --> D[4. Self-growth]
Many talented engineers burn out, silently struggling with the loneliness and the stress of trying to fix team workflows with no mentorship, long before they ever reach that final stage of maturity.
This playbook exists to bridge that specific educational gap. It is built to compress years of painful trial-and-error into actionable, practical strategies. You do not have to reinvent the wheel, and you do not have to do it alone.
What This Playbook Is Not
No Textbook Theories. Let me be clear: this book completely rejects generic management theories. The internet is already full of them. If you want abstract concepts written by people who don't build software, close this tab. This playbook only contains the raw frameworks, scripts, and tools that I have actually used, tested, and survived with in the trenches of real engineering teams.
Radical Transparency of Competency. This book represents my direct, unfiltered understanding of the Engineering Manager role at the team execution level. I am honest about its boundaries. I will not teach you how to write a 3-year high-level organizational strategy like a Director of Engineering or a VP. This is about managing people, untangling processes, and shipping software on the ground.
Who Is This For?
YES: This book is for Senior Engineers, Tech Leads, Technical Architects, and Software Architects transitioning into an EM role. It is written for those facing the exact pain, confusion, and identity crisis of leaving the Individual Contributor (IC) track. If you are struggling to earn respect without administrative power, or trying to understand how to measure your own value when you are no longer writing the code yourself—this is a letter of deep empathy and shared understanding for you.
NO: If you started your career as a pure manager from day one without technical roots, or if you have never felt the pain of a broken deployment pipeline, this book is not for you. The analogies, the pain points, and the approaches will simply not resonate.
Welcome to the trenches. Let's build your team.
Self-Reflection for You
Are you currently stuck in the cycle of "Self-experience", fighting invisible battles with no mentor to guide you? Let's fix that.