Responsibilities

• Social—be where the conversation is
• Own SageOx's voice on X and LinkedIn. Publish on cadence, every week: threads, posts, short video, and the occasional longer piece. The raw material comes from the founders, the team's own experiments with agents, customer stories, and shipped features; you turn it into things people actually read.
• Be a real presence, where builders compare notes. Reddit, Hacker News, and the Discords and Slacks of the agent tools themselves — the Claude Code, Cursor, Codex, and MCP communities. Show up as a person, be useful, know who the interesting voices are, and be one of them.
• Run launches. When we ship something worth announcing, own the moment end to end — Hacker News, Product Hunt, the coordinated push across every channel, and the follow-through in the comments.
• Amplify the founders and team. Identify the highest-impact platforms, podcasts, and moments for the founders and other team members to show up, get them there, and shape what they say so it lands.
• Bring outside-in signal back. What people are asking, what they're confused by, who's comparing us to what — surfaced to the core team continuously. What you hear in public is a deliverable, not a byproduct.
• Events—put SageOx in the room
• Own event presence end to end. Pick the events worth being at across San Francisco, Seattle, and other builder hubs, and decide how we show up — talk, demo, booth, dinner, sponsorship, or just being there.
• Host our own. Meetups, hackathons, workshops, and small dinners for the teams building with agents. Start small and repeatable; grow what works.
• Turn every event into a pipeline. Know who's coming, who we met, and what happened after. An event that produced no conversations worth following up on is an event we shouldn't repeat.

Requirements

• 2–7 years in developer marketing, community, DevRel, social, or events — for a technical product with a builder audience. The title matters less than the evidence: audiences you've grown, events you've run, and what happened after.
• Mission alignment: believes deeply in what SageOx is building. Lives and breathes the product every day, all day long.
• Complete fluency with AI: you use AI throughout your own work, and you're curious and knowledgeable about the ecosystem — emerging technologies, products, practices. The pitch is only credible from a practitioner.
• Has personally grown an audience, a community, or a channel somewhere. Show us.
• Has run events people wanted to come back to — from a 10-person dinner to a hackathon.
• Technical enough to be credible: you can explain what an MCP server is, demo the product, and follow an engineer's answer without needing it translated.
• Thinks deeply, communicates clearly, writes well: AI slop is all around us — stand on your own thinking, clarity, and craft. Bonus if you're good on camera.
• Strong sense of ownership: owns outcomes; makes things happen with limited resources; has a great sense of direction and prioritization amid the ambiguity of an early-stage startup.
• Cultural fit: embodies SageOx's values.

Preferred

• Great to have
• Already connected to the builder scene in Seattle, San Francisco, and online — you know who to invite.
• An existing audience of your own among builders.
• Founder or early-employee experience somewhere that grew fast.
• Experience with open-source products or developer communities.
• Location — Seattle or San Francisco, in person