About the role

We’re hiring a Developer Relations Engineer to help developers understand, evaluate, and build with Recursive’s models and tools. Recursive is building AI that improves AI, starting with automated AI research. You’ll turn technical progress into runnable examples, clear explanations, and practical learning experiences for developers.

You’ll work closely with research, engineering, product, and marketing, writing code and teaching from what you build. You’ll help establish how we support an early developer community and bring its experience back into the product, from first experiments through repeated, useful work.

Where you can make an impact

• Developer education: Make emerging capabilities understandable through tested examples, tutorials, and practical explanations of strengths and limitations.

• Community and adoption: Help developers get started, build useful projects, share their work, and learn from one another.

• Developer experience: Identify where builders get stuck and turn those observations into improvements to documentation, tooling, and product interfaces.

What you’ll do

• Build and maintain working demos, example applications, and reference integrations that show useful applications of Recursive’s released capabilities.

• Create technical tutorials, documentation, videos, and walkthroughs that take developers from setup to a working result, including how to evaluate whether it works.

• Work with researchers and engineers before launches to understand new capabilities, test examples, and prepare accurate developer materials as access becomes available.

• Run hands-on workshops, office hours, and selected hackathons or meetups; answer technical questions and help developers work through implementation problems.

• Build relationships with developers, open-source maintainers, and ecosystem partners; support community projects and make it easy for people to share what they learn.

• Bring recurring developer issues to product and engineering, contribute fixes where appropriate, and measure progress through successful onboarding, useful projects, and continued use.

What we’re looking for

• Strong software engineering skills and a track record of shipping applications, developer tools, or integrations that other people use.

• Hands-on experience with AI models, APIs, or agent workflows, and the ability to debug examples and explain their implementation choices.

• Clear technical writing and teaching, supported by examples such as tutorials, repositories, documentation, talks, or workshops you created.

• Developer empathy: you can understand an unfamiliar workflow, reproduce a problem, and help someone make progress without losing technical precision.

• Good judgment about demonstrations and claims, including how to explain model limitations, evaluation results, and practical deployment tradeoffs.

• Ownership and adaptability. You can choose worthwhile projects, deliver them independently, and work constructively across technical teams and communities.

Especially relevant experience

• Developer relations, developer advocacy, technical education, open-source maintenance, or engineering work with a substantial teaching component.

• Public examples of tools, sample applications, or technical content that helped developers complete a task or adopt a new technology.

• Experience designing hands-on learning programs, building community relationships, or supporting developer events.

• Experience with AI development tools, coding agents, research software, or emerging developer platforms, including using feedback to improve the product.

What success looks like

Developers can move from curiosity to a working project with clear guidance and dependable examples. They return because the tools and community help them do useful work. You can show where education improved adoption and where developer feedback led to better documentation, interfaces, or product behavior.