Aligning with product to build the right things on a schedule everyone can live with that supports the inflow revenue via sales deals. Lots of backlog grooming,

Aligning with product to build the right things on a schedule everyone can live with that supports the inflow revenue via sales deals. Lots of backlog grooming, coordinating with other teams on their dependencies for the team (including devOps procedures and their shared libraries, new core libraries, new infrastructure, new cloud-native technologies we can use). Ensuring that what the team builds makes sense in the context of the whole company (alignment). Reporting up weekly metrics that are translated and normalized for the whole org across all teams in general (things like scrum/product team efficiency), following released product dependencies, writing change logs, release notes. Testing out APIs (which is sometimes like a variety of program management stuff at times). Learning all the black boxes of the system you're building and also all the ones you interface with, or might interface with. Then all the personnel stuff, the hiring, the care and feeding of the team, the one-on-ones, the hiring, the firing. Attending architectural discussion meetings for your own team, but as well as others. Working with MSPs on outsourced infrastructure, costs, some budgeting. Being accountable when a project goes sideways, and coming up with ways to try and get things back on track. Finding resources at the company to help out with something that might be in a gray area that's not my teams responsibility, but something we need, but is something that we're not experts in.... I still try to code a couple hours/week, but it's mostly around the undesirable stuff, or tooling (like CLI-stuff) to facilitate efficiency, generate metrics, help me play with the platform in a constructive way that facilitates my knowledge, etc...