Join the waitlistlog in · Nairobi
// curriculum

AI-Ready Product Engineer

Curriculum outcome: an engineer who knows what to build, why it matters and how to deliver it.

15 months
for the full programme: Module 1 takes up to 6 months, Module 2 up to 9.
30–40 hours a week
Full-time study, at your own pace.
On site, remote or both
The Selection Sprint is on site in Nairobi. After that, study on site, from home, or a mix.
No coding experience needed
You learn to code here, starting from zero. Open to anyone who likes figuring things out. Studies are in English.

The next Selection Sprint dates in Nairobi are still being confirmed. Join the waitlist and we’ll contact you as soon as they’re announced.

// the job

Take one product from idea to launch

Pick an idea and walk it through the seven steps of a product engineer’s job.

  • Product

Ask why

Before any code, you talk to five students. The fights aren’t about booking times. They’re about who left the room unlocked, so version 1 needs a lock-up rota as much as a calendar.

Which topic you learn it in

// problem.md
Problem   Saturday slots clash, and the
          room gets left unlocked.
Who       40 students, one study room.
It works  no double bookings and no
when      unlocked nights for a month.
The one page your team agrees on before building.
// what you learn

7 questions that separate a product engineer from a vibe coder

Each topic opens with a question. You answer it by building a project with your team, and the next topic stacks on what you built before. Pick a topic to see what you build, the code, how you use AI and the part of the job around the code.

Selection Sprint3 weeks

Module 1: Programming fundamentals and backendUp to 6 months

Module 2: Product engineeringUp to 9 months

Graduationafter 15 months

Selection Sprint / 3 weeks on site

Is this way of learning for me?

You build
Short tasks that a machine checks, exams on two Fridays, and bigger team tasks at the weekends.
Code
Programming basics in Java and the tools developers use every day. No experience needed before you start.
Around the code
Working with people you met that week, and finding answers yourself before you ask. Tutors guide you with questions and hints instead of answers.

Every project ends with a peer review, and every topic has its own AI step, so by the time AI writes most of the code you can tell when it’s wrong. //kood has its own curriculum team and its own learning platform team. They design what you learn, build the platform you learn on, and change both when the work changes.

“We started from what a junior engineer is trusted with in their first year and worked backwards. Every topic opens with a question you’ll meet at work, and you answer it by building with a team. You get AI from the first week, and more of it as you learn to check it.”

Viktor Veertee, Curriculum Lead at //kood
// why this curriculum

We dare to say it’s the best

35+

interviews, and counting

We rebuilt the curriculum in 2026 after interviewing tech recruiters, senior engineers, engineering managers and our own alumni, and checking what they said against job market data from Europe, the US and Africa. Three findings hold everywhere:

  • /The technical bar for a first job has gone up. Testing, documentation and checking AI output now get you in the door.
  • /The skills around the code decide who grows: talking about trade-offs, taking feedback, owning an outcome.
  • /AI made writing code cheaper. Judging whether it’s right got more valuable.
kood/Fellowship

advises what you learn

kood/Fellowship is the curriculum’s advisory board. Tech leaders from Bolt, Katana, Swedbank and other companies tell us what they’ll expect from a new engineer, and we build their answers into how you learn.

“If you can’t code, you’re just a vibe coder.”

Oliver Leisalu, technical founder of Bolt, kood/Fellowship member
Our own team

keeps it running and keeps it current

The curriculum and platform team update the curriculum all the time. The platform is used by thousands of people every year. Most recent countries: Finland / Germany / Kenya / Uganda / Ukraine.

If you can’t work without AI, employers won’t hire you. If you can’t work with AI, you’ll fall behind. At //kood you learn both.

// how you learn

You learn peer to peer. No teachers, no lectures.

Stuck? You’re not on your own.

Your team
You build every project with one to three others and work through problems together.
Your peers
Learners from your own cohort in Nairobi and from earlier batches review your work and help when you're stuck.
The whole school
Ask in the study forum on //kood’s Discord, where learners from every batch and learning centre help each other.
AI as a tutor
It explains error messages and docs. You check what it tells you.
The kood/Nairobi team
A project team and a technical coordinator on site, and a tech team for platform problems. Reach them on Discord or by email.
Each topic builds on the one before.

You keep going deeper into what you know and wider into what needs it.

Study where it suits you.

On site in Nairobi, from home, or both.

Our own learning platform
“Not long ago I was a student on this platform myself. Now I help build it with a team of engineers who are just as passionate about making every student’s journey smoother. We’ve started connecting students across batches, so you review and learn alongside people a step ahead or a step behind you.”
Saba Gul, Product Engineer, learning platform

It starts with the Selection Sprint

Three weeks on site in Nairobi, free of charge. Applying costs nothing: the logic game, the info session and the Sprint are all free. No coding experience needed.

You become
AI-Ready Product Engineer
You learn
Backend, frontend, distributed systems and AI
How
Peer to peer, project by project
Next Sprint
Dates to be confirmed