Happening on:10–11 September 2026CodeGenAI Developer Training, Amsterdam

Get Your Ticket

Services

AI Education

A structured programme that teaches your engineers to use AI coding agents in their real work. Delivered in cohorts, over several weeks, by senior engineers who use these tools daily.

image-built

The problem

The adoption gap doesn't close on its own.

When a team is given AI coding tools without structured training, a predictable pattern follows:

Only a small group adopts on their own.

Roughly 5–10% of engineers get productive with agents unassisted. The rest try once, hit friction, and stop — or stay wary.

Habits and tools fragment across the team.

Different agents, different conventions, different quality. Output rises in patches, but the team as a whole isn't faster and the codebase gets harder to control.

Agentic coding is a new skill, not a switch.

It changes how a developer works day to day. That shift only happens with structured practice, repeated over weeks, on real work.

How it's taught

Real work on your backlog, not slides.

Cohorts of up to 15 engineers, taught over several weeks by re:cinq's senior engineers — the same people who use these tools to build software and run transformations for clients.

How each session runs

Cohorts of up to 15

Small enough for hands-on supervision. Weekly sessions over several weeks, with real work between them.

Doing, not watching

Slides set context. Most of each session is exercises with the tools, under a trainer's supervision.

Tasks from your own backlog

Real work surfaces real obstacles. That's where the most useful learning happens.

Adapted, kept current

Modules your team already knows get dropped. Content updates every few weeks as the tools change.

Decorative spinning earth graphic

Who it brings along

Enthusiasts, the hesitant, and the sceptical.

For the enthusiasts

From

Personal habits, inconsistent tooling, running ahead of the rest of the team.

product-pointer

To

Productive within a set of shared standards the whole team follows.

For the hesitant

From

Tried an agent once, hit friction, and went back to writing every line by hand.

product-pointer

To

Confident daily use of agents on real production work.

For the sceptics

From

Worried the tools produce poor code, threaten the craft, or replace the role.

product-pointer

To

Reviewing and recovering from agent output with judgment, not fear.

How a cohort runs

What the programme actually looks like.

01

Discovery

Before kickoff

Scope the syllabus

We map what your team already knows and cut modules they don't need.

02

Kickoff

Session 1

Open with a listening exercise

Engineers name what worries them about AI. Nothing sits underneath the training.

03

Cohort sessions

Several weeks

Weekly hands-on sessions

Six modules, delivered weekly. Exercises on the team's own backlog.

04

Train-the-trainers

Optional

Prepare your own trainers

Your senior engineers learn to run the programme themselves.

01

Discovery

Before kickoff

Scope the syllabus

We map what your team already knows and cut modules they don't need.

02

Kickoff

Session 1

Open with a listening exercise

Engineers name what worries them about AI. Nothing sits underneath the training.

03

Cohort sessions

Several weeks

Weekly hands-on sessions

Six modules, delivered weekly. Exercises on the team's own backlog.

04

Train-the-trainers

Optional

Prepare your own trainers

Your senior engineers learn to run the programme themselves.

01

Discovery

Before kickoff

Scope the syllabus

We map what your team already knows and cut modules they don't need.

02

Kickoff

Session 1

Open with a listening exercise

Engineers name what worries them about AI. Nothing sits underneath the training.

03

Cohort sessions

Several weeks

Weekly hands-on sessions

Six modules, delivered weekly. Exercises on the team's own backlog.

04

Train-the-trainers

Optional

Prepare your own trainers

Your senior engineers learn to run the programme themselves.

Outcomes

What a cohort takes away.

Every programme commits to measurable outcomes agreed at the start. The standard baseline: at least 90% complete the curriculum and at least 80% report increased confidence.

A shared team standard

Engineers work to the same conventions and guardrails, so the codebase stays coherent as agentic use scales.

Sceptics turned adopters

The hesitant come along with the enthusiasts. A change-management outcome that quietly matters as much as the technical one.

The ability to teach yourselves

Train-the-trainers prepares your senior engineers to run the programme, so new joiners reach the same standard without us.

Measurable baseline

Completion, confidence, agentic-tool usage, and delivery metrics agreed up front, so leadership can see what the investment is producing.

Get started

Bring your team up to a shared standard.

Tell us where your team is today and what a cohort would need to cover. We'll come back with a scoped programme, timelines, and the measurable outcomes we'll commit to.

btn-ellipsStart with our free capability assessmentStart with our free capability assessment