- 6 min read
Who this is for
Developer Dojo is not a coding bootcamp. We train for the top 0.1% of product people: a role we call the 2030 Product Development Manager. That is a high bar on purpose. It is also open to anyone, because the training is free and the way up is clear: do the work, show it, get it reviewed.
The role exists because the work has changed. AI agents can now write code, tests and documents, draft research, clean data, and run routine operations. They do this quickly and cheaply, and they make mistakes that look confident. What agents do not do is decide what is worth building, take responsibility for the result, or notice that the plan is wrong. A person does that. The 2030 Product Development Manager is that person.
What the role does
| The human job | What it means in practice |
|---|---|
| Decide | What to build, for whom, and why. What is good enough to ship. What to stop. |
| Frame | Turn a vague problem into a clear one: the customer, the pain, the measure of success. |
| Specify | Write the brief and the acceptance criteria so clearly that an agent (or a person) can do the work and you can check it. |
| Own the plan | Write the epics and the roadmap yourself. People write epics; AI never does. |
| Direct agents | Give each agent a task, a brief and limits. Run several at once when the work allows. |
| Verify | Read the diff, compare with the acceptance criteria, test with a real person, check the numbers. Never trust a result you did not check. |
| Manage risk | Ask the security, cost, legal and reliability questions before launch, not after. |
| Ship and learn | Put it in front of real users, measure what happens, and change the plan. |
What you hand to agents
Agents are your workforce for the lower-level work. Typical tasks you delegate, each with a written brief:
- writing code from an approved issue, and writing its tests;
- first drafts of documentation, release notes and user guides;
- summarising interviews and research, and comparing options (you read the sources that matter);
- cleaning and analysing data;
- boilerplate, scaffolding, migrations and routine operations tasks;
- checking a draft against a standard, such as an epic against the epic standard.
What you keep: the decision, the epic, the roadmap, the acceptance criteria, the sign-off and the accountability. The five rules of The Way say how.
The agent ladder
Working with agents is a skill with four rungs. Good lessons on this site say which rung they teach.
| Rung | What you do |
|---|---|
| Use | Work with one agent, step by step, and learn how it fails. |
| Delegate | Hand a whole task to an agent with a written brief and acceptance criteria. |
| Orchestrate | Run several agent sessions at once, each with its own task, and keep them coordinated. |
| Govern | Write the policy, hooks and gates (pipelines, merge trains, protected branches) that keep the work safe without you watching every step. |
You do not need the top rungs on day one. You do need to know they exist, because the person who can govern a group of agents leads far more work than the person who can only use one.
Every discipline, enough depth to direct and judge
The 2030 Product Development Manager is not a specialist in one field. You need enough depth in each discipline to give a good brief and to spot a bad answer. You do not need to hand-type the work.
| Discipline | You decide | An agent can do | You verify by |
|---|---|---|---|
| Strategy and product | Which customer, which problem, which bet | Market and competitor research drafts | Checking sources and talking to customers |
| Design and brand | The promise, the look, the flow | Mockup drafts and copy options | Showing real users and checking accessibility |
| Marketing | The message and the channel | Draft copy and variants | Reading it as the customer would |
| Finance | The budget, the price, the trade-offs | Models and scenario tables | Rebuilding the key numbers yourself |
| Operations | How the product is run and supported | Runbooks and routine tasks | A dry run, and who is on call |
| Security and risk | What must never happen | Scans and first-pass reviews | Asking “what is the worst case?” and reading the findings |
| Engineering | The architecture you can defend | Code, tests, pipelines | Reading the diff and watching the pipeline |
How the Dojo builds this role
- Developer path (six weeks). You own one product from first customer talk to a final Product Package. Start with Developer path: six weeks.
- Master Developer. Platform, production launch and agent orchestration across the whole product. See Master Developer: the second rank.
- Learning tracks. Focused series on one skill at a time, each with the best free courses and videos from other publishers. Browse the learning tracks and the resources.
- The Way. The five rules we work by, starting with people write epics, git is the source of truth and disclose AI use.
- Sensei. The people who coach others and review work. See Sensei.
What we do not promise
We do not promise a job, a salary or a certificate you can show as a degree. Developer Dojo is not an accredited school. We promise a clear path, honest feedback on real work, and material that is free.
Where to start
- New to all of this: read Developer path: six weeks and start Week 1.
- Already building with AI: read The Way, then pick a track that covers your weakest discipline.
- Not sure: open the learning tracks and choose the one you would least like to read. That is usually the one you need.
