Ask HN: What Is an "AI Engineer"?

It doesn't mean anything. The very title "engineer" is a massive scam to begin with, especially in places like the United States where it's neither a protective title or credentialed. Any asshole can call themselves an engineer and nobody bats an eye at the absurdity.

When employers invent these titles like "AI engineer", they're looking for tech geeks who check off the keywords du jour. It's no different from the now defunct "blockchain engineer" of yesteryear. It's about broadcasting a particular skillset without really having anything to do with actual engineering. I guarantee you that the role of an AI engineer at one company will look very different in another – because it's not real.

I like these definitions:

- AI Engineer: an engineer who builds software that makes use of LLMs and other AI models, and maybe trains models (but not required)

- Agentic Engineer: an engineer who makes use of AI tools like coding agents when writing software.

AI Engineer was quite well established in the last few years to that first meaning, mainly thanks to swyx in 2023: https://www.latent.space/p/ai-engineer - which then lead to the popular AI Engineer Summit / World's Fair series of events https://www.ai.engineer/

But this year coding agents have become much more widely spread (the category didn't exist when AI Engineer was coined in 2023), so there's a possibility the term is being redefined to describe people who use those. I think that's a bad redefinition, personally.

("Agentic Engineer" is much less widely used, there may be other names for that category of engineer that I've not encountered yet.)

I wrote an entire blogpost about this ridiculous phenomenon:

https://gavinray97.github.io/blog/absurdity-of-ai-engineer-t...

When the hype cycle for "technology x" is in full swing, everybody becomes a "x engineer", sometimes without even knowing. According to some of my previous employers, I've been an "engineer" in areas such as information security, development using specific languages and/or frameworks and the like. This was of course more performative than anything else - no reputable dev shop would be caught dead not having a couple blockchain engineers on call when the customer demands.

IMHO, it not only means nothing at all, it also could mean nothing in several different ways. For example, if you take "AI engineer" to mean "someone who uses AI as a tool in their daily job as a software developer", then I'm also a "chair engineer", "coffee engineer" and "keyboard engineer" as well, since I consider those essential to be able to design and code, even if they're not part of the deliverable. Or you could go the way of champagne - "engineer is anyone who is registered by this engineering council/association, and this is done by filling certain requirements in matters of education and/or professional status".

An AI Engineer is just a mid level experienced SWE who wants to be hired in 2025-26.

If you did not get the above statement, people who changed their title to "AI Engineer" found it more easy to get jobs, at least from what I have seen.

In my mind, an AI Engineer builds products on top of LLMs, integrating them into real software (RAG, agents, evals, inference/prompt infra).

Using Claude or Copilot to write your otherwise-normal app isn't that. That's a dev with good tooling, the same way an IDE doesn't make you an "IDE Engineer" or Google a "Search Engineer." You don't title yourself after your tools.

Most of the LinkedIn relabels are that second group borrowing the title. Nothing wrong with using AI in your day to day, especially when you understand the concepts underneath, know what it does well, and know what it doesn't. But that and "makes use of LLMs in what they build" still aren't the same job.

At Databricks they’re responsible for the creation, care, and feeding of the AI agents we have in production. As these start to perform real use cases, you have to ensure they’re actually delivering the outcomes they were designed to do… and don’t drift. More often than not they’re resolving upstream data/context issues and now cost optimization with model selection and testing.

Doesn't matter, the title means nothing. What you can do does. If you can do something, does it matter what your title is?

Probably the only correct answer is to look at the job description under the title. Job titles in software engineering have always been flexible. What matters is what they actually want you to do. Even better is if you can figure out what problem they’re trying to solve because there can be better ways.

As for whether you should market yourself that way, I personally think your actual experience matters way more because most companies also haven’t hired many “AI engineers” before.

Here are a few job descriptions for reference:

https://news.ycombinator.com/item?id=47975744

https://news.ycombinator.com/item?id=48099785

https://news.ycombinator.com/item?id=47978246

Engineering involves assuming liability. I can't see how anyone can rationally assume liability for the output of any current LLM or anything likely to emerge in the near future.

Used to mean building models. Now it means you figured out which system prompt stops GPT from hallucinating your product name. The bar moved fast.

The definition is definitely changing.. or the way people are using it. AI PM used to mean something very different than what it does now as well!

AI Engineer It doesn't mean anything

Somebody soon to lose their job?

“AI Engineer” is already out-of-date. You need to be an “AI GTM engineer”.