# 012: The Developer Advocate Within Every Technical Writer
¡Hola, Tech Writing Friends!
What if I told you that as a technical writer, you’re already halfway to becoming a developer advocate?
You might be thinking: “Me? A Dev Advocate? Isn’t that a different role entirely?”
Actually...
You might be doing Developer Advocacy without even realizing it.
What is a Developer Advocate?
Developer Advocates in Developer Relations (DevRel) teams bridge the gap between developers and the companies creating techy stuff for them.
They do this by:
Creating technical content that helps developers understand and use tools effectively.
Speaking at events, webinars, or conferences to share insights and best practices.
Engaging with the developer community to gather feedback and advocate for user needs.
Sound familiar? It should—because these are also key parts of a technical writer’s role.
What Makes Tech Writers Perfect for Developer Relations?
Here’s why technical writers are natural fits for DevRel:
Communication Skills
You know how to break down complex technical concepts into clear, actionable steps.
Dev Advocates need to do the same—whether through blog posts, tutorials, or live demos.
User Empathy
Tech writers are user advocates by default.
You anticipate user pain points and create content that addresses them. This mindset is critical for engaging with the developer community authentically.
Technical Knowledge
You’ve spent time working with APIs, SDKs, and other tools.
Even if you’re not writing code daily, you understand the technical landscape—and that’s exactly what dev rels need.
Yo, Flex Your Inner DevRel
If you’re ready to explore this path, here are a few ways to get started:
👩💻 Create Educational Content
Write blog posts, tutorials, or sample code that help developers solve problems.
🎤 Speak at Events
If you want to start small, first present at local meetups or webinars.
Focus on topics you’ve already written about—this is a great way to repurpose your expertise.
🤝 Engage with Global Communities
Join online forums, Slack groups, or Discord channels where developers hang out.
Listen to their challenges, answer questions, and use those insights to inform your content.
Your Next Action Steps
If you’ve ever thought about transitioning into DevRel —or just want to explore new skills—start by leveraging what you already do as a technical writer.
Here’s your roadmap:
Audit your existing portfolio. Do you have content that aligns with developer needs?
Experiment with new formats. Try creating videos, sample code, or live demos to complement your docs.
Engage online. Start conversations with developers to build your visibility and learn about their challenges.
You’re Closer Than You Think
As you can see, Technical Writers and Developer Advocates aren’t so different after all.
So, the next time you hear about DevRel, remember that you’re already doing it!
Happy writing (and advocating)! 📝
¡Hasta luego!
Quetzalli
