Skip to content
TailoredMinds

AI role profiles.

What good looks like for the roles that build AI, and how we help you define them.

Six roles, defined.

Each profile covers what the role does, the skills it needs, and what we look for when we shortlist for it.

Applied AI / LLM engineer

Ships features on top of foundation models: retrieval, agents, evals.

What they do

An applied AI or LLM engineer builds product features on top of foundation models. They design the retrieval, prompting, tool use and agent logic, then build the evaluations and guardrails that keep those features dependable in production. They usually work in the product codebase, close to users, rather than training models.

Core skills

  • Retrieval-augmented generation: chunking, embeddings, vector and hybrid search, re-ranking
  • Prompt and context design, structured outputs and tool or function calling
  • Agent and workflow orchestration, with clear limits on what the model may do
  • Evaluation: test sets, model-graded and human review, regression checks on every change
  • Guardrails, safety and handling of sensitive data
  • Production engineering: latency, cost per request, caching, fallbacks between model providers
  • Strong general software engineering, usually in Python or TypeScript

Signals we look for

  • An LLM feature they shipped to real users, and what changed after launch
  • How they measured quality, beyond "it looked right in testing"
  • A failure they found in production and how they fixed or contained it
  • Trade-offs they made between quality, latency and cost

Often confused with: Machine learning engineer. An LLM engineer builds with models; an ML engineer trains and serves them.

Machine learning engineer

Trains, tunes and serves models that hold up in production.

What they do

A machine learning engineer trains, tunes and serves models. They turn a modelling problem into data, features, training runs and an evaluation plan, then ship the model behind a reliable service and keep it accurate as the data changes.

Core skills

  • Python and the core ML stack: PyTorch or TensorFlow, scikit-learn, NumPy and pandas
  • Data preparation, labelling strategy and feature engineering
  • Training, fine-tuning and hyperparameter search, including fine-tuning pretrained and foundation models
  • Offline evaluation, metric choice and error analysis
  • Model serving, batch and real-time inference, and optimization for latency and memory
  • Monitoring for drift and degraded accuracy, and retraining

Signals we look for

  • A model they took from experiment to production, and how it performed once it was live
  • The metric they chose, and why it matched the business problem
  • Error analysis that changed the data or the model, not just the hyperparameters
  • Comfort writing production code, not only notebooks

Often confused with: AI researcher. An ML engineer makes known methods work reliably in production; a researcher develops and tests new methods.

MLOps & AI platform

Pipelines, GPUs, observability and cost control.

What they do

An MLOps or AI platform engineer builds the infrastructure that lets teams train, deploy and run models safely. They own the pipelines, compute, deployment paths and monitoring, so model work is repeatable, observable and affordable.

Core skills

  • Training and data pipelines, workflow orchestration and experiment tracking
  • Model registry, versioning and reproducible environments
  • Containers and Kubernetes, infrastructure as code, CI/CD for models
  • GPU scheduling and capacity, inference serving and autoscaling
  • Observability: latency, errors, drift and model-quality metrics
  • Cost control and usage tracking for compute and model APIs
  • Access control, secrets and audit trails for models and data

Signals we look for

  • A platform or pipeline other engineers actually adopted, and what it replaced
  • A deployment path from commit to production model, including rollback
  • A cost or capacity problem they diagnosed and fixed
  • Incident experience: what they monitored, and how fast they knew something was wrong

Pairs well with: Machine learning engineer. and **Applied AI / LLM engineer.** The platform is what lets both ship without rebuilding infrastructure for every model.

Data engineer

The clean, governed data every model depends on.

What they do

A data engineer builds the pipelines and models that turn raw data into clean, governed, reliable datasets. Analytics, machine learning and AI features all depend on that data being correct, documented and on time.

Core skills

  • SQL and data modelling for warehouses and lakehouses
  • Batch and streaming pipelines, with orchestration and scheduling
  • A general-purpose language for pipelines, usually Python, Scala or Java
  • Data quality: tests, contracts, freshness and lineage
  • Governance: access control, privacy and retention
  • Preparing data for ML and AI, from feature tables to document collections for retrieval

Signals we look for

  • Pipelines they own that other teams depend on, and how they keep them reliable
  • How they catch bad data before a dashboard or a model does
  • Schema changes and migrations handled without breaking downstream users
  • Clear reasoning about batch versus streaming for a given need

Pairs well with: Machine learning engineer. Models are only as good as the data a data engineer delivers.

AI product manager

Turns model capability into a product people trust.

What they do

An AI product manager decides what an AI feature should do, for whom, and how good is good enough to ship. They turn model capability into a product people trust, working with engineers on evaluations, failure modes and cost, and with users on where AI helps and where it shouldn't act alone.

Core skills

  • Product discovery and problem framing
  • A working understanding of how models behave: uncertainty, errors, latency and cost
  • Defining quality: success metrics, evaluation criteria and launch thresholds
  • Designing for failure: human review, fallbacks and clear user feedback
  • Responsible AI, privacy and policy considerations
  • Prioritizing a roadmap across model, data and product work

Signals we look for

  • An AI feature they launched, and the quality bar they set before launch
  • A time they chose not to ship, or narrowed scope, because the model wasn't ready
  • How they used evaluation results and user feedback to decide what came next
  • Clear writing: specs that engineers and stakeholders can act on

Often confused with: a general product manager. An AI PM also owns model quality, evaluation and failure modes, not just features and timelines.

AI researcher

Explores what's next and brings it back to the roadmap.

What they do

An AI researcher designs and runs experiments to develop new methods or significantly improve existing ones, from model architectures and training techniques to evaluation. In a product company, they also bring what works back to the roadmap, so research turns into capability the team can ship.

Core skills

  • Deep knowledge of machine learning and the relevant mathematics
  • Experimental design, baselines, ablations and statistical rigor
  • Reading, reproducing and extending published work
  • Strong prototyping in Python with a deep learning framework
  • Training at scale and analysing results
  • Writing and presenting findings clearly

Signals we look for

  • Research questions they defined, not only executed
  • Results they reproduced or extended, with honest reporting of what didn't work
  • Published papers, preprints or open-source work, where available
  • Research that made it into a product or a team's practice

Pairs well with: Machine learning engineer. The researcher proves a method works; the ML engineer makes it reliable in production.

Hiring for one of these roles? Brief it once and we'll help you define it.

Start hiring

Put a whole network on your next hire.

Tell us who you're looking for. Our talent network and recruiters take it from there.

Talent? Join freeRecruiter? Join the workforce