This is a great, but confusing, position to be in. You have a great start, but there is a huge different between being an amazing programmer and being a success

This is a great, but confusing, position to be in. You have a great start, but there is a huge different between being an amazing programmer and being a successful leader of programmers. In most companies, they don't really want that 10x programmer, and if that's what they are trying to hire, you don't really want the job. Technical leadership is about getting everyone on the team more productive and only jumping into the weeds, and being hands on, when you absolutely have to. A great way to do this, as a senior technical person, is code review. Every note you leave has the potential to make someone a little better at their job. That means, over the course of the year, you can make 10-20 people 10-20% better - however, doing so, without pissing everyone off, is an art and takes practice. Another place you can help is systems level thinking. Not necessarily telling people how to build something, more so about helping people understand the tradeoffs and making an informed decision. Yet another way is to use your gift to make hard things easy, so others can learn too. Every company / team has a regression towards the mean effect. But, if you can make complex things digestible to everyone, that adds real value. New engineers have to figure out how to write code and be productive. Mid-career engineers can make smart decisions, do things faster / more efficiently and every once and a while, pull a rabbit out of a hat. Great technical leaders turn more of the aforementioned into great technical leaders.