If I build and maintain chains of Google's APIs calls to develop an application that performs X, Y, and Z then I would say that I'm an "application developer", not a "Google API engineer". I mean I assume there is going to more to the application than just a pile of API calls.
So maybe a good name for this course would be "Building applications using Large Language Models", which is actually how the course is described in the intro.
Or maybe it's just a modern expected skill, and those who choose not to incorporate it in their workflow are left to struggle to keep up, just like if someone refused to use Google in 2001. After all, it's not like I list Google-fu in the skills section of my resume, despite that being a skill I use every day and find indispensable.
Yeah I agree with this. The tool is not the product or profession.