ProductJudgment evaluation
Hiring for the job, not for the skill list
Two people can both pass your skills test and be completely different hires. The difference is judgment — the calls your brief leaves open. NorthAssay pulls those out of the job description, shows them to you, and builds the assessment around them.
Try it on a real postingThe problem
A skills score answers a question you already know the answer to
By the time someone reaches an assessment you have usually seen their portfolio, their history, and their proposal. "Can they write TypeScript" is rarely the open question. The open question is whether they will make good calls on your job — where the brief is thin, the constraints are real, and nobody is going to be watching them work.
The skills report
What the test measured
Knows TypeScript
Passed system design
Wrote idiomatic Go
Judgment on job trade-offs was never measured.
The open question
What the job actually asks
“Rewrite the retry engine, or instrument it for six months first?”
Reasoning is the signal
Both are defensible; the choice changes the outcome. A skills test cannot see this fork.
That question is also the one that has got harder, not easier. Work that is mostly execution is being compressed: on Upwork’s own 2026 data, execution-heavy contracts are down 13% in earnings per contract while complex, judgment-led work is up 45%. The part of a job that survives is the part a test of recall never touched.
Execution-heavy work
-13%
Earnings per contract on Upwork, 2026
Judgment-led work
+45%
Earnings per contract on Upwork, 2026
The thing nobody fixes
Most bad remote hires are not people who could not do the work. They are people who did the wrong work well, because the brief never said which trade-offs mattered — and neither did the assessment.
What an open decision is
An open decision is a real fork in your work where two competent people would reasonably choose differently, and where the choice changes the outcome. Not a gap in the brief to be filled in — a genuine choice the job leaves to whoever takes it.
This is the oldest well-evidenced idea in selection research wearing new clothes. Situational judgement tests — put a person inside a realistic dilemma and score the call they make — have been validated for decades, with predictive validity in the r = .32 to .52 range. What has never been practical is writing one per job. That is the part this automates.
A fork in the job
Open decision
Reasoning is the signal
“Rewrite the retry engine, or instrument it first?”
Skill
One answer; the CV screen already checked it
“Do they know Go?”
Clarification
Needed to proceed, not judged
“What database are you using?”
How it works
How it works, in four steps
- 1
1. It reads your job description and pulls out the forks
Alongside the competency model, NorthAssay extracts what the work actually is — responsibilities, deliverables, constraints, business context — and then the judgment calls the brief leaves open. For each one it writes what a weak answer looks like and what a strong one looks like, concretely enough that you could tell two candidates apart by reading them.
Extracted forks
Retry strategyOwnership modelObservability - 2
2. It tells you where each one came from
Every decision is graded by provenance: in the brief (your posting raises it), inferred (standard for this role and domain, but you did not say it), or speculative (a guess worth confirming or cutting). Thin briefs produce more inferences, which is exactly when you want to know that. Provenance is one of those three words, never a confidence percentage you have to interpret.
Provenance
In the briefInferredSpeculative - 3
3. You confirm or edit them before anything is built
The run stops and shows you the list, least-trustworthy first. You rewrite anything that is wrong in your own words, and confirm. Nothing is generated until you do — because these become the things real candidates are measured on, and you know your job better than any model reading a posting about it.
Confirmation gate
Review open decisionsEdit or remove any that are wrongConfirm before building - 4
4. The assessment is built around them
The written and multiple-choice stages put candidates inside the decisions rather than asking about them in the abstract. Distractors are the weak approaches, and each one names why it fails here. Then the live interview probes the same calls in conversation, following up when an answer is shallow — and the criteria it is scored against come from your decisions, so the score is about them rather than about a generic rubric.
Assessment built around decisions
What you get back
What you get back
Evidence per requirement, in your own words. For each decision: what the candidate showed, the verbatim quote it rests on, and — this is the part most tools skip — what was not established, kept visually distinct from what they got wrong.
"We never asked them about this" and "they answered this badly" are opposite facts, and most reports render both as an empty row. Collapsing them reports a gap in the assessment as a deficiency in a person, on the screen where you decide whether to hire them. They are kept apart deliberately.
The score is not the answer
Assessments are scored, and the dossier shows a headline mean. What it does not do is roll this evidence into that number: the requirement findings do not sum, and nothing here is weighted into a single figure that says how well someone matches a job. A composite is the thing you would screen on without reading anything underneath it, and the reading is where the value is.
Evidence by requirement
Established
Candidate explained the retry trade-off with concrete failure modes.
Not established
We did not ask about write-load failure modes under pressure.
Got wrong
Chose to instrument without defining what “good” telemetry looks like.
Limits
What this does not do
It does not know your business
It does not know your business. A model reading your posting can infer a great deal about a role and nothing at all about the politics, the history, or the customer who will not be named in writing. That is why the decisions are graded and why you confirm them — the screen exists to be argued with.
It does not replace judgment about judgment
It does not replace judgment about judgment. A strong candidate can reason well and still be wrong for you, and a score here is evidence rather than a verdict. You can override any score, and we ask you to say why.
It does not work miracles on a thin brief
It also does not work miracles on a two-line brief. It will still find decisions — inferring from the role and the domain is the point, because a thin brief is exactly the case where a client cannot specify their own work — but it will mark them as inferred, and you should read those hardest.
More in Product
See what it finds in your job description
Paste a real posting and look at the decisions it pulls out. If they are the ones you would have named yourself, that is the whole product working. If they are not, rewrite them — it takes a minute and it is the fastest way to judge this.
Try it on a real posting