Learn Computer Stuff
Home / UX & Product Design / Developer Advocate
UX & Product Design

Developer Advocate

You help developers succeed with a product, and tell the company the truth about what is wrong with it.

No degree needed Moderate technically, hard in stamina. It is public-facing work with an unclear finish line.


Can I actually do this?

Open without a degree, and unusually open to career-changers from teaching, support or community work — provided you can actually build. It is rarely a first job: the role depends on developers believing you have done what you are describing. It is also the least stable role on this site, being marketing-funded and often cut first in a downturn, which is worth knowing before you aim at it.

Who it suits. People who genuinely enjoy explaining things and can take a public correction without flinching.

Runway. You need real engineering experience first — the credibility is the job.

Coming from another job?

Coming from support or teaching with real coding ability? That combination is exactly what this role is, and it is undervalued by people who assume it is a marketing job. Backend Developer Technical Writer Help Desk / IT Support

Also advertised as

  • Developer Relations
  • DevRel Engineer
  • Technical Evangelist
  • Community Engineer

The route

Four stations, in order. Each one is a thing you finish before the next matters.

  1. Station one

    Learn it free

    Only the best few, deliberately. Every one of these is free to use — the pill on each card says exactly what is and isn't free.

    Google — Technical Writing courses

    Free to learn · no certificate

    Most of this job is explaining clearly, in writing, at speed. Free.

    MDN — Learn web development

    Free to learn · no certificate

    You need to be able to build the thing you are demonstrating. MDN is also a model of the register to write in.

    GitHub Actions — quickstart

    Free to learn · no certificate

    Samples that break in public are the occupational hazard. Test them automatically.

    See the full catalog in the explorer →

  2. Station two

    Attest strategically

    Nothing to buy. This role is hired on public evidence — talks, posts, sample code, answered questions — all of which is free to produce and permanently visible. A certificate adds nothing a hiring manager cannot already see.

    Nothing here is worth paying for

    No credential needed

    Nothing to buy. This role is hired on public evidence — talks, posts, sample code, answered questions — all of which is free to produce and permanently visible. A certificate adds nothing a hiring manager cannot already see.

  3. Station three

    Prove it

    A certificate says you passed a test. These say you can do the job.

    A tutorial that works when followed exactly

    Publish it, then watch someone follow it literally. Fix everything they trip on.

    A talk recording

    A meetup counts. The bar is being watchable, not being a conference keynote.

    Feedback you carried back to engineering

    Show a product change that happened because you reported what developers were struggling with. This is the half of the job people forget.

  4. Station four

    Get hired

    Search these exact titles

    • developer advocate
    • developer relations
    • DevRel
    • technical evangelist

    Who hires for this. Developer-tool companies, cloud vendors, API businesses and open-source foundations.

    Everything this role produces is public by nature, so hiring managers assess the actual output rather than a description of it. That is our reasoning about what is inspectable, not a verified hiring statistic.

    On salary

    We don't publish salary estimates. Numbers copied between blogs drift from reality, and a wrong number costs you real negotiating power. When we have a verified public source, it goes here with its date.


Where this route continues

· How we verify