Prefect
Developer Relations Engineer
Remote — the employer does not say where candidates may be based.
Location not stated
Employer listed it 4 weeks ago · Added yesterday
Been open since 4 weeks ago, still being checked, but it has been live a while.
Salary
$149,000–$242,000
Location
Location not stated
Timezone
Not stated
Contract
Full-time
Experience
Mid
Category
Software
Published by the employer
Remote flexibility
Undisclosed
The listing is advertised as remote but does not state which countries or regions candidates may work from.
Why this role is Undisclosed
We only label a role Work from anywhere, Region restricted or Work from home when the employer's own wording says so. We checked this advert under our current rules and found no country or region eligibility requirement in it. We don't guess, so it stays Undisclosed until the employer publishes enough location information. Here is exactly what the advert left out.
- Countries you can work from: Not stated. The advert only gives "Remote", which names no country you must live in.
- Whether the work is remote: Never mentioned. The role reached us through a remote job board, but the advert itself doesn't say the work is remote.
- Working hours: Not stated. No timezone overlap or set hours are mentioned, so assume nothing either way.
Worth a look all the same. Missing wording is usually a rushed job posting rather than a closed door, so ask where you can be based in your first message, before you write a tailored application.
What the employer says
- Source listing states candidate location: "Remote"
What Nomaders makes of it
- No residency or region requirement found in the job description
- Check with the employer before assuming you can work from abroad
The quotes above are the employer's own words; the reading is ours. Always check the original listing and employment terms before working from another country.
About the role
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.
About Prefect
Prefect builds automation for an unpredictable world. The last decade of automation was about protecting workflows from unpredictability; in the agentic era, unpredictability is the point. Our mission is to give people confidence in automated work, whether that work is a mission-critical data pipeline or a fleet of AI agents.
In August 2026, Prefect and Dagster, competitors for eight years, joined forces to build the next generation of automation infrastructure. Today, our ecosystem includes Dagster, the data platform; Prefect, the agent platform; and FastMCP, the leading open-source developer framework for the MCP ecosystem. Together, our open-source and commercial products are trusted by Fortune 500 companies, data innovators, and high-growth technology companies around the world.
We think of our culture as the operating system of the company. We’ve carefully created a supportive, high-performance environment that empowers our team to do the best work of their careers, have meaningful impact, and continue growing personally and professionally. We’re a remote-first team that values high standards, ownership, and thoughtful collaboration.
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.
What You'll Do
In your first year you will:
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.
Your Qualifications
Must have
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.
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.
Benefits
- ·Remote-first team with flexible-first culture
- ·Equity Stock Options
- ·401(k) with 5% company match (vests immediately!)
- ·Medical, Dental and Vision insurance
- ·Generous Parental Leave
How to apply
- 1Check the flexibility label above, undisclosed, matches where you plan to live and work.
- 2Tailor your CV to the role at Prefect, mentioning your remote working experience.
- 3Apply directly on the employer's careers page using the button below. Nomaders never handles your application.
Found 1d ago. Last checked today. Always confirm the details on the original posting, salary and location can change after publication.
Listing sourced from Company boards.
Similar roles
Other open software roles with comparable remote rules.
Free to apply, no account needed.
$149,000–$242,000 · You'll be taken to the employer's careers page.