Role Description
Weβre looking for a DevOps practitioner who builds the runnable proof (pipeline templates, working examples, self-serve tutorials) that lets a developer go from βmy pipelines canβt handle AI-generated codeβ to "ran a real pipeline successfully" without help. If something you built doesn't survive a skeptical engineer poking at it live, it doesn't ship.
-
Start from the pain point, not the product:
-
Pick the DevOps/developer problems teams hit most often, then build the working solution and the narrative around it, before deciding what format it becomes.
-
Build forkable, production-realistic pipeline templates and code samples (CI, CD, GitOps, feature flags) that developers can clone and adapt directly, not superficial demos.
-
Own the "zero to first pipeline run" self-serve paths for our flagship products, and validate them by having real, unassisted users run through them.
-
Record short technical walkthroughs and live coding demos of real CI/CD workflows on Harness.
-
Own the example-repo strategy: the canonical, maintained source of truth.
-
Keep every sample and tutorial working as the product changes; stale examples cost more trust than no examples.
-
Show up in developer communities (GitHub Discussions, Discord, relevant subreddits) and understand developer pain points and answer real questions first, turn the best ones into content second.
-
Be the technical sign-off on content produced elsewhere on the team. If a use case or demo is wrong, you're the one who catches it before it publishes.
Qualifications
-
Real, hands-on CI/CD experience: you've built and maintained pipelines in production, not just used one someone else configured.
-
Comfortable writing YAML, scripting (Bash/Python/Go), and working across git, containers/Kubernetes, and common CI/CD tooling (Jenkins, ArgoCD, or similar), familiarity with GitOps/progressive delivery, SAST/SCA, or DORA metrics.
-
Background as a software engineer or DevOps practitioner: someone who's shipped, not just covered the space.
-
Can write clearly for other engineers: a tutorial, not just code comments.
-
Comfortable on camera or mic for short technical content: we'll coach delivery; the technical judgment has to already be there.
-
Self-directed: you spot the gap in self-serve content and build the fix without waiting on a brief.
Requirements
-
Nice to have: Direct experience with Harness, or a comparable platform.
-
An existing presence in a developer community, or a personal technical content portfolio.
Benefits
-
Competitive salary.
-
Comprehensive healthcare benefits.
-
Flexible Spending Account (FSA).
-
Flexible work schedule.
-
Employee Assistance Program (EAP).
-
Flexible Time Off and Parental Leave.
-
Monthly, quarterly, and annual social and team building events.
-
Monthly internet reimbursement.