Chapter 11 – Managing Conflict and Internal Politics

Many engineers believe that delivering good technical solutions is enough to grow. But anyone who has reached the Staff level knows: conflict and internal politics are part of the game.

Ignoring this is like playing chess without knowing the rules—you will be surprised and lose ground.

The Myth of Neutrality

Some professionals say: “I don’t get into politics, I just do my job.”

In practice, this is the greatest naivety of all. Not taking a stand is already a stance. And, without realizing it, you end up being used in others’ games.

Conflict Is Not the Enemy

Many people fear conflict, but the truth is that well-managed conflicts are engines of innovation.

When two people disagree on a technical decision, there is an opportunity to explore different perspectives and arrive at a better solution. The problem is not the conflict itself, but how you handle it.

How a Staff Engineer Should Handle Conflict

1. Listen before reacting: A Staff Engineer who reacts instantly loses credibility. Listen, ask questions, understand the interests behind the words.

2. Focus on facts, not people: “Your idea is bad” creates enemies. “This pattern might create a cost bottleneck” focuses on the problem, not the ego.

3. Be a bridge, not a wall: Staff Engineers influence beyond their team. You will often be called upon to mediate disputes between areas.

4. Learn to disagree respectfully: A simple phrase changes everything. Instead of “You are wrong,” use “May I propose an alternative that balances these points?”

Internal Politics: The Invisible Game

Politics is not just “office gossip”—it is how decisions actually happen. This involves:

• Relationships of trust.

• Interests between departments.

• Alignment (or clash) of priorities.

A Staff Engineer who ignores this gets left out of the big discussions.

Metaphor: The Chessboard ♟️

Each leader or area is a piece on the board. Some have more movement power (rooks, queens), others less.

The Staff Engineer doesn’t need to be the king or queen, but they need to know how the game works so they don’t get sacrificed without realizing it.

Common Mistakes

• Fighting over everything: A Staff Engineer who picks every battle becomes “the difficult one.” Choose strategic battles.

• Avoiding all conflict: Being too neutral ensures your voice is never heard.

• Confusing politics with sycophancy: Politics is navigating interests, not sucking up.

Practical Examples

Case 1 – The combative senior: An engineer always challenged architectures in meetings, but aggressively. Over time, he was isolated from discussions. His technical reputation didn’t save his image.

Case 2 – The diplomatic Staff Engineer: Another engineer mediated disputes between product and engineering. Instead of imposing solutions, she built consensus based on data. Result: gained leadership trust and became a reference in strategic decisions.

Practical Exercise

Think about a recent conflict you were involved in. Ask yourself:

1. Did I focus on the problem or the person?

2. Did I truly listen to the other party’s interests?

3. Could I have mediated the situation better?

Rewrite how you could have conducted that conversation more constructively.

Staff Insight

“Staff doesn’t avoid conflicts. Staff transforms conflicts into productive agreements.”

Practical Checklist

• Do I know how to choose which battles are worth fighting?

• Can I disagree without attacking people?

• Have I been recognized as someone who helps resolve disputes?

• Am I clear about the political games in my company?

• Do I know who the key allies are who trust me?

👉 In this chapter, you learned that conflicts are inevitable and politics is inescapable. The role of Staff is not to run away, but to navigate these scenarios with intelligence, respect, and strategy. In the next one, we will talk about another differentiator of those who reach the top: how to build trust with leaders and peers, to be seen as someone everyone can bet on.