I feel like these days it's more like managing a team of seniors who are technically very competent, but may not always have the full domain context of the prob

I feel like these days it's more like managing a team of seniors who are technically very competent, but may not always have the full domain context of the problem they're solving. And/or they forget parts, if that context is too large. And/or they have a poor temporal dimension (deprecated badly maintained information polluting the context). They also tend to overengineer solutions if not guided well. If you think about it, in that respect it's not that different from managing actual human senior engineers. I think this is why focussing one's limited human attention more the input (defining clear requirements) as well as on validating the output (good CI/CD including end-to-end automated tests) is far more important than manual code reviews and micro-managing the development process.