Put an end to being the “go-to” engineer 

Estimated reading time: 7 minutes

Protecting your energy as an IC may feel uncomfortable, but it’s necessary. 

In every engineering org, there will almost certainly be one stand-out team member that everyone knows as the “go-to engineer.” They turn to this person when something fails, when there is a lack of information, or when decisions feel uncertain. There is nothing wrong with being the “go-to engineer.” In fact, earning this designation means you are reliable and experienced. But being the one who always has the answer comes with underlying costs, and, over time, the consistent burden of being the go-to engineer leads to burnout.

Join LeadDev.com for free to access this content