Agentic Engineering Academy

We opened our doors to a small group of students and junior developers. A selective, hands-on program built for people who wanted to build real software with AI tools, the way real engineering teams do it.

The result? A room full of people who can now say they’ve shipped something real.

Weeks of focused, hands-on agentic engineering

Hours of instruction, code review, and mentorship

Selected participants with direct mentorship

VERDICT

Participants have spoken

Four weeks of late-night sessions, real projects, and steep learning curves. Here’s how our first generation describes it, in their own words.

To make sure we got the full picture, we also gathered feedback anonymously. No names, no pressure, just honest opinions from people who lived through it.

Academy timeline

Mondays and Wednesdays, for four weeks. Each week opened with a problem and closed with something participants built.

Week 1

Foundations of agentic engineering

Two sessions of theory and setup: what agentic engineering actually is, AI capabilities and limits, prompts, agent files, subagents, skills, hooks, and MCPs. Ends with everyone’s Claude Code environment up and running.

Week 2

Product, design, and the real project begins

Four teams, four real DECODE apps, assigned at random. Product discovery, a Figma crash course, then straight into scrum: creating and estimating the actual tasks they’ll build.

Week 3

Working on a real project

Full sessions of hands-on development, reviewed by DECODE engineers the same way they’d review a teammate’s pull request. QA and testing included, not an afterthought.

Week 4

Deployment and final presentation

Deployment and release process, then a live demo day. Each team presented what they built, DECODE engineers and peers judged it, and one team won.

Participant didn’t just learn it. They built it.

Instructors were looking at how participants approached the problem, not just whether the answer was right.

Action over theory – Participants built from day one. No slides, no videos, no “exercises.” Everything they did produced something they could show.
Feedback that’s actually useful – Not “good job.” Engineers who’ve built this stuff for years told you specifically what to fix and why.
A portfolio to show – One real deliverable in four weeks. Code that ran in a live environment, reviewed by engineers who’ve shipped software for global giants.

Meet the mentors

Everyone who taught here lives and breathes software. They’ve built complex products for some of our biggest clients and they reviewed work the way a senior colleague would, not the way a professor would.

Matija Šelendić

Senior software engineer

Vladimir Kolbas

Engineering manager

Eight spots.
One cohort a year.

Next cohort: 2027, Zagreb.