book

A Friendly Guide to Developer Advocacy : Everything You Need to Know to Become a Developer Advocate and Crush Your First 90 Days

Name: A Friendly Guide to Developer Advocacy : Everything You Need to Know to Become a Developer Advocate and Crush Your First 90 Days
Author: Linda Ikechukwu
ISBN: 9798868824623

by Linda Ikechukwu

May 2026

Beginner

319 pages

5h 55m

English

Apress

Read now

Unlock full access

Friendly Guides to Technology
A Friendly Guide to Developer Advocacy
Introduction
Acknowledgments
Table of Contents
About the Author
About the Technical Reviewer
Part I: Introduction to Developer Advocacy
Introduction to Developer Advocacy
1. What Is Developer Advocacy?
1.1 The Rise and Importance of DevRel Practitioners1.2 Components of Developer Relations1.2.1 Developer Experience1.2.2 Developer Education1.2.3 Developer Marketing1.2.4 Developer Success1.2.5 Developer Community1.3 The Place of DevRel Within a Company1.4 Summary
2. What Does a Developer Advocate Do?
2.1 Developer Advocates Are Technical Jacks of Many Trades2.2 Developer Advocates Code, Create Content, and Engage the Community2.2.1 Code (Technical Background)2.2.2 Content2.2.3 Community2.3 Reality Check: Developer Advocacy May Not Be Right for You2.3.1 It Requires Comfort with Ambiguity2.3.2 It’s a Public-Facing Role2.3.3 It Involves Constant Multitasking and Context Switching2.3.4 Career Progression Isn’t Always Clear2.3.5 You Might Lose Your Technical Edge2.4 Summary

Part II: Advocating to Developers
Advocating to Developers
3. Laying the Groundwork for Your Developer Advocacy Strategy
3.1 First, Understand the Company3.1.1 What Is the Company’s Position in the Market?Market LeadersChallengersNiche PlayersShooting Stars3.1.2 What Is the Company’s Growth Stage?Early-Stage StartupsGrowth-Phase CompaniesMature Companies3.1.3 What Is the Company’s Business Model/Monetization StrategyRevenue Up FrontRevenue DelayedMarket EnhancementEcosystem Play3.2 Second, Understand the Product3.2.1 Learn the Product CategoryAPIsSDKsDeveloper ToolsDeveloper ServicesDeveloper Marketplaces and Ecosystems3.2.2 Learn the Product Like a DeveloperQuestions to Ask While Testing3.2.3 Learn the Competitive Landscape of the ProductLook for the GapsCompare the Developer ExperienceBe Honest About Strengths and WeaknessesFeed What Insights Back into the Company3.3 Third, Understand Who the Product Is For3.3.1 Start with SegmentationTechnical Layer: What Technical Context Does the Product Require?User Layer: Who Is the Developer?Organization Layer: What Kind of Company Are They In?Market Layer: What Industry or Region Are They In?3.3.2 Define Your Ideal Customer Profile (ICP)3.3.3 Identify Who’s in the Room3.3.4 Uncover the Jobs to Be Done3.4 Finally, Understand the Team3.4.1 Sync with Surrounding Teams3.4.2 Audit Your Current Dev Advocacy InitiativesStep 1: List Every Current and Recent InitiativeStep 2: For Each Initiative, Ask the Right QuestionsStep 3: Assess Strategic FitStep 4: Decide What to KeepSummary: Bring It All Together
4. Crafting Your Developer Advocacy Strategy
4.1 Choose Your Strategic Bets and Define Your OKRsSummary
5. Executing Your Strategy (Best Practices for Developer-Focused Content and Programs)
5.1 What Makes Developer Content Actually Work?5.1.1 It Solves a Real Problem5.1.2 It’s Written for a Specific Stage of the Developer Journey5.1.3 It’s Skimmable and Easy to Follow5.2 Format-Specific Best Practices5.2.1 Webinars and Online EventsHow to Do Webinars WellConception: Design Your Event to Scale, Not Just to PresentPreparation: Promote and Rehearse HeavilyExecution: Deliver a Human, High-Quality ExperienceWrap-up: Extend the Life of Your Event5.2.2 TalksHow to Do Talks WellPick the Right ConferencesChoose a Talk TopicPrepare Your Talk AbstractPrepping and Delivering Your Talk5.2.3 Event SponsorshipsHow to Do Event Sponsorships WellChoose Events That Will Serve YouGet ready to Show Up WellUpgrade Your Merch GameDesign Your Booth Flow for Lead CaptureThe Hook (Entry Point)The Conversation and Lead Capture (Middle Point)The Exit (Last Point)Follow Up, Measure, and Refine5.2.4 Blog PostsHow to Do Blog Posts WellFind Ideas That MatterCheck That Your Idea Is Worth ReadingUse Templates for Guidance and EaseTemplate 1: How We/I Built ItTemplate 2: Bug HuntTemplate 3: Thoughts on TrendTemplate 4: Lessons LearnedTemplate 5: Benchmarks and Test ResultsFinish StrongTighten the DraftCheck the Shape and ScannabilityGet the Right Kind of FeedbackWrite the Title and Description LastCheck Metadata and AssetsOptimize for Multi-platform UseDo a Final Reader Pass5.2.5 DocumentationHow to Do Documentation WellBuild a Clear Doc Structure with DiátaxisTutorialsHow-to GuidesReference GuidesExplanation GuidesUse Good Docs Templates to Streamline WritingApply Both Frameworks to Your Own DocumentationAudit What You Have and Spot GapsDecide on StructurePrioritize Critical Paths FirstProtect Quality with Reviews, Automation, and Feedback5.2.6 VideosHow to Do Videos WellResearchScriptingFilming/RecordingEditingPublishing and Retrospectives5.3 Designing Your Content for Discovery and Scale5.3.1 Pick a Primary Format You Can Win With5.3.2 Create Once, Repurpose Many Times5.3.3 Distribute and Promote Like Your Life Depends on ItSummary
6. Measuring the Impact and Success of Your Developer Advocacy Efforts with Metrics
6.1 What Not to Do When Picking Your Metrics6.1.1 Don’t Choose Metrics That Are Overly Complex to Collect6.1.2 Don’t Choose Untrusted Metrics6.1.3 Don’t Fall into the Vanity Metrics Trap6.2 What to Do When Picking Your Metrics6.2.1 Identify Your Company’s North Star and Keystone Metrics6.2.2 Pick a Primary DevRel Metric6.2.3 Define Your Success Metrics6.3 Identify Your Assist Impact6.3.1 Examples of DevRel AssistsProduct: Feedback and Beta TestingEngineering: Hard-to-Solve BugsBusiness Development/Partnerships: IntegrationsRecruiting: Potential New HiresCustomer Success: Reduced Support FrictionMarketing and Sales: Leads Handed Off6.4 Calculating ROI of Developer Advocacy6.4.1 Lessons from Zapier: Calculating “Return on DevRel Spend”6.4.2 Beyond Revenue: Quantifying DevRel Influenced Cost SavingsSupport cost savingsCustomer acquisition Cost (CAC) SavingsRetention and Churn Reduction6.4.3 Bringing It All Together6.5 Communicating Your Developer Advocacy Impact to C-Suite6.5.1 Match Your Metrics to the Reporting Period6.5.2 Keep Things Short and Sweet6.5.3 Don’t Bury the Lede: Start with the Impact6.5.4 Use the Body of the Report to Show Causation6.5.5 Conclude with Learnings, Next Steps, and an AskSummary
Part III: Advocating for Developers
Advocating for Developers
7. Building and Nurturing Developer Communities
7.1 What Is a Community?7.1.1 The Community at Large7.1.2 Passive Contributors7.1.3 Active Contributors7.1.4 In-Betweeners7.1.5 The Inner Circle7.2 The Value of Community for Companies7.3 If I Had to Build a Community from Scratch7.3.1 Start with the Willing7.3.2 Expand to the Broader Ecosystem7.3.3 Nurture Through Authentic EngagementMeetingsContent As the Second TouchpointFeedback LoopsRecognition and IncentivesNudges7.3.4 Scale with ProgramsAmbassador ProgramsHackathonsGuest Writing Programs7.4 If I Had to Steer an Existing Community7.5 Measuring Community HealthSummary
Part IV: Landing the Developer Advocacy Job
Landing the Developer Advocacy Job
8. Breaking into Developer Advocacy
8.1 Building a Developer Advocacy Portfolio8.1.1 Step 1: Pick a Tool or Product You Love8.1.2 Step 2: Research the Wins, Friction, and Pain8.1.3 Step 3: Use Your Research to Create a Strategy8.1.4 Step 4: Measure Your Impact and Use Feedback to Improve8.1.5 Step 5: Package Your Work into a Portfolio8.2 Updating Your Resume for Developer Advocacy Opportunities8.3 Finding Developer Advocacy Opportunities8.4 Acing Developer Advocacy Interviews8.4.1 Research the Product (and Company)8.4.2 Demonstrate Core DevRel Traits8.4.3 Prepare for the DevRel Interview LoopCulture or Screening InterviewTechnical InterviewContent or Communication TaskTake-Home AssignmentFinal Round/Team FitOther Common Questions to Expect8.4.4 Prepare Your Own Questions for the TeamHR or TalentHiring managerFuture TeammatesProduct or EngineeringLeadershipCommunity-Specific Probes8.4.5 Watch Out for Red FlagsSummary
9. Your First 90 Days As a Developer Advocate
9.1 Week 1: Learn and Build Camaraderie9.1.1 Marketing9.1.2 Sales9.1.3 Product9.1.4 Engineering9.1.5 Customer Success/Support9.1.6 Other DevRel Team Members9.2 Week 2: Draft Your Plan9.3 Weeks 3 and 4: Ship and Share Your First Win9.4 Months 2 and 3: Execute and Expand9.5 Week 12: Reflect, Report, and ResetSummary
Appendix
Success Metrics Definitions
Index

Content preview from A Friendly Guide to Developer Advocacy : Everything You Need to Know to Become a Developer Advocate and Crush Your First 90 Days

L. IkechukwuA Friendly Guide to Developer Advocacy Friendly Guides to Technologyhttps://doi.org/10.1007/979-8-8688-2462-3_9

9. Your First 90 Days As a Developer Advocate

Linda Ikechukwu¹

Linda Ikechukwu

Email: hello@lindaikechukwu.com

Up until this point, we’ve gone through everything you need to know to land a developer advocacy role, and now you’ve actually landed one.

Congratulations. Really, take a moment to celebrate that. But as exciting as this milestone is, the truth is the real work starts here.

The first 90 days are critical. They shape how you’re perceived, whether you make it past probation, and how well you set yourself up for long-term success. Done right, they create momentum that carries you ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Software Architecture and Decision-Making: Leveraging Leadership, Technology, and Product Management to Build Great Products

Srinath Perera

HBR's 10 Must Reads on Artificial Intelligence, Updated and Expanded (featuring "How AI Can Help Managers Think Through Problems" by Elisa Farri and Gabriele Rosani)

Harvard Business Review, Thomas H. Davenport, Ajay Agrawal, David De Cremer, Stefan Thomke

Improve Your Emotional Intelligence to Communicate Better

Curtis Newbold

Improve Your Critical Thinking Skills

Charles Humble

Publisher Resources

ISBN: 9798868824623

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design

Business

Soft Skills

A Friendly Guide to Developer Advocacy : Everything You Need to Know to Become a Developer Advocate and Crush Your First 90 Days

by Linda Ikechukwu

9. Your First 90 Days As a Developer Advocate

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.