Harness Engineer: the developer job of tomorrow?
It’s quite likely.
Indeed, the better agentic development models and tools get, the more the developer’s role shifts up a level.
Little by little, developers are leaving implementation details behind (where AI is already more relevant, and faster, than most developers), to move up to the level above: architecture, conventions, technical choices, business rules.
And when you barely write code by hand anymore (or not at all), there is ONE thing that acts as a guardrail for the models: the Harness.
The Harness is everything around the AI model that makes an agent do what you want it to do. Instructions, tools, rules, tests, hooks, CI…
It’s the part I take care of for my clients.
And watch out, this is nowhere near blind, uncontrolled vibe-coding.
It’s the exact opposite.
What a Harness Engineer has to do
The Harness Engineer has to:
- define a strict framework, know what they want and what they don’t
- make as many rules as possible impossible to break
- spot drift as early as possible and fix the harness as they go
- deal with technical debt as fast as it shows up
A whole new set of skills
They also have to master a whole new area of knowledge: context management, long sessions, multi-session tasks, orchestration, cost optimization…
… and on top of all that, they will very often be the only developer on the codebase. So full-stack skills, infra, even design or product.
The final boss of development
In short, the Harness Engineer is to development what the final boss is to a video game. The ultimate senior, able to run a horde of agents without sacrificing quality.
My bet: within a few months, this job title will be trending on LinkedIn :) — one more symptom of the ongoing shift in the developer market.