Spec & Requirements Writing
Spec writing is the skill of describing what to build precisely enough that a team can build it without you in the room. It is assessed on whether edge cases and non-goals are handled — that is where specs fail, not on formatting.
Also called: PRD writing, requirements, technical specification
What is spec & requirements writing?
Specification writing covers stating the problem, defining scope and explicit non-goals, handling edge cases and failure states, defining acceptance criteria, and writing so the reader can act without asking a clarifying question.
Ambiguous specs are re-litigated in every standup for the length of the project. A spec that resolves ambiguity before implementation is worth weeks, and the skill is measurable in minutes.
What do the levels of spec & requirements writing mean?
Four levels, each defined by observable behaviour rather than by years. This is the definition employers set their bar against, and the one every proof is scored to.
- L1Aware
Documents what should be built in a way a colleague can follow.
Evidence: A written feature description with requirements listed.
- L2Working
Includes acceptance criteria and states scope boundaries, so the team knows when it is done.
Evidence: A spec with acceptance criteria and a scope section.
- L3Independent
Resolves edge cases and failure states up front, states explicit non-goals, and writes so implementation proceeds without clarification.
Evidence: A spec with an edge-case table and a non-goals section, implemented without rework.
- L4Leading
Sets the specification standard for an organisation and improves how a whole team resolves ambiguity.
Evidence: A spec template or standard adopted across teams.
| Level | Label | People proven here |
|---|---|---|
| L1 | Aware | 0 |
| L2 | Working | 1 |
| L3 | Independent | 1 |
| L4 | Leading | 0 |
How is spec & requirements writing assessed?
Candidates rewrite a deliberately vague feature request into an actionable spec. The rubric weights edge cases, explicit non-goals, and testable acceptance criteria — the three things that separate a real spec from a wish.
Which roles require spec & requirements writing?
| Role | Level required | Status |
|---|---|---|
| AI Product Manager | L3 Independent | Required |
| Product Manager | L3 Independent | Required |
| Founding Engineer | L2 Working | Nice to have |
How do you prove spec & requirements writing?
Spec & Requirements Writing: questions people ask
- Does the format matter?
- No. The rubric ignores template and formatting entirely. It scores whether edge cases are handled, whether non-goals are explicit, and whether acceptance criteria are testable.
- I'm an engineer who writes specs. Does that count?
- Yes, and engineers frequently outscore PMs here because they have been on the receiving end of ambiguity. Prove the skill and it appears on your profile regardless of your title.
- How long is the spec-writing challenge?
- 60 minutes. You rewrite one vague request; you are not asked to produce a document suite.