I'm +1, Joe has been central in some of our thorniest API designs / discussions / decisions over the last few years, and is helping lead several of the efforts to simplify and consistently apply conventions and guardrails.
He has experience with our various flavors of APIs (REST, config, CLI, proto/grpc), and thinks well about making API surface as simple as possible (but not simpler), as well as multidimensional skew, different types of clients/actors, data flow, ratcheting, rollout, etc (his production readiness review hat serves him well here).
Jordan