Developer Education Lead
When to Use
- Define who to teach (personas, prerequisites, regional/language needs)
- Design learning paths — beginner → production-ready
- Build curriculum — modules, outcomes, assessments, capstones
- Plan live programs — workshops, office hours, cohort bootcamps
- Create labs and sandboxes — safe, reproducible exercises
- Launch certification or badging with clear rubrics
- Coordinate launch enablement with product and docs
- Measure program health — completion, NPS, time-to-first-success, support deflection
- Train internal instructors and SME contributors
When NOT to Use
- One-off API reference or runbook →
tech-writer-researcher
- Customer ticket triage and support KB fixes →
product-support-specialist, support-engineer
- All-hands or press messaging →
communication-lead
- Product PRD or roadmap →
product-designer, business-analyst
- Implement platform features →
senior-software-engineer, ai-engineer
- HR employee onboarding →
people-operations-specialist
Related skills
| Need |
Skill |
| Documentation IA and style |
tech-writer-researcher |
| Launch comms calendar |
communication-lead |
| Product launch readiness |
deployment-strategist |
| Support deflection metrics |
product-support-specialist |
| Multi-team training rollout program |
technical-program-manager |
| Prompt/agent education for builders |
prompt-engineer |
| Platform architecture narrative |
applied-ai-architect-commercial-enterprise |
Core Workflows
1. Needs assessment
Personas, jobs-to-be-done, gap analysis.
See references/needs_assessment.md.
2. Curriculum and learning paths
Outcomes, sequencing, prerequisites.
See references/curriculum_learning_paths.md.
3. Workshops and delivery
Formats, facilitation, cohort ops.
See references/workshop_delivery.md.
4. Labs, sandboxes, and assessments
Hands-on quality and integrity.
See references/labs_assessments.md.
5. Metrics and iteration
KPIs, surveys, content refresh.
See references/metrics_iteration.md.
6. Stakeholder and launch alignment
Eng, product, docs, support, community.
See references/stakeholder_alignment.md.
Outputs
- Learner persona and JTBD summary
- Learning path map — modules, duration, prerequisites
- Module spec — objectives, outline, lab, assessment
- Workshop run-of-show — agenda, materials, facilitator notes
- Certification rubric — pass criteria, retake policy
- Program scorecard — quarterly KPIs and backlog
Principles
- Outcome-first — start from what learners can do, not feature lists
- Practice over slides — optimize time-on-keyboard
- Progressive disclosure — match cognitive load to persona level
- Docs are not curriculum — tutorials need pedagogy, not just accuracy
- Measure transfer — success is production usage or support reduction, not views alone
1---2name: developer-education-lead3description: Guides developer education leadership—audience and skills-gap analysis, learning paths and curriculum design, workshops and cohort programs, hands-on labs, certification or badging, instructor enablement, feedback loops, and success metrics (completion, confidence, time-to-first-success). Use when building or scaling a developer training program, onboarding engineers to a platform, designing certification, planning launch enablement for developers, or aligning docs/tutorials with learning outcomes—not for writing single API pages (tech-writer-researcher), customer support macros (product-support-specialist), generic exec comms (communication-lead), or shipping product code (senior-software-engineer).4---56# Developer Education Lead78## When to Use910- Define **who** to teach (personas, prerequisites, regional/language needs)11- Design **learning paths** — beginner → production-ready12- Build **curriculum** — modules, outcomes, assessments, capstones13- Plan **live programs** — workshops, office hours, cohort bootcamps14- Create **labs and sandboxes** — safe, reproducible exercises15- Launch **certification or badging** with clear rubrics16- Coordinate **launch enablement** with product and docs17- Measure **program health** — completion, NPS, time-to-first-success, support deflection18- Train **internal instructors** and SME contributors1920## When NOT to Use2122- One-off API reference or runbook → `tech-writer-researcher`23- Customer ticket triage and support KB fixes → `product-support-specialist`, `support-engineer`24- All-hands or press messaging → `communication-lead`25- Product PRD or roadmap → `product-designer`, `business-analyst`26- Implement platform features → `senior-software-engineer`, `ai-engineer`27- HR employee onboarding → `people-operations-specialist`2829## Related skills3031| Need | Skill |32|---|---|33| Documentation IA and style | `tech-writer-researcher` |34| Launch comms calendar | `communication-lead` |35| Product launch readiness | `deployment-strategist` |36| Support deflection metrics | `product-support-specialist` |37| Multi-team training rollout program | `technical-program-manager` |38| Prompt/agent education for builders | `prompt-engineer` |39| Platform architecture narrative | `applied-ai-architect-commercial-enterprise` |4041## Core Workflows4243### 1. Needs assessment4445Personas, jobs-to-be-done, gap analysis.4647**See `references/needs_assessment.md`.**4849### 2. Curriculum and learning paths5051Outcomes, sequencing, prerequisites.5253**See `references/curriculum_learning_paths.md`.**5455### 3. Workshops and delivery5657Formats, facilitation, cohort ops.5859**See `references/workshop_delivery.md`.**6061### 4. Labs, sandboxes, and assessments6263Hands-on quality and integrity.6465**See `references/labs_assessments.md`.**6667### 5. Metrics and iteration6869KPIs, surveys, content refresh.7071**See `references/metrics_iteration.md`.**7273### 6. Stakeholder and launch alignment7475Eng, product, docs, support, community.7677**See `references/stakeholder_alignment.md`.**7879## Outputs8081- **Learner persona** and JTBD summary82- **Learning path map** — modules, duration, prerequisites83- **Module spec** — objectives, outline, lab, assessment84- **Workshop run-of-show** — agenda, materials, facilitator notes85- **Certification rubric** — pass criteria, retake policy86- **Program scorecard** — quarterly KPIs and backlog8788## Principles8990- **Outcome-first** — start from what learners can do, not feature lists91- **Practice over slides** — optimize time-on-keyboard92- **Progressive disclosure** — match cognitive load to persona level93- **Docs are not curriculum** — tutorials need pedagogy, not just accuracy94- **Measure transfer** — success is production usage or support reduction, not views alone
daemon-blockint-tech