Surviving a Toxic Manager in Tech
"People leave managers, not companies." This cliché is repeated endlessly in the Indian IT sector because it is overwhelmingly true. Whether you are at an early-stage startup or a massive service-based MNC, a toxic manager can halt your career progression and severely impact your mental health.
Toxic managers in tech usually fall into three archetypes: The Micromanager (who needs daily status updates on 15-minute tasks), The Credit Stealer (who presents your code as their architecture), and The Burnout Driver (who texts you on weekends).
Here is a practical guide to handling them without sabotizing your own career.
Strategy 1: The "Paper Trail" Defense
If your manager frequently changes requirements, denies previous instructions, or blames you for missed deadlines that they caused, your memory is no longer sufficient. You need documentation.
- The Post-Meeting Email: After every 1-on-1 or architectural discussion where your manager gives verbal instructions, send a summary email: "Hi [Name], just confirming our discussion. Based on your instructions, I will drop feature X and focus entirely on feature Y for Friday's release. Let me know if I misunderstood."
- Jira is Your Shield: Do not write code for tasks that are not documented in Jira (or your tracking tool). If they ask for a "quick favor," say: "Sure, can you create a quick ticket for that so I can track my sprint velocity?"
Strategy 2: Managing the Micromanager
Micromanagers are usually driven by anxiety and a lack of control, not malice.
- Proactive Over-Communication: The best way to get a micromanager off your back is to give them information before they ask for it. Send a daily end-of-day summary on Slack outlining exactly what you accomplished and what you are doing tomorrow. Overwhelm them with transparency.
- Establish Boundaries Early: If they Slack you at 10 PM, do not reply until 9 AM the next day. If you reply at night once, you have established a precedent that you are available 24/7.
Strategy 3: Handling the Credit Stealer
This is common in large MNCs where Engineering Managers present the work of their team to higher leadership.
- Visible Contributions: Ensure your name is attached to the actual work. Be active in public Slack channels. Answer technical questions in group settings.
- The "We" Correction: If your manager takes credit in a meeting, politely interject with a collaborative correction: "Yes, the team worked really hard on this. When I was implementing the caching layer that [Manager's Name] just mentioned, I found that..." This forces them to acknowledge your specific contribution without initiating a direct confrontation.
Strategy 4: The HR Escalation (The Nuclear Option)
Going to HR should be your absolute last resort.
- The Reality of HR: HR exists to protect the company. If your manager is a high-performing "10x engineer" or holds significant political power, HR is unlikely to side with a junior developer without undeniable proof of harassment.
- When to Escalate: Only escalate if the toxicity crosses into legal territory (harassment, discrimination, verbal abuse) and you have documented proof (emails, Slack screenshots, witness statements).
The Ultimate Solution: The Exit Strategy
You cannot fix a toxic manager. You can only manage them while you plan your escape.
- Do Not Quit Without an Offer: Unless your mental health is in severe jeopardy, do not resign impulsively. Use the frustration as fuel to grind LeetCode and System Design on the weekends.
- Internal Transfer: In large MNCs, quietly network with managers on other teams. Often, you can request an internal transfer to a different project without ever needing to confront your current toxic manager.
- The Silent Checkout: While interviewing, switch to "quiet quitting" (doing exactly what your job description requires and nothing more). Save your mental energy for the job hunt.
