Developer Advocate Jobs: DevRel Titles and How to Find Them
Developer advocate jobs are hard to search for. The field is small, every company names the role differently, and the same title can mean content creation at one company and hands-on engineering at another. This guide covers what developer relations work involves, the titles it appears under, how to read a DevRel posting, and how to set up a search that doesn't miss half of them.
What developer relations is
Developer relations, or DevRel, is the team that sits between a company and the developers who use its product. Its job is to help those developers succeed and to bring what they learn back inside the company. In practice that means some mix of:
- Content: tutorials, blog posts, videos, sample apps, livestreams.
- Documentation and examples: often in close partnership with technical writers.
- Talks and events: conferences, meetups, workshops, webinars.
- Community: forums, Discord or Slack servers, open-source contributors, ambassador programmes.
- Product feedback: turning what developers struggle with into clear, prioritised input for product and engineering.
No one does all of it. Most DevRel roles lean towards one or two of these, and the posting tells you which.
The titles
| Title | What it usually leans towards |
|---|---|
| Developer Advocate | Content, talks and community; often the default DevRel title |
| Developer Evangelist | Similar to advocate, with more emphasis on outreach and events |
| DevRel Engineer, Developer Relations Engineer | More code: sample apps, SDK examples, integrations |
| Community Engineer, Community Manager | Running forums and programmes; engineering depth varies a lot |
| Developer Experience (DX) Engineer | Improving the product itself for developers: CLI, SDKs, onboarding |
| Developer Educator | Courses, workshops, learning paths |
| Developer Relations Manager, Head of DevRel | Leading the team, setting strategy and measuring impact |
Some of these sit close to other roles. Developer Experience Engineer is often a software engineering job with a developer-facing focus. Developer Advocate overlaps with the demo-heavy side of solutions engineering, and developer educators overlap with technical writers.
Where DevRel sits matters
DevRel can report to marketing, product or engineering, and that decides how your work is judged:
- Under marketing: reach, sign-ups, event attendance, content output.
- Under product: feedback quality, adoption of new features, developer satisfaction.
- Under engineering: SDK quality, sample code, time for a developer to make a first working API call.
None of these is wrong, but they are very different jobs. If the posting doesn't say where the team sits, ask in the first conversation. It's also fair to ask how they measure success, because DevRel impact is hard to measure, and a team that hasn't agreed on it may change its mind later.
An honest note on volume
DevRel teams are usually small compared with engineering teams, so even a large company may have only a handful of these roles. Our September 2026 snapshot of the boards Hot Jobs checks didn't break Developer Relations out as a separate figure, so we won't quote one. What we can say is that it's the kind of role where waiting for the perfect title is a slow strategy.
Ways to widen the net:
- Track every title in the table above, not just Developer Advocate.
- Add neighbouring roles: Solutions Engineer, Technical Writer, or a Software Engineer role if you'd also take a DX-focused engineering job.
- Target companies that build for developers. Among the boards Hot Jobs checks are developer-tool companies such as Supabase, Sentry, PostHog, Vercel, Netlify, GitLab and Grafana Labs, whose products depend on developers adopting them. Building your own target company list helps here.
- Read the location line carefully. DevRel roles are sometimes tied to a region because of events and time zones: "Developer Advocate, EMEA" means something different from a global role.
Your public work is your CV
For most roles your CV carries the application. In DevRel, hiring teams will look you up. What helps:
- Two or three pieces of content you're proud of: a tutorial, a talk recording, a sample repository with a good README.
- Evidence of community work. Moderating a developer chat, organising a meetup, maintaining an open-source project or answering questions on forums all count.
- Proof you can still build. A small app that uses the company's product, with a short write-up of what was confusing, is one of the most convincing things you can send.
You don't need a large audience. A few clear, useful pieces show more than follower counts.
How to read a DevRel posting
- Content, community or code? Count which verbs dominate: "write", "speak", "grow" or "build".
- Which ecosystem? Languages, frameworks and platforms the company's users work in.
- How much travel? Conference-heavy roles can mean frequent trips; ask how often.
- Who is the audience? Beginners, experienced backend engineers, data teams?
- What are the first-quarter goals? A clear answer is a good sign that the team knows why it exists.
Searching in Hot Jobs
The Developer Relations role in Hot Jobs matches titles containing Developer Advocate, Developer Relations, DevRel, Developer Evangelist or Community Engineer, including manager and head-of titles. Developer Experience Engineer and Developer Educator titles come through the Software Engineer (any) role instead, and plain Community Manager titles aren't matched by any role, so check those by hand if you want them.
Pick Developer Relations alongside Solutions Engineer or Technical Writer, choose the regions you can work from, and new postings from company career pages arrive in Telegram. It's €3, paid once, and you can change roles later with /settings. Connect the bot