// the engine

A standard for engineering ability — and the network built on it.

Shortlist is a verification engine: a senior-reviewed bar for what good means in a domain, and the regional pool that bar produces. It defines the standard, holds engineers to it, and connects the verified pool to the work that needs it.

a senior-reviewed standard · a verified pool · a network that runs on it
// why this exists

AI now produces code, completes take-homes, and clones writing style. Resumes are noisier than they have been in twenty years. Phone screens never caught identity in the first place. Without a standard, senior is a self-reported word.

The engine exists because the signal under engineering hiring broke and nothing replaced it. A senior in the field, on the record, looking at real work with the candidate in the room — that's the missing rung. The standard is the way it goes back in.

// what stays fixed

Four properties the engine holds constant.

One bar, held across the network.

The standard doesn't relax for an internal hire or tighten for an external one. The same bar applies whether the engineer ends up on an Orion team, a partner company, or a recruiter's pool.

Comparable evidence per engineer.

Every verified profile carries the same kind of receipt — assessment score, lab artifact, SME endorsement on record, identity confirmation. Profiles read side by side without disclaimers.

Calibrated per domain, not generic.

What good means in cloud infrastructure is not what good means in applied ML. The bar is set by a senior in each domain, not borrowed from a generic interview rubric. A domain is added when a senior in it can run the standard.

AI-assisted, human-anchored.

AI calibrates the bar, scores at scale, and surfaces signal that's harder to see by hand. A senior in the field signs off on whether the engineer cleared it. No model decides alone.

// the standard

Clearing the standard takes about two and a half hours of real work: a domain assessment, a take-home lab, and a live session with a senior engineer in the field. Identity is re-verified at placement, so the engineer verified is the engineer who starts.

The live session carries the weight — a lab shows what someone can produce; a senior in the room shows whether they understand it.

The standard is the product. Everything else runs on top of it.

// what it tests

A senior isn't checking whether an answer can be produced — tools produce answers. They're checking whether the engineer can reason about their own work: why this design, where it broke, what they'd change.

AI assists where signal is harder to see by hand: calibrating the bar against a domain, scoring at scale, surfacing patterns across attempts. A senior signs off on whether the engineer cleared the bar. No model decides alone.

The standard proves a real engineer did real work and could defend it to someone senior. It doesn't claim more than that.

// how it works
  1. 01
    Set the standard

    A senior-reviewed bar per domain. What good means in cloud infrastructure differs from what good means in applied ML. The standard is calibrated by seniors in the field — not borrowed from a generic rubric.

  2. 02
    Measure

    A system of signal: assessment tooling, hands-on labs, live sessions with senior engineers in the field, identity checks. AI assists in calibration and scoring; a human signs off. No model decides alone.

  3. 03
    Profile

    Every verified engineer carries a profile — domain scores, lab artifacts, SME endorsement, identity confirmation. Built from results, not from self-reported claims.

  4. 04
    Connect

    The profile connects to where the work is — Orion's own teams, partner companies, recruiter rails. The engine routes the match; the human keeps the relationship.

  5. 05
    Re-verify at placement

    When a match converts, identity is re-confirmed. The engineer verified is the engineer who starts.

// see it run

What the engine looks like from inside.

End-to-end across candidate onboarding, evaluation, partner matching, and placement — all in the admin console.

~/shortlist · live engine tail auto · 1:00 · looping
14:32:08[engine]new candidate intake · m. verma
14:32:09[engine]domain: cloud infra · senior+ · calibrating bar
14:32:42[ai]assessment scored 94 · cleared bar
14:33:01[lab]artifact submitted · terraform-multi-region.zip
14:33:11[sme]r. chen endorsed lab (3m read · "ship-ready")
14:33:14[engine]profile assembled · scores · lab · sme · identity ✓
14:33:22[engine]match request · senior cloud engineer · NoVa
14:33:23[ai]routing m. verma → 96 fit (top of pool)
14:33:24[engine]connecting profile to acme partner
14:33:38[acme]partner accepted match · interview scheduled
14:33:40[engine]placement scheduled · re-verify 2026-06-15
14:33:41[ok]verified · engineer-who-starts = engineer-who-verified
Partner · admin console
A pipeline of engineers already vetted by a senior in the field.
Ranked candidates, match scores, SME endorsements, live pipeline analytics.
Pipeline Analytics Roles Reports 3 open roles
Active Matches
47+12
Verified
38
81%
Avg Score
94%
Top Candidates
Sr. Cloud Eng.
96
V
ML Engineer
91
V
DevOps Lead
87
R
Full Stack Dev
84
V
Data Engineer
79
N
Match Activity · 4 Weeks
Hiring Funnel
142 sourced
47 matched
18 interviewing
6 hired
Weekly pipeline volume
Candidate · profile console
A profile built from results, signed off by a senior who saw the work.
Verification progress, skill assessments, learning activity, employer interest.
Profile Skills Matches Labs VERIFIED
Profile Score
92%
Labs Passed
7
7/8
Matches
12+3
Verification Progress 4 of 4 Complete
ProfileAssessmentLabSME Review
Skill Assessments
Cloud Arch.
95
IaC / CDK
91
Sys Design
88
Containers
85
CI/CD
82
Learning Activity · 4 Weeks
Employer Interest
12 matched
7 viewed
4 interviews
Profile views · 30 days

Recorded in the actual admin console. End-to-end candidate and partner onboarding UAT-passed; AI matching live.

// the network

Where the verified pool is used.

The engine routes verified engineers to the work that matches; the human relationship stays with the partner or recruiter.

route 01 · internal

Internal teams

The teams building Orion's own platforms draw from the pool.

route 02 · partners

Partner companies

Organizations Orion works with draw verified engineers through a relationship, not a listings page.

route 03 · recruiters

Recruiter rails

Recruiters and talent teams run on the verification as infrastructure — the engine supplies the proof; the recruiter keeps the relationship.

// how the standard is held
// what it covers

Senior through lead and engineering management — the standard is about depth a title can't show, so there are no junior tiers. A domain is added when a senior in it can run the standard.

cloud & infrastructure backend AI/ML devops data full-stack frontend security eng leadership
// the mission

The aim isn't throughput; it's the floor. Starting in Northern Virginia, the engine is building a verified pool deep enough to shift what incoming tech talent means in the region — a quality bar that compounds as it grows. The pool is built before the demand: verify the engineers, hold the standard, and let the work find the proof.

// the work

Where verified engineers are being placed today.

Live roles from employers using the engine.

Loading roles…

→ submit a profile → post a role

// what this is not
a job board a staffing agency a résumé reseller a data broker

It does one thing: make verified mean something, and connect what it means to the work that needs it.