Developer Growth Engineer

About the role

You'll stay close to the developer ecosystem, build things that get Arcade noticed, and ship them fast. The projects you build don't go through the product roadmap - they run alongside it. They're designed to capitalize on trends, demonstrate what's possible, and get developers to pay attention to Arcade. Your work falls into two modes: engaging and building . Engaging means showing up in the places developers already hang out - Reddit, Discord, Hacker News, GitHub discussions - and being genuinely helpful. Not pitching. Not dropping links. Answering real questions about MCP, AI agents, auth, tooling, and the messy problems people actually run into. You'll develop a feel for what developers care about, what's confusing them, and where the market is heading - and feed those signals back to product and marketing to influence roadmap and prioritization. Building means turning those signals into action. Every month you'll ship 2-4 projects, demos, or experiments designed to ride trends, demonstrate what's possible with Arcade, and earn attention across the market. Partner integrations are a key part of this - building the connectors and demos that embed Arcade into the modern AI stack wherever developers are building agents. Additionally, when big news breaks - a new model drop, a major API change, a shift in the ecosystem - you're the person who has something live within hours. You'll stay tight with product and marketing to align on key themes, upcoming launches, and product announcements - so the things you build amplify what Arcade is shipping and capitalize on what's trending. You own the full loop: spot the opportunity, build the thing, ship it, and promote it back into the communities you came from - as an engineer talking to engineers. The insights you pick up along the way feed back to product and marketing to influence roadmap and prioritization.