Skip to main content
For hiring teams

Scope the role. Not the résumé.

State the evidence level the role actually requires across five capability layers. You get a weighted screening scorecard, the evidence probes to interview on, and the published dossiers documenting the market — the same benchmark candidates are measured against in our diagnostic.

A weighted scorecard

Five capability layers, each with the share of the decision it actually carries.

Interview evidence

Observable artefacts to ask for, generated from the decisive layers of your bar.

Sourced market evidence

Published dossiers with citations, so the bar is argued rather than asserted.

1

Role family

2

Role level

3

Calibrate the bar

The default is the published benchmark for this family, calibrated to the role level. Move only what your context genuinely requires — every deviation is flagged.

Quantitative foundations

Reading numbers correctly before acting on them.

19% of scorecard

Technical craft

The tools of the trade, used on real artefacts.

Decisive layer34% of scorecard

Systems & sovereignty context

Knowing which constraint actually governs the outcome.

18% of scorecard

Execution discipline

Turning intent into a delivered, verifiable result.

20% of scorecard

Judgement & influence

Being understood, and trusted, by decision-makers.

9% of scorecard
4

Evidence to require at interview

Generated from the decisive layers of your benchmark. Each statement is an observable artefact, not an adjective.

  1. 1. Technical craft

    required 4/4
    • I ship work in the primary tool of my target role (code, CAD, model, spec) without a template.
    • I use AI systems as instrumented tools — I check their output against a source of truth.
    • I can explain the failure modes of the technology I work with, not just its features.
  2. 2. Execution discipline

    required 3/4
    • I have owned a deliverable end to end against a hard deadline, including the trade-offs.
    • I instrument my own work — I can show what I measured to know it worked.
    • When a plan breaks, I re-sequence it rather than escalate without options.
  3. 3. Quantitative foundations

    required 3/4
    • I can rebuild a company’s cost or capacity figure from primary filings rather than quoting a headline.
    • I size an unfamiliar market or plant with explicit assumptions I can defend line by line.
    • I distinguish correlation, base rates and survivorship when a dataset supports a decision.
6

Send the brief

Reference sent: engineering.mid.34332

We use these details only to answer your request. No advertising tracking.