Why This Role, Why Now

We are about to open-source a real piece of CanyonOS: our harness, our scaling, and our observability.

Until now our motion has been top-down and enterprise-led, and this role opens the second front. Developers sign up for tokens all the time. The open layer is how they find us, and how we organically build a base of users inside Enterprise AI.

We are ready for someone to own that motion full time.

About the Role

We are looking for a Head of Developer Relations to work directly with Canyon Code's CEO and Chief Architect and own the developer motion end to end: the open-sourced harness, scaling, and observability, the community around them, how we launch and position it, and how we show up in the rooms where AI infrastructure gets argued about. This is hands-on. You build the sample apps and write the posts yourself, and you hire into the function once it is working.

You're a fit if you…

• You have been the senior-most developer-facing voice at a developer-tooling or infrastructure company, in developer relations, developer advocacy, or technical marketing.

• You have grown an open-source project: run the repo, triaged issues, reviewed community PRs, cut releases, and taken a contributor base from near zero to a real community.

• You have owned a developer launch end to end: narrative, sequencing, Show HN, Product Hunt, launch-day support, and the follow-through in the weeks after the spike.

• A track record of conference talks and workshops, and standing in at least one relevant developer community.

• Credible as an engineer. You can build a sample application, instrument it, read a stack trace, and hold your own with a staff engineer who is skeptical of anything that smells like marketing.

• You can define and instrument the developer funnel — repo visit, install, first instrumented workflow, retained usage — and move those numbers deliberately rather than by vibes.

• Judgment about the line between the open layer and the commercial one. You will help decide what we give away and what we do not, and you understand why that sequence matters.

• Clear written communication: you can turn research-grade ideas into a narrative developers actually want to read.

• Self-driven; thrives in early-stage, ambiguous, fast-moving environments.

• Hands-on with the agentic stack: LangGraph, AutoGen, CrewAI, Semantic Kernel, or custom agent systems.Plus

• Fluent in the LLM observability landscape (LangSmith, Langfuse, Arize Phoenix, W&B Weave, OpenTelemetry) and able to articulate crisply where a new entrant wins and where it does not.Plus

• Model-serving and infrastructure literacy: vLLM, SGLang, Ray, or NVIDIA Dynamo.Plus

• You have built a developer community from zero, including the Discord or Slack side of it.Plus

• You have hired and managed developer relations or technical marketing people.Plus

Why Join

Early in something much larger

The open-source launch is the opening move, not the destination. Canyon Code is building toward agentic workflows that optimize themselves. The adoption you drive is what generates the data that makes the rest of it possible, which makes this role part of the machine rather than commentary on it.

Define the function

You are the first developer relations hire. The strategy, the community, the launch playbook, and eventually the team are yours to build rather than inherit.

Strategic weight, not a megaphone

You will sit in the decision about what we open-source and what stays commercial, working directly with the CEO. This is not a role that gets handed a finished product and asked to promote it.

A real product to launch

The observability layer is built and genuinely differentiated at the per-agent and per-call level. You are launching something developers will actually keep using, not vapor.

Work alongside the founding team

Daily collaboration with a CEO and Chief Architect who have deep experience in ML systems research and AI infrastructure platforms, and you build your own name in the process.