# AI Roles Overview

**Fast-Changing Tools**

* New models make existing work obsolete
* Engineers adapt quickly and embrace uncertainty

**Product-First Mindset**

* UI and UX become central
* Focus shifts to application layer, not backend logic

**Broader Skillset**

* Core software skills remain important
* AI-specific knowledge becomes essential

**Speed Matters**

* Models replace months of work overnight
* Teams adapt or fall behind
* Product ships faster than infrastructure

***

> 💅 User experience trumps technical perfection
>
> 📝 Prompts beat algorithms
>
> 🚀 Ship first, optimise later

## Boundary Collapse

Traditional role distinctions fade in AI engineering:

* Data scientists collaborate directly with frontend teams
* Backend engineers work on model optimisation
* Product managers need technical AI knowledge
* Engineers must be product-minded and design-aware

### Data Scientist → AI Landscape Navigator

**Before:** Built models from scratch.

**After:** Makes AI reliable

What Changed:

* ~~Built custom ML models~~
* ~~Ran statistical analysis~~
* ~~Chose algorithms~~

What They Do Now:

* Test LLM outputs for quality
* Catch bias before users do
* Design experiments that matter
* Measure what works in production

### ML Engineer → AI Performance Evaluator

**Before:** Got models to production

**After:** Builds AI infrastructure and supporting capabilities

What Changed:

* ~~Training pipelines~~
* ~~Model deployment~~
* ~~Feature engineering~~

What They Do Now:

* Build agent frameworks
* Scale prompt systems
* Handle LLM reliability at scale
* Make AI systems fast and cheap

### Software Engineer → AI Appilcation Builder

**Before:** Built web apps

**After:** Ships AI products or features

Core Skills:

* Design conversational interfaces
* Handle streaming responses
* Build AI-first user flows
* Ship features in days, not months

Why They Win:

* Understand users and AI
* Bridge technical and product needs
* Move fast without breaking things

### DevOps Engineer → AI Platform Enabler

**Before:** Deploy and monitor services

**After:** Keep AI systems running

New Challenges:

* Model costs spike unexpectedly
* Inference needs scale differently
* AI systems fail in new ways
* Performance means response quality, not just speed

**What They Monitor Now:**

* Token usage and costs
* Model response quality
* User satisfaction scores
* System reliability under AI load


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://jamiewen00.gitbook.io/ai-engineering-handbook/roles-and-teams/ai-roles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.