This will probably stay with me for a long time. It was the day I had my first ever Developer Relations interview for an Internship at
. Long story short, I did my fair share of community experience, tech contributions, and talks & presentations, but an official DevRel interview felt different. It was a like mix of excitement, curiosity, and a bit of nervousness, to be honest.The conversation was quite insightful and the Interviewer, a DevRel Engineer at Keploy. It lasted for about an hour and covered a lot about my background, community work, and how I see on what a DevRel does. I began by sharing my journey as a developer. Working on web and mobile projects over the past couple of years and how I gradually also got into no-code tools along the way. I even mentioned how community projects have always been close to me and how I love mentoring or speaking at such events or conferences.
We then moved on to what DevRel really means. I described it as the “bridge between a company and its developer community”, both internally and externally. I said I see DevRel as three main things code, community, and content. Although at first I forgot to mention content. I quickly realized how crucial it is. If anything, I personally value community and content more than the coding part in some cases.
Then the conversation also went into strategies for community engagement. I shared some of my go-to methods like promotions on social media, sending calendar invites, and using Discord announcements to keep the community active etc. We even discussed collaborating with active tech communities such as CNCF to increase the reach. I’ll admit, I missed mentioning an important platform like meetup.com that actually helps in discovering the right audiences.
Another interesting part of the discussion was around content creation. We talked about using blogs, documentation, and tutorials to communicate product value and help users onboard smoothly. I highlighted how short videos, social media content, precise formatted documentation could play a big role in reaching developers who prefer quick visual learning. Then talked about the importance of design assets and branding in DevRel, something I now understand is just as impactful as the technical side.
When it came to my own skills, I rated my design abilities around seven to eight out of ten. I enjoy creating clean UI and visuals that connect with people. My strong background in community work and my eagerness to grow into the DevRel role was noted then. At the same time, I was suggested to focus on building more innovative marketing ideas and sharper content strategies. I appreciated that feedback because it gave me clear areas to work on.
By the end, the interviewer mentioned that they would send follow up results soon and also shared me some resources to help me strengthen my DevRel knowledge. As soon as the interview ended, I felt a mix of relief and motivation at that moment. It was not just a test of what I know but was also a reflection on what I want to become.
Looking back, I realized that DevRel isn’t just a job title. It more about connecting people, understanding their needs, and helping them succeed with the technology the product offers. And while I may still have a lot to learn, this experience gave me a solid place to start.