AI engineering is the work of turning an existing AI model into a product people can actually use. You don't train the model: you connect it to an app, feed it the right data, control what it's allowed to do and make sure what comes out is safe to show.
Using a model, not building one
Training a large language model from scratch takes huge datasets, racks of GPUs and a research team. That is machine learning research, and very few companies do it. AI engineering starts where that work ends: with a pre-trained model someone else has already built, from a provider such as OpenAI or Anthropic, or an open-weight model downloaded from Hugging Face.
The closest comparison is a database. Most developers never write a database engine, but plenty of them build excellent products on top of one. An AI engineer treats the model the same way: as a powerful component with known strengths, known failure modes and a cost per use. The skills are mostly software engineering ones: APIs, data pipelines, testing, security, latency and cost.
Hosted API or open weights
There are two common ways to get at a model, and the choice shapes everything after it.
| Hosted API | Open-weight model | |
|---|---|---|
| Setup | An API key | Your own servers or GPUs |
| Cost | Pay per token | Pay for hardware |
| Control | Provider's rules | Full control of data |
A hosted API is the quickest start and usually the strongest models. Running an open-weight model yourself keeps data inside your own systems and removes per-call fees, but you now own the hardware, scaling and updates.
Wondering how this was made? How we make these