Skip to content
Training course
Intermediate to Advanced Tailored to your team

Building AI Agents

A build-it course for engineers: what an agent actually is underneath, how to give it tools it cannot misuse, and how to know whether the thing works before a customer finds out.

Level
Intermediate to Advanced
Length
2 or 4 days
Delivery
On site, Remote, Hybrid
Group size
5 to 20 participants
See all courses

Booked privately for your team. Dates and length are agreed when you book.

What your team will be able to do

Every module ends with something participants can repeat on Monday morning, in your codebase and against your conventions.

Know when to build one

Recognise the workflows an agent genuinely improves, and the ones a plain script would handle better and far more cheaply.

Give it usable tools

Design tool interfaces an agent calls correctly the first time, without being told three times what the arguments mean.

Orchestrate multi-step work

Break a long task into steps that can be retried, resumed and reasoned about after the fact.

Evaluate it honestly

Build an evaluation set that says whether a change helped, instead of judging from the last three runs somebody happened to watch.

Contain the failures

Decide in advance what an agent may do unattended and what waits for a person, then enforce that rather than trust it.

Run it in production

Instrument an agent so you learn it is misbehaving from your own dashboards rather than from a support ticket.

Curriculum

Built around hands-on work rather than slides. The running order and the depth of each module are adjusted to the group before delivery.

75% hands-on
1

What an agent actually is

From 2 days
  • The loop underneath: plan, call a tool, read the result, decide again
  • What belongs in a tool and what belongs in the prompt
  • Memory, state and context: what survives between one step and the next
  • The workflows where a plain script wins, and why so many of them do
2

Building one

From 2 days
  • Tool interfaces that survive being called by something which cannot ask you a question
  • One agent, several agents, and the point where splitting stops helping
  • Holding state across steps without inventing a database halfway through
  • Passing work between steps, and keeping the trail readable afterwards
3

Making it trustworthy

From 4 days
  • Building an evaluation set before you need one to settle an argument
  • The characteristic ways agents fail, and which of them a test suite catches
  • Retries, timeouts and budgets, so a stuck run ends instead of spiralling
  • Where a person belongs in the loop, decided deliberately rather than by accident
4

Running it for real

From 4 days
  • Getting it running somewhere that is not somebody's laptop
  • Cost per run, and the outliers that quietly cost fifty times the average
  • Traces you can actually read at nine in the morning after an incident
  • Changing the prompt without changing the behaviour you promised

How long you book it for

Every length is drawn from the same modules. A longer booking is more of the course, not a different one.

Essentials

Intermediate

2 days

Two days to build a working agent and understand what it is doing. Enough to judge whether the use case in front of you is one an agent should handle at all.

Modules covered

  • What an agent actually is
  • Building one

Complete

Advanced

4 days

Adds everything between a demo and a system somebody depends on: evaluation, failure handling, cost, and finding out it has gone wrong before a customer does.

Modules covered

  • What an agent actually is
  • Building one
  • Making it trustworthy
  • Running it for real

Not sure which one fits? The intake call settles it, and the length can still change afterwards.

Built around your team

No two runs of this course are the same

The curriculum above is a starting point, not a syllabus. Before anything is booked I find out where your team actually stands, then rebuild the course around that. A team already running agents daily spends its two days somewhere completely different from one that installed the tool last week.

  1. Step 1

    Intake call

    A call before anything is agreed: what your team already uses, what has gone wrong so far, and what you need them doing differently afterwards.

  2. Step 2

    Stack review

    Language, framework, review process, CI. Exercises are rebuilt against your repository so nothing in the room is hypothetical.

  3. Step 3

    Curriculum reshaped

    Modules get dropped, deepened or added. You see the adjusted outline and sign it off before the date is fixed.

  4. Step 4

    Delivery and follow-up

    We run the course, then check in once the team has applied it to real work and the awkward questions have surfaced.

What gets adjusted

  • Depth of each module
  • Your stack and repository
  • Group size and seniority mix
  • Length and how days are split
  • English or German
  • On site, remote or hybrid

Is this course right for your team?

Who it is for

Backend and full-stack engineers who have called an LLM API and now want to build something that runs on its own.
Platform engineers who will own the thing once it is live and would like a say in how it gets built.
Technical product people deciding which parts of a workflow are worth handing to an agent at all.

What participants need beforehand

  • Solid working experience in Python, TypeScript or something comparable.
  • Having called an LLM API at least once, even if only out of curiosity.
  • A laptop with a working development environment and API access on the day.

How the training is delivered

Same material either way. The format changes how much of it lands in the first week.

On site

I come to your office and work with the team in the room. Usually the most effective option for a first rollout, because the sideways questions get answered as they come up.

Remote

Delivered live over video in focused blocks rather than one long day, with shared screens and hands-on exercises on your own work.

Hybrid

A day on site to get everyone moving, followed by shorter remote sessions once the team is applying it to real work and hitting real friction.

Optional add-ons Certificate of participation

There is no public schedule. Every course is booked privately for a single team, and we agree the dates together.

Luka Breitig, software engineer and AI coding trainer
Your trainer

Luka Breitig

Software engineer and AI coding trainer

I train engineering teams to work with AI coding tools, and I use the same tools to ship production software every week. The material comes out of building things, not out of a slide deck.

Before going freelance I spent six years as technical co-founder of a marketing agency, responsible for everything technical from automation infrastructure to coordinating a freelancer network. That is why the courses spend as much time on review, guardrails and rollout as they do on prompting.

  • Ships production software every week
  • Delivers in English and German
  • On site across Europe, or remote
  • Speaker at Nomad Summit, Chiang Mai

Trusted by teams & training providers

I deliver AI training for some of Europe's leading organisations and L&D platforms.

Cegos Integrata

Cegos Integrata

Commissioned trainer via leading European L&D provider

NobleProg

NobleProg

AI coding workshops via one of the world's largest IT training marketplaces

Innomotics

Innomotics

In-house AI training for engineering teams

Bots & People

Bots & People

Commissioned trainer for developer workshops

Code First Girls

Code First Girls

Course creator — 3-month AI & agentic tools curriculum

Nomad Summit

Nomad Summit

Conference speaker on AI tools, agentic development, and developer workflows (2025)

Vertiv

Vertiv

In-house AI-assisted coding training for engineering teams

Questions about this course

The things teams ask before booking. If yours is not here, ask me directly.

Enough to have called an LLM API and seen what comes back. The course does not spend time on what a model is; it starts where you want one to do something on its own. Strong general engineering experience matters considerably more here than AI experience does.

We build with one and also without one, because the point is understanding the loop rather than a particular library's opinion of it. Tell me what your team already uses and the exercises run there. If nothing has been chosen yet, this course is a good place to make that decision with evidence behind it.

Yes, and the four-day version is largely that. Bring a real workflow you are considering handing over. Some groups conclude during the course that theirs should stay a script, which is a genuinely good outcome and far cheaper to reach in a workshop than in a quarter of engineering time.

Modest, but not nothing, and agent runs cost more than chat does. I send an estimate along with the requirements once we have a date. If you would rather cap it, most of the material runs against smaller models without losing the point.

Five to twenty. Agent work is slow to run and quick to argue about, so the group has to be small enough that everybody's build gets looked at properly at least once.

Yes, in German or English. Materials stay in English because the libraries, their documentation and every error message participants will meet are in English, and a translated glossary tends to make those harder to search rather than easier.

Still not sure whether this is the right fit for your team?

Book this training for your team

Tell me the size of the group, the codebase they work in, and roughly when you want to run it. I will come back with a proposal.

Download trainer profile

Delivered in English or German, on site across Europe or remotely.