Today is a day of contemplation for me, a day to take pause and reflect. It’s a big day because today I conclude 3 years of working my first professional Developer Relations (or DevRel) role (and, well, first job) at Appwrite. Honestly, back in July of 2021, when I sat in my room at my home in Dehradun applying for Appwrite’s DevRel Engineer (which was still on a Google Form back then), I never expected that I’d be spending the next 3 years supporting one of the coolest developer tools I had come across.
My journey in DevRel has been an absolute roller coaster ride since, with lots of ups and downs and a few loops around, but one that I have thoroughly enjoyed! I have had a number of learnings, some of which I would love to share with you all today.
Major learnings I’ve had in DevRel 🥑
Before we further, if you are unaware of what DevRel really is, please consider giving the following article a read:
Learning 1: Understand that you are a part of a business
Most bystanders who notice and comment about DevRel don’t realise that Developer Relations isn't just about fostering community and creating engaging content; it requires aligning with and supporting your company's broader goals. I have to be mindful of how every action and initiative I take contributes to tangible business outcomes, such as user acquisition, retention, or product feedback loops. This also means that I can’t hide away from the workings of your Engineering, Marketing, Product, and Sales teams.
It requires a strategic mindset, where you're always thinking about the bigger picture, about how your efforts as a DevRel professional can help the company grow and succeed. To better understand what I mean, take a look at the Developer Advocate iceberg created by Wassim Chegham (read his blog).
Learning 2: It’s necessary to grow out of the little leagues (a.k.a. student communities)
Starting in student communities was a great way for me to build foundational skills in DevRel, such as public speaking, content creation, and community management. However, moving beyond these early experiences was just as crucial to grow professionally.
Engaging with more seasoned developers and industry professionals presents new challenges and learning opportunities. It pushes you to elevate your game, develop deeper technical knowledge, and refine your communication skills. This growth isn't just about moving away from student communities but expanding your horizons to include more diverse and complex developer needs. It's about evolving from a mentor for students to a trusted advisor for professional developers, who are the primary customers for most of us.
I wrote a more focused piece about the same:
Learning 3: Get your hands dirty with the tech
In DevRel, credibility comes from being hands-on with the technology you endorse. I can't effectively advocate for Appwrite if I haven't used it myself, experienced its strengths and pain points, and understood its potential from a developer's perspective.
This requires a willingness to dive deep into the tech, experiment, build, and sometimes break things to understand them better. By getting your hands dirty, you can provide more authentic insights, write better tutorials, and offer more valuable support to the community. It’s about being a practitioner as much as an advocate, bridging the gap between product teams and developers with firsthand experience.
I have better explained how DevRel professionals can further support their Engineering team if they possess this knowledge here:
Learning 4: Social media isn’t the only way
A lot of early DevRel professionals and teams put substantial emphasis on social media as a primary channel for engagement. While it is a valuable tool, I learned that it’s not the only way to connect with the community. Real engagement happens through various channels: meetups, conferences, webinars, blogs, forums, and even one-on-one conversations. Social media can enable initial awareness, but it doesn't create deeper, meaningful relationships.
Therefore, it is necessary to diversify your approach to outreach to your community, using a mix of online and offline methods to reach developers more impactfully.
Learning 5: You don’t have the luxury of keeping enemies
The tech world is a small, interconnected community, and in DevRel, maintaining good relationships is crucial. I’ve learned that in DevRel, there’s no room for grudges or enemies. Every relationship matters, whether it’s with community members, other DevRel professionals, or colleagues. You never know when you might need to collaborate or when someone from your past might cross your path again.
It isn't about avoiding conflict but rather handling disagreements professionally and respectfully, understanding that today’s rival might be tomorrow’s collaborator.
Learning 6: Hold your opinions with kindness
In a field that involves a lot of public interaction and community engagement, the way you communicate matters immensely (also keeping the previous learning in mind). I remember how easy it could be to be passionate and outspoken, even brash sometimes. Over time, I realized that holding my opinions with kindness was far more effective because it forced me to plan my communication more. Being thoughtful and constructive in my feedback helped build trust and foster a more inclusive community environment.
In DevRel, where you're often seen as a representative of the company, it's crucial to balance honesty with empathy, recognize the impact your words can have, and ensure that your communications build bridges rather than walls.
Learning 7: Don’t forget your health, it’s important
DevRel can be demanding, with constant travel, events, and community management, which can lead to burnout if not carefully managed. I learned the hard way that I needed to prioritize my health, both mentally and physically. Setting boundaries, taking breaks, and ensuring I didn’t overextend myself have become crucial practices for my sustainability.
Taking care of your well-being is not just about personal health but also about being at your best for your community and your company. It’s a reminder that while work is important, it’s not everything.
Learning 8: Carry out the trash when needed
DevRel isn’t always glamorous. There will be times when you need to handle the less exciting tasks, whether it’s moderating a forum, responding to repetitive queries, managing logistics for an event, or literally taking out the trash after that event concludes.
Embracing these tasks with a positive attitude is part of being a team player and contributing to the overall success of the team. It shows that you’re willing to do whatever it takes to support the community and the company. It’s about having the humility to do the small things, knowing that they are essential to the bigger picture.
Learning 9: Evolve or die
The tech industry is one of constant evolution, and staying relevant requires continuous learning and adaptation. In DevRel, this means not only keeping up with the latest technologies and trends but also evolving your strategies and approaches to community engagement.
We did not have platforms like Discord or Slack being used for communities 10 years ago. The hype of meetup groups from pre-COVID times isn’t close to the same today. Social media engagement and short-form content consumption (TikTok, YouTube Shorts, Instagram Reels) are at an all-time high.
This adaptability allows you to stay effective and continue adding value even as the landscape shifts. It reminds you that stagnation is not an option.
Learning 10: We take care of our own
The DevRel world is a very small world. It can be a demanding and sometimes isolating field, where challenges are unique and not always understood by those outside the role. Supporting each other, sharing experiences, and offering advice has been incredibly valuable. I realized that we're all in this together, facing similar obstacles and striving towards common goals, whether it's community engagement, advocating for developers, or aligning our efforts with business objectives.
Building a strong network of DevRel professionals has been essential for my growth. It’s about reaching out, sharing knowledge, and being there for one another in both good times and challenging ones. Encouraging and uplifting each other helps create a stronger, more resilient DevRel community. It really does create a win-win for everyone.
The journey onwards 🛣️
Looking back, my journey over the past three years has been filled with countless moments and invaluable lessons that have shaped who I am today, both as a DevRel professional and as a person. This makes me feel very excited about my future in the developer community. Honestly, I don’t know how the world of tech will proceed in the years to come. However, I will say, I’m ready to take on whatever challenge may come my way in the days forward.
This write up is so valuable when it comes to understand the umbrella term - Devrel. You carried your ideas and thought very beautifully.
After reading this I have 2 realizations-
1. I need to work on a lot of things. Like : work more on technical part, learn to hold my opinions and a lot more small but essential things.
2. I also need to start a newsletter of my own to share my learnings and experiences so that it can't die with me as it can benefit a lot of people as well as myself in the future.
Thanks for sharing this beautiful and valuable article.