Developer Relations Engineer

Prefect builds resilient Pythonic orchestration and MCP platforms for mission-critical workloads. The Developer Relations Engineer will own how developers learn to build with Prefect, Dagster, FastMCP, and Horizon by creating reference implementations, technical content, documentation, videos, and public presentations. The role also involves improving developer experience, representing Prefect in technical communities, and translating developer feedback into actionable product input.

Responsibilities:

• Ship reference implementations developers copy. Working, maintained examples: MCP servers with production auth, gateway configurations, agentic workflows that do something a person would pay for. The bar is that someone builds on your code in production, not that it demos well
• Teach people about agentic workflows. Take a product being defined in real time and make it understandable through demos, posts, talks, and video that a skeptical senior engineer finds honest. You'll work directly with product and engineering while the thing is still moving
• Make video a channel we're good at. We built a recording studio this year and publish across YouTube, LinkedIn, X, and TikTok. You'd own the technical end: what to build on camera, and how to make a fifteen-minute build watchable
• Improve DX by being the first user. Build with our tools before customers do, then file the issue, send the docs PR, and fix the example
• Represent us in public. Conference talks, PyAI, livestreams, podcast episodes, and participation in MCP and Python AI communities as a practitioner rather than a booth
• Bring the field back in. You'll see what confuses people, what breaks, and what's missing before anyone else does. Turn that into product feedback our engineering team can act on

Requirements:

• 6+ years writing software professionally, strong Python desirable. This is an engineering role with a public-facing job attached
• A public body of technical work we can go read: repos, posts, docs, talks, or videos developers used. One excellent thing beats ten mediocre ones, and we'd rather see the artifact than hear it described
• You've built things with LLMs and agents (MCP servers, tool calling, agent frameworks, retrieval) and have opinions about what breaks once it's in front of users
• You're good on camera and on stage, or you've clearly got it in you and can show us something. Comfortable isn't enough; a lot of this job is being watched
• You can run as a team of one. You'll choose what to build, ship it, and tell us honestly whether it landed. Nobody is going to hand you a content calendar
• You maintain or substantially contribute to a popular open-source project
• An existing developer audience: YouTube, X, Twitch, a newsletter, wherever
• Data engineering or orchestration background: Prefect, Dagster, Airflow, dbt. Half our community lives there
• You can hold a conversation with a platform or security engineer about SSO, RBAC, audit logs, and PII without changing the subject. Enterprise governance is where Horizon lives