Developer Relations — DevRel for short — is the bridge between a tech company and its developer community. It is part education, part marketing, part community management, and part product feedback. Most people outside tech have never heard of it. Most people inside tech underestimate how valuable it is. If you love teaching, writing, and technology, it might be your ideal career path.
The three main DevRel roles
Developer Advocate is the most common title. Advocates create content, give talks at conferences and meetups, write tutorials, and represent the company at developer events. They are the public face of the developer program. Developer Experience Engineer — DX Engineer — sits closer to the product side: they build sample apps, improve SDKs, and make it easier for developers to get started with the product. Technical Writer focuses on documentation — the guides, references, and tutorials that live in the product's docs site. All three roles require you to be technical enough to be credible and communicative enough to be useful.
Who thrives in DevRel
The profile is specific: technical enough to understand what developers are building, but with a genuine passion for helping others learn rather than building things yourself. Strong communicators who are comfortable in writing, on video, and on stage. People who are energized by community rather than drained by it. Former teachers, technical writers, and developers who spend more time explaining things than building them tend to be naturally suited to DevRel. The skills are almost identical — explaining complex topics clearly to an audience that wants to learn.
What the job actually looks like week-to-week
A typical DevRel week might include writing a tutorial or blog post, recording a short demo video, answering questions in the community Slack or Discord, preparing for or traveling to a meetup or conference, and sitting in a meeting with the product team to share what developers are confused about or asking for. The feedback loop between community and product is one of the most valuable things DevRel brings — good DevRel professionals become the voice of the developer inside the company.
How to build a DevRel portfolio without a DevRel job
Start writing technical tutorials on your own blog or on platforms like Dev.to or Hashnode. Pick an API or developer tool you find interesting and build a small public project with it — then write about what you learned, what was confusing, and how you solved problems. Contribute to open-source documentation by fixing unclear sections or writing missing guides. Give a talk at a local meetup, even a short one. These activities demonstrate the core DevRel skill set before you have the title. Career changers from teaching and writing who can show a body of published technical content are genuinely competitive for junior DevRel roles.