How to become a Developer Relations / Advocate

Represent developers inside the company and the company to developers: content, talks, docs and community.

24-40 weeks4 phases14 steps13 free resources4 checkpoint tests

Before you start this one

Real engineering experience plus a public body of work - talks, writing, open source or community organising. DevRel is credibility-first, and credibility takes time to build.

Best for

Engineers who enjoy teaching and being public, and who can take feedback in the open without flinching.

Maybe not for you if

Anyone who dislikes visibility, or who wants it as an easier route than engineering. It is not easier - it is engineering plus communication plus travel.

The 4 phases

What each phase gets you to. The steps, resources and checkpoint inside each one open with a free account.

  1. Phase 1 - Be a credible engineer

    8-13 weeks

    Goal: Have something real you built, documented and supported, that survives being questioned.

    3 steps · ends in a scored checkpoint (70% to clear) · assumes working engineering experience

  2. Phase 2 - Learn to explain in public

    6-10 weeks

    Goal: Publish consistently enough that someone finds you useful.

    4 steps · ends in a scored checkpoint (75% to clear)

  3. Phase 3 - Speak and build community

    7-11 weeks

    Goal: Present to a room, teach a room, and help run something that is not yours.

    4 steps · ends in a scored checkpoint (70% to clear)

  4. Phase 4 - Make the impact legible

    3-6 weeks

    Goal: Show that your work changed something measurable, inside the company as well as outside.

    3 steps · ends in a scored checkpoint (70% to clear)

Open the full Developer Relations / Advocate roadmap

Free account, no card. It takes about a minute and you do not need to verify your email to start.

  • All 14 steps, in order, with why each one is there
  • 13 hand-picked free resources, no paid course upsells
  • The specific mistake people make at each stage
  • 4 scored checkpoint tests, so progress is earned not ticked
  • Progress saved per step, so a break does not cost you the thread
  • Adaptive start, phases your test history already clears are skipped

What hiring actually looks like here

DevRel hiring in India clusters at API and developer-tool companies and at the India teams of global platform vendors, under titles like Developer Advocate, Developer Educator, Technical Content Engineer and Community Manager. Listings ask for engineering experience plus links you can send today: a repository, a post, a talk recording. The role is commonly filled by people who already had that public track record, which is why the path below is mostly about building one.

We claim no placement outcome, salary or success rate. This describes what is commonly reported about the role, nothing more. Linked resources are credited to their authors.

Comparing paths?