Hi HN,
I'm a senior level contributor at a late-stage private company. I've previously worked at a FAANG company for a decade and my take was that most software managers, especially software managers that directly managed engineering teams understood how the system worked and how services interacted with each other.
At my new gig, it seems like managers (and leadership, whatever that word means to you) seem to care about the metrics and availability numbers, but from my experience there seems to be a lack of want to understand how the system works. A lot of managers are from FAANG companies, but were building software probably in the 90s. Things have moved on. We now use declarative APIs, large distributed services, etc.
How do you deal with this type of management? A lot of questions they ask simply boil down to this isn't important because XYZ... It seems as soon as you start explaining the reasons they just stop listening.
Have you'll dealt with this? How have you helped educate managers to increase their understanding of the underlying software services that they manage?
So enjoy your autonomy, figure out what they do care about, make sure you hit their goals, and you may end up with a great role.