There's a bit of snake oil in all of that. By any means ML is a very specialized subfield, where you need solid math basis and a deep understanding of the science behind it all. But I struggle to see the same thing for AI. If by "AI engineers" you mean someone who builds an LLM*, then it's very much just ML. If you mean someone who integrates with the LLM someone else built, then it's very much just backend work. Sur…
If you have React engineers, why couldn't you have AI engineers? I think the post is right to try to delineate the roles of "builds LLMs or other ML models" and "uses those models", as (as you noted) the skills required are very different (vs. "creates a JS framework" vs "uses a JS framework" are the same skills, just on another level). "AI engineer" is, as you say, inaccurate, but as swyx says, it's least cringy of…
We most definitely could. That's one way to prop up a cottage industry, stay relevant, command hefty salaries, and maintain that charade of importance through complexity by creating Frankenstein features in search of problems and promotions.