An incomplete list of skills senior engineers need, beyond coding [x-post]

cross-posted from: https://programming.dev/post/144418

I generally don't like "listicles", especially ones that try to make you feel bad by suggesting that you "need" these skills as a senior engineer.

However, I do find this list valuable because it serves as a self-reflection tool.

Here are some areas I am pretty weak in:

• How to write a design doc, take feedback, and drive it to resolution, in a reasonable period of time
• How to convince management that they need to invest in a non-trivial technical project
• How to repeat yourself enough that people start to listen

Anything here resonate with y'all?