5 Warning Signs of a Toxic Tech Manager and How to Identify Them

Yesterday a programmer complained about his leader's poor management in a large company, prompting a list of five typical flaws of bad technical managers.

1. Acting like a headless fly, thinking they lead direction

Bad managers often have no technical knowledge yet give directives, oversimplifying tasks like “just add a button” without understanding architecture, database migrations, or API compatibility, leading to absurd decisions such as unnecessary micro‑service splits that damage stability.

2. Pretending to understand while avoiding details

When teams face technical challenges, these managers offer empty platitudes, get impatient with explanations, and constantly question resource needs without grasping the underlying trade‑offs.

3. Focusing on superficial reports, ignoring core issues

They demand extensive dashboards and PPTs, neglecting code quality, architecture, and technical debt, causing teams to spend time on paperwork while debt accumulates.

4. Taking credit and shifting blame

They claim all successes as their own and blame the team for failures, eroding morale and fairness.

5. Creating information silos

They hoard knowledge, foster internal competition, and manipulate information asymmetry, leading to misguided decisions and rework.

A good technical manager may not be the top coder but respects technology, trusts professional judgment, shields the team from unnecessary interruptions, and shares both pressure and recognition.