My definition is "Finds and creates the most valuable work for other engineers to do."
I really started to see the value once I moved from Principal to Manager. All of a sudden I was busy with boring manager stuff and needed an IC who could get deep into the details of our initiatives and make sure everyone's efforts were lining up. You don't need the title of Principal to do this role, of course, but ICs who see the big picture and understand what's important for the business are invaluable.
The other points in the article are on the money as well, especially around modeling and amplifying a good dev culture for the organization.
I like this definition, even if it overlaps with the PM role. In effective teams I’ve been part of, the PM and engineering leads help each other winnow down the work, with the PM making the final call for priority (except in circumstances where that doesn’t make sense).
I really started to see the value once I moved from Principal to Manager. All of a sudden I was busy with boring manager stuff and needed an IC who could get deep into the details of our initiatives and make sure everyone's efforts were lining up. You don't need the title of Principal to do this role, of course, but ICs who see the big picture and understand what's important for the business are invaluable.
The other points in the article are on the money as well, especially around modeling and amplifying a good dev culture for the organization.