Titles lie, work does not
"AI Engineer" means at least six different jobs depending on who wrote the posting. Read the responsibilities section, ignore the title. Here are the roles that actually exist, described as they feel on an ordinary Tuesday rather than in a brochure.
Data engineer
You move data from where it is created to where someone can use it. Pipelines, schemas, backfills, an alert at 03:40 because last night's job died on a row containing a comma.
A Tuesday: a dashboard shows Monday's orders as zero. You trace it to a payments provider that renamed a field from order_id to orderId on Saturday without telling anyone. You fix the parser, replay two days of data, and write a note so the next person loses ten minutes instead of three hours.
There are more of these jobs than any other kind on this list, in every country. Least discussed, most stable.
Data analyst
SQL, spreadsheets, dashboards, and the question behind the question. Someone asks for "signups by region". What they are actually deciding is whether to keep paying for the Nairobi campaign. Most of the skill is finding that out before you write the query, because the query takes four minutes and the wrong question wastes a week.
This is the most common first job in the field for people who did not study computer science.
ML engineer
You put models into products and keep them alive: serving, latency, retraining, monitoring, rolling back when the new version is quietly worse. Training models is a slice of it. Training one from scratch is rare outside research labs.
A Tuesday: recommendations got 400ms slower on Friday and nobody knows why. You find a feature lookup making one database call per item instead of one per request.
AI product manager
You decide what gets built and what "good enough" means — which in this field means writing down how the system will be measured before it exists. Also: arguing with legal about which data may be used, cutting scope, and telling people no in a way they can accept.
Prompt and evaluation work
The newest and least settled corner. The durable half is not writing prompts, it is evaluation: assembling the test cases that decide whether a system ships, grading outputs, hunting failure modes, turning "this feels off" into a number someone can act on. Job titles here change every eighteen months. The work does not.
Research scientist
Reading papers, running experiments that mostly fail, writing up the few that do not. A small number of jobs, concentrated in a few dozen labs and universities worldwide, nearly all wanting a PhD. Keep it on your map. Do not plan your life around it.
The ratio nobody prints
Picture a 300-person fintech in São Paulo with a genuine data team: about four data engineers, six analysts, two ML engineers, one product person who covers AI alongside three other things, and zero researchers. Multiply that shape across thousands of companies and you have the actual job market.
If you are choosing where to aim, aim where the jobs are and where you can produce evidence fastest. Analyst and data engineer are the two widest doors. ML engineering is far easier to reach from a data engineering job than from a course.
What they all share
Every role above is mostly one activity: something is wrong with the data and you have to find out why. Courses skip this because it does not demo well. Employers pay for it because it is where the time goes.
Before you move on