Some great points in the article. I think gaining recognition for acting in your team's best interests and long term efficiency is even harder in bigger companies (like Squarespace in this article). People won't understand why you're committing to such endeavours as an IC, even if you're past the senior level.<p>There are now more and more cross functional roles that would better fit this sort of skillset, for example technical programme management or product operations.<p>I also think any good lead or engineering manager should know how to "be more glue". If it becomes a vocation and you don't feel like stopping (or if no one who's in control at your company feels like rewarding you for it), it's maybe time to start looking elsewhere. I feel like the people I've seen embodying these skills are more likely to take on lead roles.<p>Moving to a startup could also help as you'd be able to drive alignment quicker with these skills and still get to dive in more technical tasks.
"The Staff Engineer’s Path" which the author wrote is a decent book. It covers all the things I don't like about working on software development (or being a SWE) and that's exactly why it's worth a read.
Imagine, your company has hired you as an engineer to design software systems & write code. Your performance at the company is measured by your ability to design software systems & write code. You've decided to take on the job of a project manager instead and not write code. Your contributions might be valuable, but why would you get promoted as an engineer?
I remember one client saying to me something like "So and so does a lot of X, and such and such is really churning out Y. What exactly would you say your focus is in this project?" At the time I gave a very unsatisfactory answer, but looking back, a lot of what I was doing was glue work and working across the stack. This looks like a great resource to help me next time I have trouble articulating such things.