Specification Engineer
What a Specification Engineer Is
A Specification Engineer converts ambiguous intent into decidable conditions.
They do not implement. They do not estimate. They own one artifact: the specification — written independently of any implementation, verifiable without asking the author what they meant.
What the Role Requires
Every requirement must resolve to true or false.
"Fast" is not a requirement. A percentile, a threshold, a measurement point, and a list of exclusions — that is a requirement.
No undefined case remains.
Concurrent actions. Expiry boundaries. Partial failures. The combination space is closed before implementation begins.
Conflicting requirements are forced to a decision.
Not smoothed over. Named, dated, and recorded with the people who chose.
Ambiguity terms are eliminated.
No "appropriate." No "promptly." No "as needed." Each is replaced with a measurable definition.
Tests derive from the specification, not from the code.
This is the only artifact independent of what was built.
What the Role Is Not
- Does not implement. Specifying how couples the requirement to one solution.
- Does not review code. Reviews verdicts against acceptance conditions.
- Does not own delivery dates. Schedule pressure absorbed into a specification is how gaps are produced.
- Does not decide anything that cannot become a pass/fail condition.
Why It Becomes More Important as AI Accelerates Implementation
When implementation is slow, gaps in the specification are absorbed downstream — by engineers who fill them with assumptions. When implementation is fast, those same gaps ship immediately.
The faster the build, the more precisely the specification must be written before the build begins.
The Success Signal
Nothing happens.
Incidents that were prevented are unobservable. The measurable proxy is the absence of a particular question: is this a bug or the intended behavior?
Organizational Precondition
The role surfaces undecided questions. It cannot decide on the organization's behalf.
Where decisions are avoided, the position produces friction and no output.
A specification is not a description of what will be built. It is a condition that what is built must satisfy — written before anyone knows how.