# The AI Engineering Workshop for engineering teams

Source: https://tpiros.dev/ai-engineering-workshop/

Every engineer got a coding agent. A few hand it whole tasks. You pay for Cursor, Claude Code, Codex or Antigravity. A few of your engineers hand the agent a whole task and check what comes back, and the rest use it as a faster autocomplete. I teach the whole team to work the way the few do, usually on your own codebase, and to build agents of their own when that's the next job. It's for one engineering team at a time, in an SME or an enterprise. The AI Engineering Workshop is a hands-on workshop run by Tamas Piros for one engineering team: working with Claude Code, Codex, Cursor or Antigravity in any language, usually on the team's own codebase, and building agents of their own. Remote or on-site. A paid engagement, quoted against scope; nothing here is priced.

## What the gap looks like

Same codebase, same agent, two different jobs.

What most engineers type:

> add pagination to the users endpoint

What the few type:

> Read AGENTS.md and the orders route first. Orders already has cursor pagination. Add the same to GET /users. Plan it and wait for me before you write any code. Add an integration test next to the others, run the test suite, and stop if anything outside the API and services folders needs to change.

The engineers who write the second one worked it out on your codebase, one rejected diff at a time. I teach the rest of the team to do the same.

## How it works

Your engineers leave with the code they wrote. I explain each moving part and they write it, on content shaped around what they are building. No pre-work for attendees. Remote or on-site.

1. A 30-minute call. What your team is building, which coding agents they use, and which half of the workshop they need. Often it is both.
2. Shaped around your team. I put the content together for your team and the work in front of them. How long it runs depends on the scope we agree.
3. The workshop. Remote or on-site. I explain each part, and your engineers do it as we go, on their own code with their own coding agent or by writing the agent themselves.

## Two halves, one workshop

The call decides which half your team needs, or both, and in what order.

- **Working with coding agents**: Cursor, Claude Code, Codex or Antigravity, whichever your team uses, in any language, usually on your own codebase. Giving the agent the context it needs with AGENTS.md, skills and rules files, planning before it writes, reviewing what it wrote, and deciding which work to hand it in the first place.
- **Building agents**: Agents, agentic workflows, harness engineering and the other moving parts, with your engineers writing the code as we go. The syllabus is the free book, and the team needs basic JavaScript or TypeScript.

Each half has its own page: working with coding agents at https://tpiros.dev/ai-engineering-workshop/coding-agents/, building agents at https://tpiros.dev/ai-engineering-workshop/building-agents/.

## Who is in the room

One engineering team. For working with coding agents, any language. For building agents, basic JavaScript or TypeScript and a basic understanding of large language models. No machine learning background for either. Where the wider problem is that most of an organisation never got past asking these tools questions, that's different work: https://tpiros.dev/power-user-gap/.

## What they leave able to do

Depending on what the call settles, they hand real work to the coding agent they already have and know how to check what comes back, or they understand how agents are built because they wrote the moving parts themselves. Often both.

## Before you book

**What does the team need to know already?** For working with coding agents, the agent they already use, in any language. For building agents, basic web development in JavaScript or TypeScript and a basic understanding of large language models. No machine learning background.

**Which coding agents does it cover?** Cursor, Claude Code, Codex or Antigravity, whichever your team uses, and others such as opencode. Context files, skills, planning and review carry across them, so a team split across two tools still gets one workshop.

**What do attendees need to prepare?** Nothing. There is no pre-work. The call decides what goes in.

**Which model providers does it use?** For building agents, OpenAI, Anthropic or Google, whichever your team is building with. The moving parts are the same, and the code is written against your stack rather than a demo one.

**Is it recorded?** No. The workshop is live, and your engineers leave with the code they wrote.

**What is the teaching like?** Customised. The curriculum is put together for your team and what they are building after the call. The coding-agent half uses the agent your team already has, usually on your own codebase. The building half draws on the free book, AI Engineering for Web Developers, and nothing in it is gated.

**What does it cost?** It is quoted against the scope we agree on the call. There are no individual seats and no published prices.

## Next step

Book a 30-minute call at https://calendly.com/tamas-piros/30min, or email hello@tamaspiros.com with what your team is building and what they need to learn. It's one quote, for one engineering team and the scope we agree on the call, one half or both, with no individual seats, so the figure you forward is the whole workshop.