Developer Relations Engineer

Prefect

2d•$149,000 - $219,000•Remote

About The Position

Prefect builds and operates resilient, Pythonic orchestration and MCP platforms -- Prefect OSS, Prefect Cloud, FastMCP OSS, and Horizon -- used for mission-critical workloads. Our Vision: Prefect will define automation for the context era. Our Mission: Curate an intelligent context layer that delivers the right information at the right time. Our remote first company is singularly focused on this vision and mission, and every team member directly contributes to their advancement. We've carefully created a supportive, high-performance culture - the operating system of our company - that empowers our team to do the best work of their careers and achieve their personal and professional aspirations. Our company operates both open-source and commercial offerings, partnering with Fortune 500 companies, data innovators, and fast-growing digitally native startups. We are looking for folks who want to join a remote-first team #LI-Remote to continue building an equally amazing company, product, and developer community. Role Summary We're hiring a Developer Relations Engineer reporting to our Chief Growth Officer. You own how developers learn to build with Prefect, Dagster FastMCP and Horizon. That means reference implementations people copy into production, technical content (including video), docs and DX gaps you find by being your own first user, and a public presence on stage, on stream, and in issue threads. Our Agentic platform, is becoming how enterprises govern all their agent workflows: who can reach which MCP servers, what data flows through them, how usage gets audited, how policy gets enforced. Whoever takes this role will help shape how the world learn about it: the demos, the talks, the reference implementations, while the thing is still being figured out. This is a generalist role by design. You'll write Python, appear on camera, review docs PRs, and file the bug you just hit, often in the same day. Time zones: Anywhere in the continental US. We're remote-first. Expect travel for events and a few days a quarter in our recording studio. We have a slight preference for candidates near New York or the Bay Area, but it isn't a requirement.

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.

Nice To Haves

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.

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.