Founding Developer Relations Engineer

The role

The best way to explain Orchestra is to build something worth trying. Take a real AI task, show what good looks like, and let developers reproduce the improvement themselves. That could mean a better prompt, a different model route, or a specialist trained for the work.

You will work directly with the founders and engineers to build our developer relations program from the ground up. You will write code, make demos and videos, bring builders together, and help their first experiments become recurring workloads. You will also use what you learn to make the product easier to adopt.

What you’ll build

• Ship runnable sample apps, integrations, and tutorials that take a developer from a real task to an evaluated improvement.
• Turn product and research work into clear technical stories: write-ups, demo videos, live walkthroughs, and short posts that show both the result and how to reproduce it.
• Create useful model comparisons and experiments, with explicit baselines, quality checks, latency, cost per completed task, and limitations.
• Bring developers together through hands-on workshops, hackathons, and small events where people leave with something working.
• Build relationships with open-source maintainers, model providers, and developer communities; find integrations and joint projects that help both communities.
• Help developers through their first workload, identify where they get stuck, and work with engineering to improve documentation, examples, and product behavior.
• Own distribution and follow-through: publish where the relevant builders spend time, respond to their questions, and learn which projects bring them back.

What you bring

• You can build and debug working software in Python or TypeScript, use APIs, and read a diff. You have built with language models and understand the tradeoffs behind a demo.
• You explain technical ideas clearly in writing, on camera, or in front of a room, and enjoy helping other developers get something working.
• You have evidence of work people used or learned from: an open-source project, tutorial, video, integration, workshop, or community you helped build.
• You choose useful projects, ship quickly, and own the details from the first experiment through publication and developer follow-up.
• You have good judgment about evidence and can explain what an experiment demonstrates, where it falls short, and what should be tested next.

Experience with evaluation, fine-tuning, model serving, or growing a developer community is helpful. Your previous title matters less than the quality of what you have built and your ability to bring people along.

What success looks like

• Developers can follow your examples, complete a useful first workload, and understand whether Orchestra improved it.
• Your demos and technical stories reach the right builders and lead to active projects, repeat usage, and concrete customer conversations.
• Developer feedback leads to specific improvements in the product, documentation, and integrations.
• You establish a repeatable rhythm of building, publishing, meeting developers, and improving what comes next.

Tell us what you’ve built.

Send us something you built and something you helped people understand. Tell us who used it, what you personally did, and what happened next. A repository, tutorial, video, or event recap is welcome. We would also like to hear one demo or developer program you would start at Orchestra. Please leave out confidential material.

Opens your email app. You can also write to founders@orchestra.ai.