The Effective Software Engineer

Chapter 7. Leadership as an Individual Contributor

You don’t need a manager title to be a leader. Senior ICs are often expected to provide technical leadership and influence outcomes across the team or even the organization, all without direct authority. This chapter is about leading from the IC position: how to guide others, drive initiatives, mentor teammates, and shape culture when you’re not “the boss.”

Leading Without Authority

By the time you’re a senior engineer, you’ll frequently find yourself in situations where you need to coordinate or influence people who don’t report to you. Perhaps you’re the tech lead on a project with engineers from other teams, or you’re proposing a new engineering standard that others would have to adopt. This is where influencing skills and informal leadership come in (as I previewed in Chapter 4).

We’ll discuss a few key techniques for leading without direct power:

Build credibility.

As repeated throughout the book, consistently delivering quality work earns you respect. If colleagues trust your technical expertise and judgment, they’ll be more open to following your lead on future decisions. This credibility is like currency for leadership. Engineers often naturally follow those with a track record of smart decisions and helpful behavior.

Communicate vision and rationale.

People need to understand the “why” to get on board. If you’re leading a project, articulate the goals and how your plan meets them. For instance, “We need to handle ...