Certificates.
A certificate shows that you have done real work and that people have checked it. Anyone can check a certificate here.
Three ranks
Developer, Master Developer, Sensei
Each rank has its own certificate. Here is what you need to earn each one.
Developer
You own one product from the first customer conversation to a launch plan, and you can show it.
What you need
- Finish the six-week Developer path.
- Hand in a Product Package: eight parts, kept in git.
- Present it in 15 minutes and answer questions without notes.
- Reach level 3 on all six skills in the rubric, with none below level 2.
Master Developer
You can run the ground products stand on, launch safely, and steer AI agents across several repositories.
What you need
- Study the Master Developer path: platform, open-source-first choices, GitOps and service management.
- Pass the four gates, each with a written test and an observed practical.
- Pass the final mixed exam and the oral review.
- Score at least 70 points and finish every mandatory item.
Sensei
You coach others, host live builds and review work. Sensei is by application, not by exam.
What you need
- Hold a Master Developer certificate, or be invited by the Developer Dojo team.
- Apply and talk with the team about how coaching works here.
- Keep contributing: points and tiers are explained on the Sensei page.
Assessment
How assessment works
You are judged on evidence in git, not on memory alone. Everything is checked by people.
Gates
Master Developer candidates pass four gates in order. Each has a written test and a practical task that someone watches.Product Package
Developer candidates hand in one folder in git that proves they own a whole product. Reviewers look at evidence, not at promises.Oral review
You explain your choices out loud, without notes. Questions test judgement: why do people write the epics, why do we fix forward.Integrity and AI policy
You work alone unless a task says otherwise. You disclose all AI use. People write epics and roadmaps. AI never does.
Read the full rules: Master Developer assessment, Product Package standard, why people write epics and how to disclose AI use.
Validity
Certificates are renewed every year
Tools and good practice change, so a certificate is valid for one year. To renew, your recent work is reviewed again. A certificate that has not been renewed after a year is no longer valid.
Verify
Verify a certificate
Type the certificate ID printed on the certificate, or the holder's name. We check it against the public list of certificates on this page.
Search needs JavaScript. Without it, use the full list of issued certificates on this page: every certificate we have issued is in it.
How verification works
- A certificate is real only if it appears in this public list. The list is part of this site's source code in git, so every change is recorded.
- We list a person only when they agreed to be listed.
- A name can be shared by more than one person. Check the ID, the rank and the date too.
- If you are shown a certificate that you cannot find here, treat it as unverified. Contact us with the ID and we will check.
All issued certificates
No certificates have been issued yet. Developer Dojo is new, so this list is empty. Every certificate that is issued will be added here, and no entry exists before the real certificate does.
