The Tech Content Creator Series is a monthly interview series where I chat with industry leaders in various technical communication roles (technical writers, documentation engineers, developer advocates, and what have you) about their careers. It's like chatting over a cup of coffee with a mentor.

On this episode, I sat down with Gift Egwuenu, who is a celebrated public speaker and tech content creator. She answered all the questions I've been asked about on how to become a developer advocate. In this episode, you'll find answers to questions like:

• What skills do you need to become a developer advocate?
• How can you start acquiring the skills necessary to become a developer advocate, and what resources can I explore as guides?
• Is Devrel different from technical content marketing?
• How can you create a developer advocacy portfolio?
• How much coding knowledge do you need to pivot to developer advocacy?

Enjoy!

Me: Can you tell me about yourself?

Gift: I'm Gift Egwuenu, a developer advocate at Cloudflare with seven years of experience in the web/tech industry. I began my career as a content developer before transitioning to developer advocacy. My passion lies in teaching and sharing knowledge, which are some key reasons why I enjoy my current role.

Me: How did you learn about developer advocacy as a career option? You've already told us it's not your first foray into tech. Was there a specific experience or project that sparked your interest in this field?

Gift: I knew about developer advocacy early in my tech career through friends in the role, but I wasn't initially interested. I wanted to focus on front-end engineering for at least five years and was only 2 years into my career at the time. Surprisingly, I found myself doing advocacy work in my free time - blogging, making YouTube videos, and speaking at conferences. It was just a hobby until someone assumed it was my actual job. That's when I realized all this fun stuff could be a real career path, and I started considering developer advocacy seriously.

Me: From what you've shared so far, your foray into developer advocacy was unintentional, but something made you stay. What would you say was the one thing that made you decide it was the career path for you?

Gift: What kept me in developer advocacy was my passion for sharing knowledge. Regardless of whether it was my full-time job, I was happy to keep doing it. Despite opportunities coming my way, I initially stuck to my goal of reaching the senior developer level because mentally, I wasn't ready for that switch. I wrote articles, hosted events, and conducted workshops in my free time, which my employer supported even though they weren't part of my job description. Even when I had a role combining front-end engineering and community management, I preferred doing advocacy work independently in my free time. The flexibility to pursue these interests alongside my job was perfect for me at that stage in my career.

Me: You've given me a little foray into developer advocacy. From my understanding, it involves a blend of both technical and soft skills. What would you say are the most crucial skills for success in this role?

Gift: The role of a developer advocate is multifaceted, blending technical and soft skills. Technical expertise is crucial for speaking developers' language and understanding their challenges. My five years as a developer helped me understand their struggles and offer useful solutions. I’d say having developer experience is a big plus for effective communication, even for less technical DevRel roles. Soft skills, especially public speaking, are equally important. While language preferences vary by company, flexibility is key. For instance, I mainly use JavaScript and TypeScript, but I've had to learn Python too.  You're taking your tech skills and adding a whole new layer on top. It's all about adapting to solve problems with whatever tech is needed.

Me: From your explanation, there seems to be a lot of marketing going on in the role. What would you say is the one thing that differentiates developer advocacy from technical content marketing? Are there any emerging or current trends in the field?

Gift: Developer advocacy falls under the broader umbrella of developer relations, which includes various roles. While there's some overlap with technical content marketing, the key difference is our approach. We're not selling; we're solving problems for developers. If someone's struggling to use our product to build something, we focus on helping them figure it out, not just telling them how great our product is. Current trends include more community-driven and video content, AI in documentation, measuring impact, and expanding into new tech areas like blockchain and IoT. Ultimately, what sets developer advocacy apart is our focus on helping developers, not selling to them.

Me: What was your first role like as a developer advocate? Were there any surprising responsibilities?

Gift: I've been in just one developer advocacy job, which is my current job at Cloudflare. In my three years in this role, I've learned a lot. While conferences and video-making were familiar, content strategy surprised me. It's not just about cool ideas; you need to consider audience needs and company benefits. SEO for YouTube was new too. The biggest shock was the multitasking – you're constantly juggling travel, meetings, writing, and problem-solving. The constant context-switching demands excellent time management skills. It's not a job where you do the same thing every day. There are lots of layers to developer advocacy, like in this image:

Me: How did you land your job at Cloudflare? What was the interview process like, and what should aspiring developer advocates have when applying for their first role?

Gift: I landed my Cloudflare job unexpectedly. After posting a video review of their product, the director reached out about a developer advocate role. I initially declined it because I wasn’t ready to switch roles and referred a friend who got the job. A year later, they reached out again and I reconsidered. The interview process was intense, involving multiple rounds and a take-home assessment. Since I'd never had this exact job before, I focused on showing how my experience fit the role. I spent a lot of time showing off my work - videos, tech talks, that kind of thing. My tip for aspiring advocates: have work to show, even if it's not company-related. Speaking engagements, videos, or tech articles demonstrate your skills and passion. The key is proving you can do the job, even without the official title.

Me:  How can someone create a great DevRel portfolio? How much does it help in job hunting?

Gift: Building a killer DevRel portfolio is all about being genuine and starting early. Create content because you love it, not just for job hunting. Start a tech blog, make YouTube tutorials, speak at meetups, contribute to open-source projects, or write for tech publications. Your portfolio shows employers you're already doing the work, even without the title. It demonstrates your communication skills, tech knowledge, and community engagement. Remember, quality beats quantity. Focus on creating valuable content, not just pumping out stuff. I started with Vue courses, which led to opportunities like teaching on LinkedIn Learning. The key is to start now, create what you care about, and keep at it. Show you're not just interested in the job - you're living it!

Me: Can you paint a picture of your typical workday as a developer advocate?

Gift: The coolest thing about this job is that no two days are the same! On travel days, I'm up early for the airport, prepping for talks, manning our booth at events, giving presentations, and networking. When working from home, I block off time for specific tasks, creating content, attending team meetings, and helping solve developer issues. The only constant is our weekly team meeting with my manager and colleagues. Otherwise, I might be at home one day and on the road the next. It's this variety that makes the job so exciting! You never know what each day will bring, but you're always helping developers and sharing knowledge. That's what makes this job so exciting - the variety keeps you on your toes!

Me: What are the biggest obstacles you've faced as a Developer Advocate? How have you overcome them, and how have they helped you grow professionally?

Gift: Like any other job, developer advocacy has its challenges. The unclear career progression in this new field was one; it's a relatively new field, and not every company has a clear career ladder. I solved this by openly discussing with my manager, learning to advocate for myself, and planning better. Staying productive while traveling was another; I improved my scheduling and prioritizing skills to tackle this. These challenges have helped me grow, enhancing my communication, planning, and adaptability. They've made me a more well-rounded professional, equipping me with skills valuable in any career.

Me: On the flip side, what would you say you find most rewarding about your role? Any particularly satisfying moments or achievements?

Gift: There have been several rewarding aspects and moments in my role as a developer advocate. It's awesome when someone tells me they found my content helpful, like last week when I met someone learning from a video I made a year ago. Quick wins are super satisfying too, like when I fixed someone's Cloudflare issue in just 10 minutes. And there are those surprising moments, like when I gave a talk and the room was so full people were sitting on the floor! That was a real “wow” moment for me.

But the best part is the connections with people. When someone reaches out to say thanks or shares how I helped them solve a problem, that's when I feel I'm making a difference in developers’ lives. It's what keeps me excited about this job every day.

Me: How can someone tell if being a Developer Advocate isn't the right fit for them? Are there signs that might indicate they'd be better suited to a different role?

Gift: Developer advocacy isn't for everyone. If you're uncomfortable in the spotlight, feel drained after public speaking, or struggle with multitasking, this role might not be your thing. It may not be your cup of tea if you prefer deep tech dives over explanations, or find keeping up with tech trends a chore. Developer advocacy is very public-facing and requires constant adaptation. But don't worry if it doesn't feel right - there are related roles that might suit you better. For instance, a Developer Educator focuses more on content creation with less travel, while a Developer Relations Engineer improves user experience with less public-facing work. The key is to be honest about what you enjoy and what drains you. It's all about finding the right fit for your skills and personality.

Me: What's the most important lesson you've learned as a Developer Advocate that you wish you knew from the start?

Gift: Initially, I worried about losing my engineering skills as a Developer Advocate. But I've learned that constant upskilling is crucial. You're not coding daily, but you must keep up with tech trends like AI, and understand them to talk about them effectively. My motto is “Always be learning.” It's challenging, but I focus on what each task needs. I now set aside time for learning, even when busy. It's about understanding and explaining complex stuff better. Embrace learning - it keeps you sharp in this ever-changing field.

Me: How important is building a personal brand or strong online presence for a Developer Advocate?

Gift: A strong online presence is helpful, but not essential for developer advocates. It's great for getting discovered, showcasing work, and promoting events. But personal branding isn't about follower count; it's about providing value. You could be helping newbies or be the go-to for a specific framework. What truly matters is the quality of your work and your impact on the developer community. While a personal brand can help you get noticed, focus on doing great work and helping others. That's what makes you stand out.

Me: What steps should I take to start a career as a Developer Advocate? Are there any resources or communities you'd recommend?

Gift: To start as a Developer Advocate, you must first understand the role fully. Build a portfolio by writing tech articles on sites like Hashnode or Dev.to. Make videos, speak at meetups, and contribute to open-source projects to hone both tech and soft skills. Follow and learn from current advocates, and don't hesitate to reach out for advice. Join DevRel communities like DevRel Collective, DevRelX, or  DevRel Community Africa. The key is to start doing the work before you have the title. Show you can create content, engage with the community, and explain tech well. Keep at it, and opportunities will come.

Me: What's your top advice for someone who wants to become an aspiring Developer Advocate?

Gift: The key is to consistently showcase your work. Don't wait for job openings; start demonstrating your value now. Share your projects, help in developer communities, and be active on social media. I know someone who got a job just by being super helpful in a community’s Slack group!

It's not just about tech skills; you must love teaching and helping others. Start small, be consistent, and build up gradually. It's a marathon, not a sprint. Keep putting yourself out there because you genuinely enjoy sharing knowledge. That passion will make you stand out in this field and the opportunities will come. I greatly recommend you read a book called “Show Your Work” by Austin Kleon

Before you go:

• If you'd like to connect with Gift, check out her LinkedIn and X. And If you enjoyed this piece, share it with a colleague or someone you know will benefit from it. Sharing is caring :)
• Subscribe to the newsletter using the form below to be the first to know when a new interview drops.
• I'm writing a a tell-book for developer advocacy titled The Developer Advocacy Blueprint. It's a guide for individual contributors to learn the skills they need to become a developer advocate and get hired. So, if you're an aspiring developer advocate, keep an eye out for it by subscribing to the newsletter below. See the landing page for the book here.