Phase 02 of 5

The Four Core Pillars

The four disciplines that define DevRel work at every level. Most practitioners specialize in one or two early on, then expand coverage with experience. All four are required for senior roles.

4 skill modules41 topics8–12 weeks at 5 hours a week
Your progress in this phase0%
0 of 45 steps · 0 of 4 Compass Challenges complete

About this phase

Phase 1 gave you the why and the technical baseline. Phase 2 is the what: the four disciplines that make up day-to-day DevRel work.

  • Content Creation teaches at scale: tutorials, docs, samples, video.
  • Community Building creates a place where developers help each other and help shape the product.
  • Public Speaking & Events builds trust fast, one room at a time.
  • Developer Experience removes the friction that makes developers quit.

They reinforce each other. A talk becomes a blog post, which becomes a docs page, which answers a community question, which reveals a DX problem, which becomes a product fix, which becomes your next talk. That loop is DevRel. The better you understand it, the more each piece of work compounds.

You don't need to master all four at once. Most practitioners go deep in one or two early in their career. Engineers often lead with content and DX, and community builders with community and events. Aim for working competence in all four before moving to senior roles. Each module ends with a Compass Challenge that produces a real, public portfolio piece. Do them: a portfolio of four challenge outputs is a strong DevRel application on its own.

By the end of this phase you'll be able to
  • Plan, write and publish technical content that solves real problems — and measure it
  • Launch, run and grow a developer community with healthy norms and metrics
  • Pitch, build and deliver technical talks and workshops, including live demos
  • Map a developer journey, measure onboarding friction and turn feedback into product change

Skill modules

Each module follows the same path — Learn → Resources → Challenge. Work through them in order, or jump to the one you need.

What makes technical content effective, and how do you produce it consistently?

0/11 topics
  1. Content StrategyAudience identification, content calendar, distribution channels, and goal alignment with business outcomes.
  2. Blog Posts & TutorialsLong-form technical writing that educates developers — from getting started guides to deep-dives.
  3. DocumentationGetting Started guides, API references, FAQs — the backbone of developer experience at scale.
  4. Code Samples & Example AppsRunnable, well-commented code that shows real-world usage patterns developers can copy-paste and build on.
  5. Video & Live StreamingDemos, walkthroughs, and live coding sessions — YouTube, Twitch, and community platforms.
  6. Podcasts & AudioInterviews, discussions, and educational audio for developer audiences on the move.
  7. NewslettersRegular digests that keep your community informed, engaged, and returning.
  8. Editing & Brand VoiceWriting concisely, with personality — building a consistent voice across all output formats.
  9. Content Performance AnalysisMeasuring reach, engagement, and downstream conversion from every content asset you ship.
  10. Guest BloggingWriting for external publications (dev.to, Smashing Magazine, InfoQ) to reach new audiences.
  11. Animations & Visual ExplainersDiagrams, motion graphics, and visual content that explains complex concepts faster than text.
🧭 Challenge: Publish your first technical tutorialStart module →

How do you build a developer community people actually want to be part of?

0/10 topics
  1. Building a Community from ScratchChoosing platforms, seeding activity, onboarding early members, and creating the culture from day one.
  2. Community ManagementDay-to-day moderation, health monitoring, member support, and keeping energy high.
  3. Community Guidelines & Code of ConductSetting expectations, enforcing rules consistently, and creating psychologically safe spaces.
  4. Forums & Discussion PlatformsDiscord, Slack, Discourse, Reddit, GitHub Discussions — where developers actually gather and talk.
  5. Meetups & Local EventsOrganizing, promoting, and facilitating in-person and virtual gatherings around your community.
  6. Encouraging ParticipationRecognition programs, contributor spotlights, first-contribution guides, and engagement loops.
  7. Managing Difficult Members & ConflictHandling disputes with empathy and clarity while protecting community culture.
  8. Community Growth StrategiesAcquisition tactics, referral programs, cross-community partnerships, and ambassador programs.
  9. Community Health MetricsDAU/MAU, retention, message volume, contributor growth — measuring vitality not just size.
  10. Onboarding New MembersWelcome flows, starter resources, and quick-win paths that turn lurkers into active contributors.
🧭 Challenge: Design a community launch planStart module →

How do you give technical talks and run events that people remember?

0/11 topics
  1. CFP Writing & Talk ProposalsHow to pitch compelling talks — abstract writing, title selection, speaker bio strategy.
  2. Talk Structure & NarrativeBuilding a story arc: hook, premise, demonstrations, takeaways. Making technical content memorable.
  3. Live Demo DeliveryRunning demos that don't break — rehearsal strategy, fallback plans, and recovery skills.
  4. Conference SpeakingTier-1 events (KubeCon, AWS re:Invent, DevRelCon, Open Source Summit) — norms and expectations.
  5. Meetup & Lightning TalksLower-stakes stages to build confidence, gather feedback, and refine material fast.
  6. Engaging Your AudienceStorytelling techniques, audience interaction, pacing, and energy management for long sessions.
  7. Handling Q&AAnticipating tough questions, bridging to your message, and managing what you don't know.
  8. Workshop FacilitationHands-on sessions that teach by doing — curriculum design, pacing, and participant support.
  9. Event ManagementRunning your own events — logistics, promotion, sponsorship, and post-event follow-up.
  10. Media AppearancesPodcast guest appearances, webinar panels, press interviews — representing your company or project publicly.
  11. Handouts & Supporting MaterialsSlide design, code repositories, resource lists — materials that extend the value of a talk.
🧭 Challenge: Submit your first CFPStart module →

How do you find and remove the friction developers hit with your product?

0/9 topics
  1. Developer Journey MappingCharting every touchpoint from discovery through onboarding to advanced production usage.
  2. Onboarding & Time-to-Hello-WorldReducing friction from sign-up to first successful API call — the single most critical DX metric.
  3. Developer Satisfaction MeasurementCSAT surveys, NPS, qualitative interviews — understanding how developers actually feel.
  4. Feedback Collection at ScaleStructured surveys, community listening, support ticket analysis, and one-on-one interviews.
  5. Feedback Loop to Product & EngineeringSynthesizing developer pain into structured, prioritized product recommendations engineering can act on.
  6. Building & Contributing to SDKsReducing integration friction by contributing to client libraries across major languages.
  7. Documentation as a ProductTreating docs as a living product — versioned, tested, and iterated based on developer usage patterns.
  8. DX AuditsSystematic review of a platform's developer experience from a fresh set of eyes.
  9. Error Messages & Edge CasesMaking failures clear, actionable, and non-frustrating — the DX of things going wrong.
🧭 Challenge: Publish a DX auditStart module →