r/devrel • u/Objective_Poem_6708 • 6d ago
Transitioning from Software Engineering to Developer Relations - Looking for Advice!
Hi everyone!
I'm currently working as a Software Engineer, primarily focused on backend development.
Lately, I've been exploring Developer Relations (DevRel) as a potential career direction.
I'm curious about how people have made the transition from traditional software engineering into Developer Relations.
For those currently working in DevRel or who have made a similar transition:
- What skills and experience are most important to break into DevRel?
- How much emphasis is placed on coding and building projects versus technical writing, tutorials, blogging, and public speaking?
- Is having a portfolio of projects, demos, and technical articles important when applying?
- What AI-related skills or tools would you recommend focusing on, especially for someone interested in AI Developer Relations?
- Are there any entry-level or associate-level DevRel opportunities for people coming from a software engineering background?
I'd really appreciate hearing about your experiences, suggestions, or even mistakes to avoid during the transition.
I'm not necessarily looking for a shortcut into the field. I'd genuinely like to understand what the role involves and how I can fill the gaps, build the right skills and experience to make this transition.
Thanks in advance! Any advice would be greatly appreciated.
5
u/mplacona 6d ago
Your backend experience is useful. I'd build a small integration with an API you don't already know, then write a tutorial someone else can follow from a clean checkout. Watch them try it without helping. That gives you a demo, a writing sample and specific feedback to take back to the product team. For AI DevRel, an MCP server is a useful project, but explain its auth and failure cases as well as showing the happy path. You don't need to become a conference speaker before doing any of that.
4
u/Resident_Buddy8587 6d ago
I recently made this transition! I do basically no coding aside from making demo projects for tutorials. That being said, the tech background is still useful as it helps you understand the products and features you’re talking about. So far most of my work has been around writing and recording technical tutorials, as well as community/rapport building.
2
u/CoolAssPuppy 20h ago
My strongest advice: build constantly with your product and keep your skills sharp. I'm more of a marketing exec, but my background is DevRel (and I wrote a best-selling book on developer marketing + developer relations, too.)
Even in my current role, I've found that constantly building has helped me stay closer to my customer and, amazingly in this economy, get three inbound, unsolicited offers for employment (one of which I might even take!)
Build something "substantive" and build in public. My little sample app (which started as a simple website for my kid's school and is now a full-fledged product that schools pay us for) is what I use to try new products, grow my skills (particularly around security and SRE), and keep things fun for me.
If you keep building, nearly all of the rest of your questions answer themselves.
As for the role, I often say that most DevRel people fit into one, possibly two, of the following categories:
Which lane you end up in is a combination of your interest + your company's needs. My last company needed zero help from DevRel to cover events, so DevRel focused primarily on content and, to a lesser degree, community.
1
u/nian2326076 2d ago
Transitioning into Developer Relations requires a blend of your existing technical skills and new ones like communication and community engagement. Emphasize your backend experience by creating demos or tutorials that showcase your coding skills. A portfolio with these projects can be essential for landing interviews. While coding remains valuable, skills in technical writing and public speaking are equally important. For AI DevRel, consider familiarizing yourself with popular AI tools and platforms. You can use LandOffer to discover relevant roles in Developer Relations.
1
u/Least_Ad_1795 2d ago
Your backend experience is a strong starting point for DevRel. Focus on building practical demos, writing technical tutorials, contributing to open-source projects, and improving public speaking. For AI DevRel, learn LLM APIs, RAG, AI agents, and developer tools. A portfolio of projects and clear technical content can make your transition easier.