17 free courses — no signup wall
Architect-led enterprise cloud, security & AI
320+ downloadable toolkits — instant delivery
Skip to content
LLM engineer

LLM Engineering

Prompting, context, embeddings, and evaluation — the craft of making a model behave predictably.

Who this is for

Engineers who own model behaviour: quality, grounding, and the regression suite behind it.

What you should be able to do

Hold a model to a measured quality bar with an eval set that fails the build when it slips.

Career ladder

The titles this track maps onto. Levels differ between companies — the useful part is the direction, and what each step adds to the one before it.

  1. Prompt Engineer
  2. LLM Engineer
  3. Senior LLM Engineer
  4. Staff LLM Engineer
  5. Principal LLM Engineer

Tech stack

What the work is actually done with. Grouped by the job each tool does, so the list reads as a system rather than a pile of names.

Prompting
System promptsStructured outputsTool schemas
Context
ChunkingRerankingContext windowsToken budgeting
Adaptation
LoRAFine-tuningDistillation
Vectors
pgvectorPineconeWeaviateMilvusQdrant
Evaluation
Golden setsLLM-as-judgeGuardrailsHallucination scoring

The delivery flow

The order the work actually happens in. Each step is where a decision gets made and written down, not a chapter heading.

  1. Task definition
  2. Prompt draft
  3. Structured output schema
  4. Retrieval grounding
  5. Golden set
  6. Automated eval
  7. Guardrails
  8. Regression gate

Reference repository structure

A starting layout for this track. The directories are the ones that get added late and hurt — decisions, evals, policy, lineage — promoted to the top level where they are visible.

llm-workspace/
├── prompts/
│   ├── system/            # one file per persona, versioned
│   ├── task/
│   └── CHANGELOG.md       # every prompt change, with the eval delta
├── schemas/               # structured output + tool definitions
├── context/
│   ├── chunking/
│   └── rerank/
├── evals/
│   ├── golden/            # inputs + expected properties
│   ├── judges/            # rubric prompts
│   └── report/            # scored runs, kept for comparison
├── guardrails/            # input and output validators
└── experiments/

Primary sources

The standards, framework documents, and vendor references this track is built against. Go here when you need the authoritative wording rather than a summary — in a security review or an audit, the source is what counts.