Skip to content
AI training for engineering teams

AI agents for your engineering team.

Ship twice as much. Keep the headcount.

  • 1 to 4 days
  • On site or remote
  • English or German
See the courses
The same three engineers merge two pull requests each on their own, and four each once they work with AI agents.

Trusted by teams & training providers

I deliver AI training for organisations and L&D providers.

Cegos Integrata

Cegos Integrata

Commissioned trainer via a 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

financial.com

financial.com

In-house Cursor training for the engineering team

Digitality Agency

Digitality Agency

Training for the design team in using LLMs for coding work

Bots & People

Bots & People

Commissioned trainer for developer workshops

Code First Girls

Code First Girls

Course creator: a 3-month curriculum on AI and agentic tools

Nomad Summit

Nomad Summit

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

Vertiv

Vertiv

On-site workshops in AI-assisted coding for engineering teams

Deutsche Telekom

Deutsche Telekom

Hands-on AI coding training for enterprise engineering teams

What clients say

Feedback from the teams I have worked with.

We had a Cursor AI training with Luka. He is a highly competent trainer who answered all our questions thoroughly and adapted the course to our needs and preferences. I highly recommend working with him!
Herbert Reiter

Herbert Reiter

Chief Technology Officer (CTO)

financial.com

Where the extra output comes from

Agents take six kinds of work off every engineer's week, and the freed hours go into shipping.

Illustration: in an engineer's week with agents, the six kinds of work below take up far less of the week, and the time freed up goes into shipping more.

  • Feature work From ticket to tested code.
  • Code review A first pass on every pull request.
  • Tests The ones nobody had time to write.
  • Migrations and upgrades Carried through hundreds of files.
  • Unfamiliar codebases Mapped before anyone edits it.
  • Bugs From stack trace to proposed fix.

Same headcount. More shipped every week.

Training topics

Hands-on, on your own codebase. Further topics on request.

The core

Agentic development with Claude Code

Hand over a whole ticket, not a prompt, and keep several agents running at once.

The engineer briefs the agent with a task and its context. The agent plans, edits the code and runs the tests, repeating until they pass, and reaches the issue tracker, documentation, databases and internal APIs through MCP. The engineer then reviews the change and merges it.
Engineer
Brief the task
Ticket plus context
Agent
Plan Edit code Run tests

Repeats until the tests pass

Connected via MCP
  • Issue tracker
  • Docs
  • Databases
  • Internal APIs
Engineer
Review
Merge
Same workflows in Claude Code Cursor Codex GitHub Copilot

Around the core

  • MCP and internal tools

    Agents with your team's context

  • Parallel work with subagents

    Several agents, one engineer reviewing

  • Review and quality at volume

    Guardrails that hold as output rises

  • Rolling agents out across the team

    From a few enthusiasts to the whole team

Briefing leadership too? AI training for leadership teams

Is this for your team?

Booked by a company for one engineering team, run on its own codebase.

A good fit

  • Backlog outgrowing the team
  • No budget for more engineers
  • AI licences used as autocomplete
  • 5 to 20 engineers

Not a fit

  • A self-paced course for one person
  • Software built for you
  • Agents merging unreviewed code

How far is your engineering team with AI agents?

Ten quick questions on setup, adoption, integration and results. You get a score for each and the engineering training that fits where your team stands.

Check your team

Courses for engineering teams

Each course has its own curriculum, prerequisites and lengths, and every booking is adapted to your stack. Pick your team's tool, or start with the fundamentals.

Beginner to Advanced

Claude Code Training

Drive Claude Code through real feature work: steering it with project instructions, keeping diffs reviewable, and setting guardrails that hold up in a production codebase.

1, 2 or 4 days View course
Beginner to Advanced

Cursor Training

Get a team genuinely fluent in Cursor: which mode to reach for, how to teach it your conventions, and how to keep a twelve-file change reviewable.

1, 2 or 4 days View course
Beginner to Advanced

GitHub Copilot Training

Move a team past tab completion into Copilot's chat, edit and agent surfaces, its role in code review, and the enterprise controls around all of it.

1, 2 or 4 days View course
Beginner to Intermediate

Codex Training

Hand engineering work over to Codex and get it back finished: task briefs, parallel runs, environment setup, and reviewing a change nobody watched being written.

1 or 2 days View course
Beginner to Advanced

AI Coding Training

Decide how your organisation codes with AI: comparing the tools honestly, agreeing the practices that transfer between them, and running a rollout that produces evidence.

1, 2 or 4 days View course
Intermediate to Advanced

Building AI Agents

Build agents that survive production: tool design, orchestration, evaluation, and the guardrails that decide what happens when one goes wrong.

2 or 4 days View course
Advanced

MCP Server Training

Build a working MCP server against your own systems, from the protocol up to auth and distribution.

1 to 2 days View course
Intermediate to Advanced

Self-Hosted LLM Training

Run language models on your own infrastructure: choosing a model, sizing the hardware, serving it to a whole team, and keeping the data inside the building.

1 or 2 days View course

Taught by an engineer who studied people

Engineers listen to someone who ships code. Habits change with someone who knows why they formed.

Luka Breitig

Engineer and founder

6 years as co-founder and CTO

Tymeslot and In A Nutshell, built with agents

Studied people

Top 2% in a master's in management

BSc Psychology

Trains teams for Deutsche Telekom (via Cegos Integrata) Innomotics Code First Girls NobleProg Bots & People

How a booking works

Three steps. The first is a free call.

  1. 01

    Free call

    Thirty minutes on your stack and how much agents can take on.

  2. 02

    Tailoring

    Rebuilt around your repositories and real tickets from your backlog.

  3. 03

    Training on your codebase

    On site or remote. The team leaves with agents doing real work.

Further reading

Articles from the blog on the topics behind this service

Do LLMs really write better Elixir than Python?

Do LLMs really write better Elixir than Python?

April 2, 2026
Luka Breitig

A Tencent benchmark ranked Elixir #1 for LLM code generation. As an Elixir developer, I dug into the data: the truth is more nuanced than the headline, but the structural advantages are real.

Questions engineering leads ask

The ones that usually come up before a booking.

GitHub Copilot made its name with line-by-line autocomplete: it suggests the next few lines as you type. Agentic coding works differently. You describe a goal, and an agent plans the approach, reads your codebase, writes code across several files, runs the tests and iterates on errors. Claude Code works this way, and so do the agent modes now built into Copilot, Cursor and Codex. For a team, the difference is scale: an engineer stops typing every line and starts directing several pieces of work at once.

It is the goal the training is built around, not a guarantee. The gain comes from work an agent can carry end to end: well-specified features, tests, migrations, first-pass reviews and bug reproduction. A team whose backlog is full of that work gets closest; a team that mostly does research or architecture gains less. The first call is where we work out which one you are.

Far more than prompt engineering. The topics that matter now are agentic workflows with tools like Claude Code, running work in parallel with subagents, MCP integrations that connect agents to internal tools, AI-assisted code review, and finding your way round unfamiliar codebases. It should also cover how review and testing keep up once agents write more of the code. And it should run on real codebases rather than toy examples, so participants can apply it straight away.

Look for a trainer who ships production software with these tools every day, not someone who only teaches theory. Claude Code is my main development environment, for client work and for my own products such as Tymeslot, an open-source scheduling platform. So the material reflects real production workflows, real failure modes and practical workarounds, not idealised demos. Cegos Integrata, NobleProg and Code First Girls book me for exactly that.

Yes. I deliver every workshop in German (native) or English (fluent), and in bilingual teams participants can ask questions in either language. The exercises run on your team's own codebase and tools, so every one relates to the daily job. Formats include online sessions, on-site training at your offices and hybrid setups.

Something else on your mind?

More output, same team.

Tell me about your stack and your team, and I will tell you honestly how much of your backlog agents can take on.

In English or German, on site or remote.