Talk to an engineerIntro call
01 - Train & Adopt / AI Training for Developers

AI Training for Developers

Role-specific AI training that teams actually apply at work - engineering, design, operations and leadership tracks, workshop or multi-week cohort format.

Talk to an engineerSee the package
Fixed-price entry packageAI Training DayEUR 2,3001 training day · first date within 3 weeks of agreeing the programWhat is included
In short
01

Built on your stack, not slides

Lab exercises run on your codebase and your workflows, with the tools your team actually uses.

02

Tracks by role

Engineering, product, operations and leadership each get material for their own day.

03

Adoption measured afterwards

A check-in four to six weeks later shows what stuck.

23Minds delivers AI training programs designed by practitioners who ship AI in production.

Show the full summary

Engineering tracks cover AI-assisted development with current tools (Claude Code, Cursor, Copilot, Aider), code evaluation patterns and production safeguards. Business tracks cover prompt design, workflow automation and safe use of AI tools day to day. Leadership tracks cover adoption roadmaps and ROI measurement. A training day has a fixed price: a workshop for a team of up to 12 or an online lecture with no attendee limit; 4-6 week cohorts are quoted as a project; selected programs are eligible for BUR/PARP funding in Poland. The AI literacy duty in Article 4 of the EU AI Act has applied since 2 February 2025.

Why 23Minds

What makes this service defensible.

  • Taught by people who ship AI

    The trainers build and evaluate AI systems in production; the material comes from that work.

  • Eligible for BUR / KFS co-funding

    Selected programs qualify under operator rules in Poland.

  • Training day at a fixed price

    A workshop for a team of up to 12 or an online lecture with no attendee limit, one day, material prepared for your stack.

  • A playbook after every track

    Every track leaves written material for later use; multi-week programs also leave the session recordings.

How we work

The process, phase by phase.

  1. 1

    1. Scope call

    Confirm audience, current AI tool usage, business goals and funding eligibility.

    Week 0
    Two chairs at a round table with one sheet between them and a yellow mark on the point being agreed: who the training is for and what it has to change.
  2. 2

    2. Curriculum design

    Tailor agenda, choose tools to cover, prepare codebase-specific lab material.

    Week 1-2
    A grid of module tiles with a path drawn through them in order and one tile marked yellow: the agenda laid out module by module for this team.
  3. 3

    3. Delivery

    Run the workshop or cohort. Hands-on labs, Q&A, working sessions with real client problems.

    Workshop days as the team needs, or 4-6 weeks (cohort)
    Five workstations facing one large screen, a yellow arrow running from the screen to the row: the workshop delivered in the room, hands on.
  4. 4

    4. Adoption check-in

    Measure post-training usage, identify blockers, recommend next-step interventions.

    Week +4-6
    A bar chart of five rising bars with a yellow ring around the last one: tool usage measured weeks after the training.
How to start

Pick the way in that fits your budget and timing.

Every practice has a free first step, an entry package with a written deliverable and its price listed here, and a full project or retainer quoted after a first call. Once the scope is agreed, the price is fixed, with no hidden costs.

  1. 1
    Step 1 · Free

    Intro call or self-assessment

    60 minutes · 1 engineer · no obligation

    Free
    Show details
    • Intro call with an engineer, or the online self-assessment
    • A written next step within one business day
    • No obligation and no sales deck
    Talk to an engineer
  2. Recommended
    2
    Step 2 · Fixed price

    AI Training Day

    1 training day · first date within 3 weeks of agreeing the program

    EUR 2,300 net

    Fixed price, no hidden costs; extras only from the Not included list.

    Show details
    • One day: a workshop for up to 12 people or an online lecture for any number of attendees
    • Engineering or business track, chosen with you
    • Workshop labs built on your own stack and repositories
    • Attendance certificate and material for reuse
    • Not included: Session recording and editing, travel and accommodation outside our office locations, room rental, catering, tool licences.
    • Eligible for BUR / KFS co-funding, subject to operator rules
    Ask for this package
  3. 3
    Step 3 · Project or retainer

    Full scope, quoted after a first call

    Full scope · phased delivery · quoted per phase

    from EUR 14,000 net, quoted after a first call
    Show details
    • Multi-track program for the whole organization
    • 4-6 week cohorts across several teams
    • Curriculum mapped to your stack and use cases
    Start the conversation
Sounds familiar?

The situations that bring teams to this service.

  • Generic vendor AI training does not translate to your codebase or workflows
  • Engineers use AI tools but cannot tell colleagues what good looks like
  • Training budget is allocated but no provider has shipped what they teach
Show the other problems (1)
  • Cohort vs workshop format choice unclear given team size and goals
Who it's for
  • Engineering managers rolling out AI coding assistants across their teams
  • L&D heads procuring practical AI training under BUR/PARP funding rules
  • Product designers and PMs upgrading their day-to-day AI workflow
  • C-suite leaders building company-wide AI literacy
Failure modes

Where this goes wrong, and what we do about it.

  1. 1. Confidence rises faster than competenceWhat stays with you: per-participant assessment of code comprehension, separate from the completion record, with the tasks used
    What happens

    A randomised study on 52 junior engineers found the AI-assisted group averaged 50% on a code comprehension test against 67% for those who wrote by hand, and the highest scorers were the ones who used the assistant to ask questions rather than to produce code. A course that teaches prompting produces people who ship faster and understand less, and the gap only shows up when something breaks and nobody can read the file.

    What we do about it

    We split every track into producing and understanding, and we assess the second one. Exercises use code the participant did not write, with the assistant switched off for the reading part. Anyone who cannot explain what a generated change does is not through the module, whatever the prompt looked like.

  2. 2. The mandate came from above and the room stopped askingWhat stays with you: written summary of objections raised and what was decided about each, delivered to the sponsor
    What happens

    Leadership announces that everyone will use AI, sometimes with a dashboard ranking how much of it each person consumes. Attendance is then compliance rather than interest, questions dry up, and the trainer gets a room that nods. The organisation buys the certificate and none of the behaviour.

    What we do about it

    We agree before the first session what the team is allowed to conclude, including that a tool does not fit a given task. Sessions are built around the participants' own repositories and their own objections, and we report what the group pushed back on rather than only what they completed.

  3. 3. Trained on a toy repository, back to a real oneWhat stays with you: context files and prompt patterns committed to your repository, plus a list of setup changes we recommend and why
    What happens

    The course runs on clean examples with no legacy, no CI rules and no review conventions. On Monday the participant opens a repository with fifteen years of history, a lint config nobody remembers and a test suite that takes forty minutes. Nothing from the course survives contact, so the tools get used the way they were used before.

    What we do about it

    We run the exercises inside your repository, with your rules and your pipeline, and we adapt the context files and prompts to what your code actually looks like. Where your setup blocks a practice we teach, we say so and fix the setup or drop the practice.

What you get

Deliverables, not deliverable-shaped slides.

  • Role-specific curriculum tuned to your stack, tools and use cases
  • Live workshop delivery (in-person Warszawa/Szczecin or remote)
  • Hands-on lab exercises tied to your actual codebase or workflows
  • Recorded sessions and a written reference playbook per track
  • Post-program check-in 4-6 weeks later to measure adoption
FAQ

Questions procurement teams ask.

A workshop is an intensive program counted in days and priced per day - best for kicking off adoption fast. Cohorts spread across 4-6 weeks with weekly sessions and homework - best for changing day-to-day habits in larger teams.
Yes. Lab exercises are built from your repos under NDA. Engineers learn AI-assisted patterns directly against the code they will work on tomorrow.
Selected programs qualify for funded development pathways (BUR/PARP) in Poland. Eligibility depends on company size, sector and current operator rules. We help check eligibility on the intro call. The labour minister's priorities for Poland's National Training Fund (KFS) in 2026, published on 25 September 2025, name AI skills in the priority on new processes, technologies and tools at work.
Current production-grade AI coding assistants: Claude Code, Cursor, Copilot, Aider, Windsurf. We also cover prompt design and LLM workflow tooling (n8n, Zapier with LLM, custom agents) for business tracks.
Pre/post adoption survey, AI-assist time tracked per developer-week, percentage of PRs touched by AI tools, and a post-program code-quality check-in. Specific metrics agreed on the scope call.
In Stack Overflow's 2025 survey, 84% of the developers who answered the question used or planned to use AI tools. Among those answering the trust question, 46% distrusted the accuracy of the output, and among those answering the frustration question, 66% named answers that are almost right, but not quite. In the 2025 DORA report, 90% of respondents used AI at work and 30% had little or no trust in the quality of AI output. The engineering track covers reviewing AI-generated changes, tests that fail when behaviour breaks, and protecting secrets and managing permissions.
Related services

Often shipped together with AI Training for Developers.

Evaluate & Secure

Independent AI Code Audit

Independent audit of AI-generated code against a rubric published in full.

Learn more
Guides

Guides that lead to this service.

Sources

Where the dates and numbers come from.

Talk to an engineer.

Describe where you are with AI training for developers. A reply within one business day.

Talk to an engineer
Szczecin - ul. Wawrzyniaka 6WWarszawaZielona GóraKraków