Indeed AI jobs do require data skills and coding experience. The job posts point to Python, SQL, data analysis, and enough coding ability to solve technical problems, not just talk about AI in broad terms.
I keep coming back to that because the gap is easy to miss. Many people hear “AI job” and picture model ideas, prompt work, or product talk. The Indeed listings tell a firmer story. The work is usually tied to data, code, and systems.
What stands out first is the data side. Current Indeed postings for AI-related roles ask for things like data analysis, data sensitivity, data pipelines, and work with data tools. Some listings name Python and SQL together, which is a strong sign that the role is meant to touch both code and data at the same time. That is not a soft skill set. It is a working skill set.
The coding side is just as clear. Indeed listings mention programming languages, code quality, and code tests. Some roles ask for Python, JavaScript, or another language. Others point to engineering habits like clean code, Git, and cloud tools. In plain terms, these jobs are not for people who only use AI tools from the outside. They want people who can build, check, and fix things.
That makes sense when I look at the kind of tasks these jobs describe. AI systems run on data. They need data cleaned, shaped, and moved. They also need code that can call models, handle outputs, and keep the whole process stable. So the two skills go together. Data skills help a person work with the input. Coding helps a person make the system do something useful.
There is also a useful split inside the AI job market. Some roles are more research heavy. Others are more data engineering or software engineering heavy. But even when the role is not a pure software job, Indeed listings still tend to ask for coding and data comfort. That is the main fact a reader needs. The label “AI job” does not remove the need for technical basics. It often raises it.
I think that is where hype causes trouble. The job title sounds new, but the skills are familiar. Python still matters. SQL still matters. Data still matters. The work may use newer tools, but the base layer looks a lot like other technical roles.
One honest limit matters here. Indeed listings change often, and job titles are not fixed across companies. One employer may mean AI product work. Another may mean ML engineering. Another may mean data work with some AI tools added. So the exact mix of skills is not the same in every posting. But the pattern is steady enough to trust. If a role is called AI on Indeed, data skills and coding experience are very often part of the ask.
For a learner, that changes how the question should be read. The real issue is not “Do AI jobs need coding?” The real issue is “How much coding and data work does this role expect?” That answer depends on the post. But the base expectation is usually technical, and often more technical than the title suggests.
That is the simple reading I would trust. Indeed AI jobs are not built on vague interest in AI. They usually ask for real data skill and real code skill. The title is broad. The work is narrower and harder.
The Dravelo Field Notes fits that same idea well: one practical technical idea, one learning decision, and one useful network resource each edition. That is the kind of small, honest help that makes a hard job market easier to read.