This sounds like one of those "soft leadership" roles, that almost always suck because you're "responsible" for something, but have little or no authority over

This sounds like one of those "soft leadership" roles, that almost always suck because you're "responsible" for something, but have little or no authority over the rest of the org. The real tech leadership (if any) are MIA or no longer in touch with the actual problems, even if they've been their forever or are the "system experts" Been there, done that, no thanks.