| name | developer-education-lead |
| description | 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).
|
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
