Developer Relations: market

Vacancy

an open job that cleared the quality gate and lists at least two technologies

Observed candidate

a candidate whose stack contains this technology; an aggregate — not a single record leaves the perimeter

Matchable candidate

not counted yet

Window

jobs open at the moment the snapshot was built

The DevRel stack is hybrid: dev tools + content tools + community platforms. Code & demos: GitHub (demo repos, OSS contributions), Replit (live-coding demos), CodeSandbox. Content: dev.to, Medium, Habr (Russian-speaking audience), HashNode, personal blog on Vercel/Netlify. Video: YouTube (tutorials, talks), Twitch (live-coding), OBS Studio for recording, Camtasia/Final Cut for editing. Social: Twitter/X (the de-facto DevRel channel), LinkedIn, Mastodon/Bluesky (growing trends). Community: Discord, Slack communities, GitHub Discussions, Reddit AMA. Analytics: GA4, Plausible, Twitter Analytics, YouTube Analytics, GitHub Insights. Conferences: Sessionize for CFP management, Notion for talk prep. Presentation: Keynote, slidev (Markdown-based), Figma for slide design.

DevRel requires a unique combination of engineering and communication skills. Engineering (must-have): a confident Senior level in the product's stack (usually one backend language + frontend basics + one cloud). Without technical depth DevRel = just marketing. Public speaking: ability to present to 100–2000+ developers at conferences, do live-coding demos without freezing under stress. Technical writing: clear tutorials, 5-15 minute reads, blog posts, documentation. Video production: recording + editing tutorials on YouTube, live streams on Twitch. Community management: running Discord/Slack, responding to GitHub Issues, moderation. Empathy for developers: understanding the pain points of the target audience (backend devs vs frontend vs DevOps need different angles). English C1+ — mandatory for international (most DevRel jobs are global). Metrics: reading DAA, MAU, conversion funnels.

Yes: 49% of DevRel jobs are full-remote. DevRel is global-remote by nature: content is created asynchronously (blog posts, YouTube videos), community runs 24/7 (Discord, GitHub), conferences are worldwide. Especially common at developer-tool companies — almost all DevRel teams are distributed. Conference talks require travel (4-8 times a year typically, travel budget covered by the company). Russian DevRel jobs (JetBrains, Yandex Cloud) more often require hybrid/office due to live events with a Russian-speaking audience. Junior remote openings are scarce — DevRel skills are hard to learn without mentorship on conference trips and content review.

DevRel is a hybrid of all three with a focus on developer audience activation. Metrics: DAA (Developer Audience Activation), community growth, content reach. Technical Writer — a narrow role: creating documentation, reference docs, tutorials. Less outreach. Marketing (B2B SaaS) — focused on lead generation and conversion, not on developer relationships. Metrics: MQL, CAC, conversion rate. Engineering — focused on product code, not on communication with users. By pay: Senior DevRel ≈ Senior Engineer > Senior Technical Writer > Senior B2B Marketer. DevRel combines engineering credibility with content/community skills. Product Marketing Manager (PMM) at developer-tool companies is sometimes close to DevRel (especially at startup stage when one role covers both functions).

DevRel is NOT an accessible entry role. You need 3-5 years of engineering experience + a notable community presence. The optimal path: 1) Become a Senior Backend/Frontend/DevOps. 2) Start a blog (dev.to, Medium, Habr) — 10-20 serious posts over 12-18 months. 3) Build a Twitter/X with 2K-5K technical followers. 4) Speak at 3-5 meetups locally, then apply to international conferences (Sessionize opens CFPs). 5) Open-source contributions to the target company's product or a crowd favourite (React, Vue, Next.js). 6) Apply for Junior/Middle Developer Advocate with a ready portfolio (blog + talks + GitHub). Books: "Developer Marketing Does Not Exist" (the DevRel book), "The Business Value of Developer Relations" (Mary Thengvall), DevRel.Agency blog. English C1+ — must-have. Courses: DevRel Foundations on CodeSchool.

As of the latest data refresh, the Zorky CRM sample contains 328 active open DevRel positions across CIS and Eastern Europe. These are postings published in the last 90 days — companies actually hiring. Geography is distributed; the leaders are US, GB, IN. DevRel is one of the most niche roles by job volume: developer-tool companies usually keep teams of 2-10 advocates, not more. Most Russian-speaking DevRel work for international SaaS on remote. Data is collected from 101 job boards and 15 780 company career sites: Telegram channels (DevRel communities + job announcements from international tool companies), specialised job sites, dedicated platforms (DevRel Collective, DevRelX Jobs).

Cyprus — a growing hub for Russian-speaking DevRel relocants on international pay. The main driver — English C1+ + a strong community presence (Twitter followers, blog reach, conference talks).

Senior DA — the full DevRel-function stack + ownership of strategy. Engineering depth: Senior level in the company's product stack (without this DevRel = just marketing). Content production at scale: 1-2 blog posts per month + 1-2 YouTube videos + regular talks. Public speaking: 6-12 conference talks per year (KubeCon, JS Conf, GopherCon, regional meetups). Community management: running Discord/Slack with 1K+ members, GitHub Issues triage. Strategy: designing DevRel programmes (workshops, hackathons, beta programmes), metrics (DAA, community growth, content reach). Cross-functional: collaboration with PMM (product marketing) on launches, with Sales on enterprise outreach, with Engineering on product feedback from community. English C1+ for international content and talks. Mentoring junior advocates. Travel readiness: 4-8 trips per year to conferences.