Drive Auth0\'s developer advocacy by owning real-time presence across developer platforms, turning public feedback into product signals, and shipping high-signal content fast.

Own Auth0\'s developer presence on X, Reddit, HN, and other platforms with regular, authentic engagement.
Must-have: 4+ years in developer advocacy with proven public engagement.
Standout: Ability to ship fast, high-signal content during trending topics and influence product messaging.

Job Description

Responsibilities

Community Listening & Trend Response: Dedicate time to actively monitoring developer conversations on platforms like Twitter/X, Reddit, and Hacker News. You will identify emerging trends in identity/security and mentions of Auth0, converting these insights into immediate opportunities. This could range from drafting a thoughtful reply or a "hot-take" blog post to commissioning a video explainer or routing critical feedback to the Product/Marketing teams.
Own Auth0's Developer Presence on X and Beyond: Be the primary voice representing Auth0 in real-time developer conversations on X, as well as Reddit, Hacker News, Bluesky, and other platforms where developers gather. Post regularly, engage authentically, and build a consistent presence that developers actually want to follow.
Turn Social Into a Feedback Channel: Systematically capture developer pain points, feature requests, praise, and criticism from public conversations and route them to Product, Engineering, and Marketing with context. You are the bridge between what developers say in public and what the company does next.
Create Fast-Cycle, High-Signal Content: Write threads, short posts, quick takes, and lightweight explainers that ride the moment. When a topic is trending, you should be able to ship something valuable within hours, not weeks. Longer-form content (blog posts, video scripts) is secondary but expected when the moment calls for it.
Collaborate With Internal Teams: Work closely with Product, Engineering, Developer Relations, and Marketing to ensure that what you're seeing externally informs what we build and how we talk about it. Help shape launch strategies, messaging, and positioning based on real community signal.

Requirements

Experience: 4+ years in developer advocacy, developer relations, or a community-facing technical role, with clear evidence of sustained public engagement with developer audiences.
Established Social Presence: You have an active, authentic presence on X (and ideally other developer platforms). You don’t need to be famous, but you should have a track record of engaging meaningfully in technical conversations and a following that reflects that.
Technical Credibility: You can hold your own in a conversation about JavaScript/TypeScript frameworks, authentication flows, API design, or web architecture.
Speed and Editorial Judgment: You can assess whether something is worth responding to, draft something sharp, and ship it; all within a short window.
Communication: Exceptional written English with a voice that feels natural on social platforms, clear, opinionated when appropriate, technically honest, and never corporate.

Preferred

Domain Knowledge: Familiarity with Identity protocols (OAuth 2.0, OIDC, SAML) and web security best practices.
Content Versatility: Experience producing short-form video (screen recordings, explainer clips, Loom-style walkthroughs) for social distribution.
Network in the Ecosystem: Existing relationships or mutual recognition with developers, advocates, or creators in the JavaScript, full-stack, or security communities.

Benefits

health, dental and vision insurance, 401(k), flexible spending account, and paid leave (including PTO and parental leave)

Okta for Developers

Resources for developers using Okta’s Identity services: Okta's Customer Identity Cloud (aka Auth0 by Okta or CIC) and Workforce Identity Cloud (WIC). Follow us here for tutorials, webinars, videos, events, product updates, and news. Keep up with our global team of developer advocates.

Founded in 2009

San Francisco, California, USA

2 employees

developer.okta.com

Traffic Signals

Monthly Visitors

151.3M

Monthly Google Ads Budget

$430.8K

Traffic Source Mix

10.4%

Direct

60.3%

Referral

27.3%

Social

0.2%

Paid

1.6%

Headcount Trend

Current headcount: ~2

Responsibilities

Community Listening & Trend Response: Dedicate time to actively monitoring developer conversations on platforms like Twitter/X, Reddit, and Hacker News. You will identify emerging trends in identity/security and mentions of Auth0, converting these insights into immediate opportunities. This could range from drafting a thoughtful reply or a "hot-take" blog post to commissioning a video explainer or routing critical feedback to the Product/Marketing teams.
Own Auth0's Developer Presence on X and Beyond: Be the primary voice representing Auth0 in real-time developer conversations on X, as well as Reddit, Hacker News, Bluesky, and other platforms where developers gather. Post regularly, engage authentically, and build a consistent presence that developers actually want to follow.
Turn Social Into a Feedback Channel: Systematically capture developer pain points, feature requests, praise, and criticism from public conversations and route them to Product, Engineering, and Marketing with context. You are the bridge between what developers say in public and what the company does next.
Create Fast-Cycle, High-Signal Content: Write threads, short posts, quick takes, and lightweight explainers that ride the moment. When a topic is trending, you should be able to ship something valuable within hours, not weeks. Longer-form content (blog posts, video scripts) is secondary but expected when the moment calls for it.
Collaborate With Internal Teams: Work closely with Product, Engineering, Developer Relations, and Marketing to ensure that what you're seeing externally informs what we build and how we talk about it. Help shape launch strategies, messaging, and positioning based on real community signal.

Requirements

Experience: 4+ years in developer advocacy, developer relations, or a community-facing technical role, with clear evidence of sustained public engagement with developer audiences.
Established Social Presence: You have an active, authentic presence on X (and ideally other developer platforms). You don’t need to be famous, but you should have a track record of engaging meaningfully in technical conversations and a following that reflects that.
Technical Credibility: You can hold your own in a conversation about JavaScript/TypeScript frameworks, authentication flows, API design, or web architecture.
Speed and Editorial Judgment: You can assess whether something is worth responding to, draft something sharp, and ship it; all within a short window.
Communication: Exceptional written English with a voice that feels natural on social platforms, clear, opinionated when appropriate, technically honest, and never corporate.

Preferred

Domain Knowledge: Familiarity with Identity protocols (OAuth 2.0, OIDC, SAML) and web security best practices.
Content Versatility: Experience producing short-form video (screen recordings, explainer clips, Loom-style walkthroughs) for social distribution.
Network in the Ecosystem: Existing relationships or mutual recognition with developers, advocates, or creators in the JavaScript, full-stack, or security communities.

Benefits

health, dental and vision insurance, 401(k), flexible spending account, and paid leave (including PTO and parental leave)