Developer Success Engineer

Prefect builds automation, orchestration, and MCP platforms for mission-critical workloads. The Developer Success Engineer will provide technical support across Prefect and Dagster, diagnosing and resolving customer issues, owning cases through resolution, and improving documentation, tooling, and product feedback to prevent recurring problems.

Responsibilities:

• Clear the failure state, and prevent the next one. Diagnose problems across Prefect and Dagster installations, integrations, deployments, and the cloud and container environments they run in. Find the underlying "why" so your first response resolves the question and pre-empts the follow-ups. Turn what you learn into docs, debugging resources, and tooling that deflect repeat submissions
• Own what's ours; say no clearly to what isn't. Take full accountability for root causes inside our products' domain of control. For problems outside our Scope of Support, issue a principled no that still gives the customer a way forward. Helplessness erodes trust as fast as a wrong answer
• Support your findings, and ask customers to support theirs. Back every diagnosis with evidence and logic. Assume the customer is the expert on their own stack, ask for what you need to troubleshoot both sides of an issue, and explain why you need it. Leave room for the possibility you've missed something
• Give the best possible update every time, and say so when you're still building it. A half-baked answer sent fast is worse than a complete one sent when it's ready; but radio silence is worse than both. When an issue needs to be escalated, you stay the customer's single point of contact, keep them updated on a regular cadence, and close the loop
• Feed the product. File reproducible product issues and surface recurring failure patterns to Engineering and Product

Requirements:

• Python fluency at the level of reading and debugging someone else's code, not only writing your own
• Hands-on experience running workloads in at least one major cloud and in containers or Kubernetes, enough to troubleshoot a deployment you didn't build
• Experience with a workflow orchestrator (Prefect, Dagster, Airflow, or comparable) and a strong interest in the data engineering space it lives in
• A track record of technical, customer-facing work: support, solutions engineering, developer relations, or similar
• Clear enough written communication to explain a root cause to a skeptical senior engineer and earn their trust
• Direct experience with Prefect or Dagster specifically
• A history of open-source contribution, in any project
• SQL and data warehouse familiarity
• Experience building support tooling or automation