logo
Kurashizu Blogwhere ideas flow
  • Home
  • News
  • Blog
  • About
  • Home
  • News
  • Blog
  • About

© 2026 Kurashizu. All rights reserved.

Admin·New Post·Service Status
Powered by Cloudflare·03.11.26
← Back to news

The truth about being a manager

Original article
sofiakodar.github.io|5 points|0 comments|by adunk|Jun 23, 2026

The Unfiltered Reality of Engineering Management

Reflecting on my own transition into engineering management and the time I've spent mentoring others making the same leap, one thing is clear: the path from individual contributor (IC) to manager is often a smooth transition challenging and isolating experience.

"It is a journey where many of the most critical lessons are learned through trial, error, and the hard way."

Whether you are currently stepping into this role or are an engineer trying to understand your boss's perspective, here are the truths that rarely make it into the job description.

1. The Mental Load and the "Invisible" Work

Unlike coding, management doesn't always have a "stop" button. You will find that work follows you home more often than not. Your mind will be occupied by:

  • The anxiety of a looming difficult conversation.
  • The struggle to justify a questionable corporate decision to your team.
  • Navigating the treacherous waters of office politics.
  • Supporting a team member through a silent personal tragedy.

To survive, you must master the art of managing stress and stopping the cycle of rumination quickly.

2. The Social Shift: From Peer to Lead

The moment you become the manager, the social chemistry changes. Even if you strive to remain "one of the gang," the reality is that you are no longer just a peer.

The shift is often subtle at first, but it becomes glaring after your first salary negotiation or a tough performance call. You have to be mindful of your communication:

  • Casual jokes →\rightarrow→ may be seen as directives.
  • Spontaneous ideas →\rightarrow→ may be mistaken for a change in project direction.

Pro Tip: Give your team the space to lead. Encourage them to voice their ideas first so they don't simply wait for your "order."

3. The Corporate Tightrope

You will inevitably be tasked with "selling" a business decision that you personally find terrible. Professionalism and diplomacy are your primary tools here.

The ChallengeThe Manager's Requirement
Disagreeing with LeadershipRemain diplomatic and professional in public.
Emotional WeightAbsorb the stress of re-orgs and budget cuts.
CommunicationKeep emotions checked while encouraging the team.
IsolationFind at least one peer to vent to or laugh with.

4. Expanding Your Horizon

Your world expands beyond the codebase. To be effective, you must build a web of relationships across the organization.

Key stakeholders to connect with:

  1. Immediate Partners: Product Managers, Designers, and Business Analysts.
  2. Cross-Functional Departments: Sales, Marketing, IT, and Customer Success.
  3. The Big Picture: You must memorize the company's KPIs\text{KPIs}KPIs, the overarching strategy, and the data driving the business.

5. The Crisis of "Output"

As an engineer, your productivity was tangible. You could point to a shipped feature or a completed refactor. As a manager, the "output" is often invisible.

Engineer Output = Code + PRs + Shipped Features Manager Output = Meetings + Coordination + Unblocking Others

It is dangerously easy to fall into the trap of "busywork" and calendar management. Do not let this happen. Your goal is to drive actual progress, not just attend meetings. You will likely miss the "flow state" of solving a hard technical problem without the noise of rhetoric and politics.

6. The Self-Taught Curriculum

There is a common misconception that you magically know how to handle labor laws, group dynamics, or confident presentations upon promotion. In reality, you are often on your own.

Your Management To-Do List:

  • Study the basics: Vacation policies, sick leave, and parental leave laws.
  • Explore union resources and free management trainings.
  • Find a senior mentor you admire for guidance.
  • Learn the art of the 1:1 and development conversations.

7. The Feedback Loop

Many managers avoid clear feedback because it is uncomfortable. However, avoiding it creates a vacuum where dysfunctional behaviors thrive. The team knows when a "slacker" is being tolerated, and it erodes morale.

To build a healthy culture, apply this logic: Open Culture=Manager’s Vulnerability+Radical Candor\text{Open Culture} = \text{Manager's Vulnerability} + \text{Radical Candor}Open Culture=Manager’s Vulnerability+Radical Candor

  • Ask for it: Request honest, critical feedback from your reports and peers.
  • Model it: Be the first to admit when you've made a mistake.
  • Push it: Give constructive feedback upward to your own boss.

8. Respect Over Likability

You will make mistakes. You will not be everyone's favorite person. If you are a people-pleaser, this will be the hardest part.

Try to be liked by everyone →\rightarrow→ Try to be a great manager.

Being a great manager means making unpopular calls, having the "hard" talks, and occasionally letting people go. You earn respect through clarity and fairness, not by avoiding conflict.

9. The Emotional Anchor

You are now the "calm in the storm." You must absorb the team's anxiety and neutralize immature behavior. As Tanya Reilly notes in The Staff Engineer's Path, your behavior sets the blueprint for everyone else.

There will be moments of sudden realization:

"This is a problem and someone should really say something..." Realization: That someone is me.\text{Realization: } \mathbf{That\ someone\ is\ me.}Realization: That someone is me.

10. The Role of the Advocate

Finally, you are now a salesperson. You aren't just selling a product; you are selling:

  • Vision: Getting the team excited about business opportunities.
  • Value: Bragging about your team's wins to the rest of the company (which can be hard if you struggle with Jantelagen).
  • Growth: Fighting fiercely for your reports' promotions and salary increases.