About Imbue

Imbue is a radically different AI company. We believe that data should belong to you, humans should come before technology, and everyone deserves to own a personal team of AI agents. We believe in a future of open agents that you can modify to do exactly what youwant. We’re building a suite of tools to make tech serve humanity, and making it open source.

Some first projects include

• mngr: A command-line tool for managing agents
• Vet: A standalone tool that catches AI coding mistakes and reviews full PRs
• Offload: A tool that automatically distributes your tests to run in isolated sandboxes
• Latchkey: A command-line tool to integrate local agents with third-party APIs
• Darwinian Evolver: A near-universal optimizer for code and agents

And we’re just getting started. If you’re excited about building a future with open agents, say hi!

We're supported by investors like Nvidia, Simon Last (co-founder of Notion), and Eric Schmidt (former CEO of Google), with $200M raised at over $1B valuation.

About the Role

You’ll be the conduit between Imbue's products and the developer communities they empower — helping us reach builders, curious engineers, and early adopters to build a strong and engaging community. This is the company’s first developer advocate role. You’ll experiment with different content types, community channels, and help shape how open software is created in the age of AI. You live on the internet. Not metaphorically, you're genuinely plugged in across every platform that matters. You’re specifically active on all things AI and Agent Tech Twitter and you’ve explored OpenClaw, ideally from its beginnings as Clawd.

We aim to make Imbue a beloved brand in developer communities, and you'll be a driving force behind that. As the voice of our company, and our founders, you’ll write and publish content to elevate our presence in a playful, and proactive direction

Our message is simple and worth fighting for: technology is meant to serve humans, not the other way around. Your job is to make the world hear it.

What You'll Do

Own our channels!

• Evangelize what we’re building and why it matters on X(Twitter), GitHub, LinkedIn, Hacker News, and across developer forums.
• Help shape conversations around Imbue’s developer tools. Posting, engaging, replying, and building community in real time, all the time.
• Manage and grow our X account as a primary channel for reaching developers, founders, and technical builders.

Build content

• Evangelize Imbue’s mission, software, and features. Turn the technical details of what we build into relatable messaging, video demos, use case examples, and stories that developers trust.
• Create documentation that is accurate and useful. Improve onboarding, nurtures, and our documentation structure to set new users up for success and reduce friction.
• Write on behalf of Imbue’s technical co-founders, Kanjun and Josh, and help them build personal brands that amplify the mission.
• Identify opportunities and drive adoption to Imbue’s open source projects on GitHub. Enrich ReadMe’s, jumpstart discussions, raise issues, and foster growth to help our repos trend within the platform.

You are someone who

• Lives and works in the San Francisco Bay Area!
• Worked as a software engineer at a tech startup or regularly contributes to open source
• Enjoys building communities and wants to shape the future of software, together
• Regularly hacks, builds, and tries the latest coding agents, tools, and features on day one of release
• Thinks and writes in posts: you're always noticing things that would make sharp, punchy content
Gets excited about turning complex technical ideas into accessible and fun stories

All submissions are reviewed by a person, so we encourage you to include notes on why you're interested in working with us. If you have any other work that you can showcase (open source code, side projects, etc.), certainly include it! We know that talent comes from many backgrounds, and we aim to build a team with diverse skillsets that spike strongly in different areas.

We try to reply either way within a week or two at most (usually much sooner).