Content Engineer, Developer Relations

Harness is the AI Software Delivery Platform company, led by technologist and entrepreneur Jyoti Bansal. The Content Engineer in Developer Relations role focuses on evangelizing the Harness AI platform by designing and building practical use cases, producing technical content, and collaborating with various teams to ensure alignment and effectiveness.

Responsibilities:

• 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

Requirements:

• Deep, hands-on fluency with Harness or a comparable CI/CD, IDP, or DevOps platform: Familiarity with the broader DevOps/platform engineering space: GitOps, progressive delivery, SAST/SCA, DORA metrics, enough to design a use case from a blank slate and build it yourself, not follow someone else's script
• A portfolio of technical content you've personally produced: concept, execution, and camera/edit, not just cut from footage someone else designed and shot. Links, not a reel
• Comfort operating your own recording setup, remote or in-person, with technical practitioners who are not professional presenters
• The instincts of a practitioner: you think about a problem the way the person you're filming or the person you're creating the content for does, and you can tell the difference between a demo that's honest about friction and one that's just polished
• Self-directed and productive: you don't wait for a brief. You spot the use case, build it, film it, and know what's worth keeping
• Genuinely creative about capturing developer attention: you have your own ideas about what makes a technical audience stop scrolling and actually watch, and you'll push for the weird format or unconventional angle when the standard playbook feels stale, not just execute the four formats we've already defined
• Engineering background: people who can write code well enough to have opinions about it, and have since moved towards explaining and teaching it
• Existing video/production craft (framing, pacing, basic edit). We'll build on this, not require it on day one
• A personal or team technical content channel you've grown yourself