Content Engineer, Developer Relations
About the role
Position Summary
This role exists to evangelize the Harness AI platform, not by describing what it does, but by using it. You'll design practical use cases that show what a specific Harness capability actually solves for a practitioner, build that use case yourself inside the platform, and turn it into content that lets other practitioners design and execute the same thing on their own.
Video is part of the job, but it's the part we can coach. Our team can teach you how to run a shoot and cut a piece the way the best technical demo producers at developer-obsessed companies do it. The must-have skill is technical judgment, i.e., knowing which use case is worth building, where the real friction is, and how to demonstrate it credibly to someone who'd see through a scripted demo in five seconds. That has to be there on day one.
About the role
- Design practical, realistic use cases inside Harness: the kind of problem a developer, a platform engineer, or a DevOps lead actually has, and build them yourself, end to end, inside the product
- Run your own shoots (remote or in-person) with technical practitioners, including our Field CTOs: you operate the capture, not just receive footage from someone else
- Produce technical content around each use case: concept, execution, and final piece are all yours, start to finish, across video and writing
- Evangelize specific Harness AI capabilities (CI, CD, IDP, security, AI cost) in ways that map directly onto a practitioner's real workflow, not a feature list
- Partner with our production team to sharpen craft: pacing, visual packaging, delivery, while owning the technical substance yourself
- Pitch and pilot new formats and hooks on your own initiative
- Let performance data steer what you build next: watch time and returning viewers tell you which use cases and capabilities are actually resonating, not a fixed calendar alone
- Cross-functional partnership: You'll work closely with Product, Engineering, and the Field CTOs to source real use cases, and with Product Marketing to keep messaging aligned, but the execution and editorial judgment are yours