London · Hybrid, 2 days/week · £85,000–£110,000 +
equity
THE DECISION BRIEF
Your next calls, in order.
Worked example
02
Call firstClear reasons to start a conversation
↳01
Clarify firstOne material question before proceeding
—02
Hold for this briefKeep visible. Revisit if evidence changes.
OUR READ OF THIS POOL
Start with Katie. Keep Marcus close.
Katie describes the closest match to Helio’s product. Marcus
brings strong production depth from a different domain. With
Leila, establish the ownership gap before deciding.
THE DETAIL THAT CHANGES THE DECISION
“Has worked with LLMs” and “can own this product in
production” are different requirements.
That’s the distinction this shortlist makes.
The call list
Every candidate stays visible. Every recommendation has a
reason.
5 SAMPLE CVs
CANDIDATE
STRONGEST RELEVANT SIGNAL
THE QUESTION STILL OPEN
NEXT STEP
↺
THE SECOND LOOK
Leila’s title isn’t the whole story.
Her RAG and evaluation work is directly relevant. The open
question is how much production engineering she can own
independently.
⇄
THE BRIEF TRADE-OFF
What if platform support exists?
Leila becomes more worth exploring if Helio can support
deployment and on-call. That changes the role’s ownership
requirement; it doesn’t erase the gap.
ⓘ
Still to confirm with every candidate
Current availability, compensation expectations and agreement
to the working pattern. The CVs do not establish these.
FROM RECOMMENDATION TO SOURCE
Follow the evidence.
SELECT A CANDIDATE TO EXPLORE
THE TRADE-OFF, SIDE BY SIDE
Two candidates. One clearer decision.
Compare the evidence against the same role. Labels describe what
the CV supports, not a prediction of performance.
⇄
ⓘ
What a comparison cannot tell you
Neither a score nor a CV verifies performance. Use the
first-call probes to investigate the differences before making
a decision.
NO MYSTERY NUMBER
Know what you’re looking at.
01
Evidence in the supplied CV
A concrete project, responsibility or result relevant to the
brief. Click a source to inspect the exact wording. A CV
statement is still a candidate claim.
02
Gaps made explicit
Missing information becomes a question. A prototype is
labelled as a prototype; collaborative delivery is not
silently treated as solo ownership.
03
A judgment you can challenge
Recommendations relate to this role and this evidence. If the
brief changes or new evidence arrives, revisit the judgment.
No candidate is automatically rejected.
WHAT THIS ROLE ACTUALLY ASKS FOR
Production ownership is the bar.
Helio’s brief asks for 3+ years on production ML or AI, hands-on
LLM work, Python/API engineering, vector databases, AWS and
end-to-end ownership. NL-to-SQL and analytics experience are
useful advantages, not mandatory substitutes for the essential
criteria.
About this example
These are fictional CVs and a fictional role already used in
Superceptron’s demo. The report is a curated worked example, not
a live AI run, a claim of verified employment, or evidence of an
actual human-review event. It shows the structure and level of
reasoning a delivered shortlist should contain.
No inference is made about honesty, AI authorship or suitability
from writing style, name, photograph, education prestige or
personal characteristics. Recommendations here focus on the
job-related evidence in the supplied documents.