Developer Relations Engineer (DevRel)

Role overview Create technical content and build an active developer community around infrastructure for AI applications. This remote DevRel role combines software development, education, community programs, and product feedback, with a focus on helping developers get from working examples to deployed applications.

Responsibilities - Write and publish end-to-end tutorials, starter kits, deployment guides, technical articles, comparisons, and benchmarks. - Build demo applications and deployment templates, including examples that connect with coding assistants and the Model Context Protocol ecosystem. - Record walkthroughs and live coding sessions, and distribute technical content across relevant channels. - Manage developer discussion spaces and organize virtual hackathons, AMAs, and deployment challenges. - Represent the product at conferences and meetups, and develop a developer ambassador program. - Turn community feedback into product insights, reproduce reported bugs, and bring developer needs into planning.

Requirements - 2–5 years in developer relations, technical advocacy, or technical content creation. - Strong software engineering skills and ability to write production-quality code in Node.js, Python, or TypeScript. - Experience deploying and operating web applications, including containers, cloud infrastructure, and CI/CD. - Clear communication skills, with the ability to explain technical topics accessibly. - Active participation in developer communities and a genuine interest in helping developers build.

Nice to have - Experience with MCP or LLM-powered developer tools. - Previous DevRel work in developer tools, cloud, or AI infrastructure; a public record of technical writing, talks, or community contributions; or multilingual communication skills.

Benefits and work setup Remote role with salary, equity, health benefits, and flexible paid time off. The position includes direct access to product decision-makers and room to shape a technical advocacy program. Example first-year success measures include publishing at least eight guides and growing the community by 500 members.