One conversation, then a week that repeats.
You are interviewed, given a level, and put on real work. From then on it is the same loop: a task, a review, the thing you were missing, and a note about what you can now do. This page is that loop, in order.
Day one is an interview, not a lesson.
Before you write anything you talk to Adaeze, your engineering manager. Out of it comes a level, and the level is what the rest of this page is calibrated against.
A conversation, not a test
Adaeze asks about work you have done, how you rate yourself, how many hours a week you really have, and what you want to be better at.
A level comes out of it
Somewhere between L1 and L5. It is not a badge. It decides how the team behaves towards you from that point on.
The team moves to meet you
At L1 your lead decides and hands you scoped work. At L5 they defer to you and expect you to make the call. Same team, different behaviour.
Then the same six things, every week.
This is the whole product. Not a course with a project attached, but a working week that happens to teach you, because that is what a first job does to a person.
- 01
A task is assigned to you
Naledi writes it, Maya puts it in the week, and it lands with your name on it. You do not pick from a menu. You pick up what is next, which is the part working on a team actually feels like.
Task BLK-218 · assigned to you - 02
You build it in your own repository
Your own GitHub, your own commits. Bring a project you already have or start from a template, and the history that comes out belongs to you whatever happens next.
Your GitHub · your commits - 03
A senior engineer reads every line
Lars goes through the change and says exactly what is wrong with it, ranked by how much it matters. Nothing counts as finished until you fix it, and then he reads it again.
Review round 2 · 3 things to fix - 04
What you were missing gets named
Whoever read your work points at the ideas behind it and says why they matter here. Not a syllabus written in advance, but the thing standing between you and finishing today.
Named by Ravi · from your task - 05
Someone teaches it until you can explain it
The teammate who raised it teaches it, by message or by voice, using your own code as the example. It is only marked learned once you can say it back in your own words.
Confirmed · you explained it back - 06
The team writes down what they saw
A short note against a specific piece of work: what you did, which skill it showed, and a link to the evidence. Over weeks those notes are what moves your level.
Schema design · L3 · noted by Tunde
Nobody hands you a syllabus.
The teaching is not a module beside the work. It comes out of the work, from the person who read it, and it is only marked done when you can explain it back.
It starts from your work, not a syllabus
Nobody hands you a list of topics. A teammate reads the task in front of you and names what it touches, which is the moment you actually need it, and the moment it sticks.
The person who raised it is the person who teaches it
You follow up with whoever made the remark, not a stranger starting over. By message or on a call, whichever you prefer, using examples from the code you just wrote.
It only counts when you can explain it back
Being shown something is not knowing it. Progress records what a teammate confirmed you could explain in your own words, which is the only version of a skill an employer can rely on.
Run the loop enough times and it is a career.
What comes out is a real commit history, a level with the work underneath it, and a page you can send to anyone. The first conversation costs nothing and takes one sitting.