Yea, as someone who is more outspoken and has passible soft skills, I often find myself accidentally becoming team leads in ways that often end up making me a worse engineer. If I'm the only person who understands the work and can express it in legible english, I end up writing all the tickets because the Project Manager can't do it as well as me. I end up leading meetings because I understand the architecture reasonably well and can put it into words. And yet, I end up looking bad on paper because I complete very little technical work because I'm doing half of the job of 3 managers.
Sure, I'm aware of it, but having your team abjectly fail isn't good for your continued job prospects either. You shouldn't be the hero, but you also don't want to have your team get fired for want of you spending 2 hours of work a week keeping it on track.
I just want to urge you to be very careful with that. A job is - most often just a job. If you are too personally invested, you may need to take a step back and see if everyone around you is as invested.
I am not saying this from the perspective of someone who is slacking off at their job but from the perspective of someone who did too many heroics and only nearly avoided burn out. If your team gets fired because of one persons work/efforts or the lack thereof then something is seriously wrong AND there is a risky bus factor of 1. Please take my advice, the grass is always greener on the other side.
