Account Development Representative

Required

• You have operated at the intersection of AI and marketing at a level most marketing leaders haven't reached; You may have been a head of marketing or CMO at an AI company, a developer tools company, or a foundation model provider; You understand the ecosystem from the inside, not from a distance
• You build with the tools you're asking your team to use; You are fluent in agentic workflows, e.g., Claude Code, Cursor, or equivalent; You can direct agents to produce content, run programs, and ship at a pace traditional marketing orgs can't match; You don't delegate this fluency; You model it
• You think about content as infrastructure; You have made deliberate decisions about what gets indexed, surfaced, cited, and trained on; You understand that documentation quality, code example density, and dataset presence are distribution levers, not support functions
• You are obsessed with developer discovery; You wake up thinking about how a developer or an agent encounters MongoDB for the first time, through a search result, an LLM citation, a framework recommendation, or an agent tool call; You know the difference; You have a strategy for each
• Technical enough to be credible with engineers, product leaders, and technical partners; You don't need to write code; you just need to understand how LLMs are built, how retrieval works, and how agents select tools; You can sit with an engineering team and know what questions to ask
• You've influenced a product roadmap from a marketing seat and can point to a specific acquisition or adoption outcome that resulted; This isn't a nice-to-have; it's core to the role
• You have a partnership instinct; You identify emerging frameworks and companies before they're obvious and move fast to establish presence before defaults are set; When a new agent framework launches, you're already in the room
• Experience influencing how a product is represented in systems you don't control, through documentation strategy, training data presence, API/integration design, or developer ecosystem positioning; You have done this deliberately, not accidentally
• You've shipped something (i.e., a system, a channel, a program) that changed how a technical audience found or chose a product; You can point to it and explain exactly what you did
• You have owned a content, documentation, or developer marketing function and have a measurable outcome to show for it; Not a strategy deck; An outcome
• Track record of holding cross-functional partners accountable without a formal reporting line; You'll bring product-owned content under the same accuracy standard as marketing's, without owning the reporting line
• A builder and an operator; Small team, high visibility, hands-on role