DeepL
Developer Growth, API & Agentic AI Products
About this role
DeepL is seeking a Developer Growth specialist to drive adoption of its API, MCP server, and CLI tools within the AI agent ecosystem. You'll own distribution strategy across agent marketplaces, optimize the activation funnel from install to paid usage, and create developer resources that accelerate adoption across emerging agentic workflows.
What you'll do
- Drive MCP and CLI discoverability across Claude, ChatGPT, Copilot, and agent marketplaces
- Optimize the activation funnel from product install through first paid usage
- Identify and resolve friction points in the developer onboarding experience
- Create prompt libraries, agent templates, and integration guides for developers
- Monitor the agentic tooling ecosystem and identify distribution opportunities
- Instrument analytics end-to-end to track adoption and growth metrics
What they're looking for
- Developer relations and ecosystem strategy
- Product analytics and funnel optimization
- API and CLI adoption growth experience
- Technical documentation and code examples
- AI agent and agentic workflow knowledge
- Marketplace and distribution channel expertise
- Cross-functional collaboration with engineering and product
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
DeepL
DeepL builds translation APIs and developer tools designed to integrate with AI agents and applications. The company is hiring for Developer Growth and related roles to expand adoption of its API, MCP server, and CLI tools within the AI agent ecosystem.
- Website
- deepl.com
Likely interview questions
- Walk us through how you would approach getting DeepL's MCP server adopted across Claude, ChatGPT, and Microsoft Copilot ecosystems—what distribution channels and partnerships would you prioritize first?
- Describe your experience instrumenting and optimizing activation funnels. How would you identify and address the highest-friction point in converting MCP/CLI installs to paid usage?