WanderingTechScoutOS blueprint

Candidate scoring blueprint

Four scores, one verdict, and the reason behind each.

Enter a candidate and a target field, and get a fit score with the reasoning behind it. A personal project, inspired by production talent-intelligence work and built from scratch with its own logic and entirely synthetic data.

  1. 01Rubric
  2. 02Scoring
  3. 03Screens
  4. 04Pipeline
  5. 05Scope
Type
Concept demo, runs in the browser
Stack
Vanilla JavaScript, no backend
Rubric
4 dimensions, scored out of 100
Verdicts
Strong Fit, Consider, Not Yet
Sample pipeline
12 candidates, fabricated
Prepared by
Jam Susana
StartStepDecisionEnd

V1 · Oct 2026

Demo

Score a candidate

Type any name and pick a domain.

01

The rubric

Four things every candidate is scored on, and what each band means.

Figure 01 · Rubric4 dimensions
DimensionRange
Technical Depth45 to 98
Public Profile Strength45 to 98
Leadership Signal45 to 98
Domain Relevance45 to 98

Reasons shown for each band

BandScoreReasons it can show
High78 or moreStrong, consistent signal across public sources.
Well above the threshold for this dimension.
Clear evidence of depth in this area.
Mid60 to 77Moderate signal — present but not standout.
Meets baseline expectations for this dimension.
Some evidence, could be stronger with more data.
Lowbelow 60Limited public signal for this dimension.
Below the typical threshold — worth a closer look.
Sparse evidence available for this criterion.
02

How a score is made

From the button press to the verdict.

Figure 02 · Scoring flow13 steps

Swipe sideways to see the whole flowchart

Scoring flow flowchartYESNOYESNOYESNO
TriggerRun Scoring pressedA candidate name and a target domain
Name entered?
EndNothing runsFocus returns to the name field
StepShort loading sequenceParsing input, running the sample rubric, computing the fit score
DataSeed from name and domainThe name is lowercased and trimmed, joined to the domain and hashed
StepScore four dimensionsEach from a fixed formula, between 45 and 98
StepPick a reason for eachHigh 78 or more, mid 60 to 77, low below 60
StepAverage into the fit scoreThe mean of the four scores, rounded
78 or more?
EndStrong FitShown in green
60 or more?
EndConsiderShown in amber
EndNot YetShown in red
Read this flow as a list
  1. Run Scoring pressed. A candidate name and a target domain
  2. Name entered?. The name is required
  3. Short loading sequence. Parsing input, running the sample rubric, computing the fit score
  4. Nothing runs. Focus returns to the name field
  5. Seed from name and domain. The name is lowercased and trimmed, joined to the domain and hashed
  6. Score four dimensions. Each from a fixed formula, between 45 and 98
  7. Pick a reason for each. High 78 or more, mid 60 to 77, low below 60
  8. Average into the fit score. The mean of the four scores, rounded
  9. 78 or more?. Strong Fit
  10. Strong Fit. Shown in green
  11. 60 or more?. Consider
  12. Consider. Shown in amber
  13. Not Yet. Shown in red
03

The screens

Three views, one top bar.

Figure 03 · Screen guide3 screens
ScreenShowsYou can
DashboardCandidates scored, average fit score, the four rubric dimensions and the five latest scoresJump straight to scoring
Score a CandidateA form with candidate name, target domain (5 choices) and an optional LinkedIn URLRun scoring and read the four scores, the overall fit score and the verdict
PipelineA table of sample candidates with domain, score and statusFilter by domain or status, sort by score
04

The sample pipeline

12 made-up candidates, scored by the same formula.

Figure 04 · Sample pipeline12 candidates
CandidateDomainScoreStatus
Jordan BlakeDeveloper Tools82Strong Fit
Taylor NovakFintech80Strong Fit
Priya NairFintech76Consider
Morgan DiazAI / Machine Learning74Consider
Drew HalvorsenCloud Infrastructure71Consider
Alex RiveraAI / Machine Learning70Consider
Robin CastellanoAI / Machine Learning66Consider
Jamie KowalskiDesign / Product65Consider
Casey LindqvistCloud Infrastructure63Consider
Avery LindgrenFintech63Consider
Reese AnderssonDeveloper Tools62Consider
Sam OkaforDesign / Product55Not Yet
05

What is real and what is not

The line between the idea and the sample.

Figure 05 · ScopeDemo
PartIn this demo
Candidate profilesNone are read, fetched or stored
Scores and reasonsGenerated from the name and domain by a sample formula
LinkedIn URL fieldOptional, and never fetched
Names in the pipelineMade up
Network callsNone

Want something like this?

Tell me about the process you want off your plate. The brief takes about three minutes, and the project is priced before I start.

Start a Brief

Open the full demo →

ScoutOS is a personal, independently built demo. It uses synthetic data only, and real records and anything confidential are left out.