Sample brief

This is what lands in your vault.

Not a transcript. A structured, quote-backed read on one candidate — the same shape every time, ready to hand to a hiring manager. Here is a real one.

How to read it

Five things to notice.

1
Candidate summary
A plain-language read of who they are and what they’ve done.
2
Structured topic coverage
Each requirement you set — marked covered, partially covered, or not mentioned.
3
Evidence quotes
The candidate’s own words behind every line. No paraphrase.
4
Recruiter verdict
Yes, partial, or no — your call in The Read. Scout never decides.
5
Hiring-manager-ready
One consistent shape — paste into any ATS or hand off as a PDF.
scout.vantumworks.io / screenings / sample

Screening summary

Software engineer with 8 years of experience. Has led a 6-person payments team at a fintech for the past 4 years; the team owns the routing layer for the transaction-processing platform. Resume lists Java and Python as production languages. The JD references Go as the primary language; the candidate stated they have written Go for side projects but not in production.

Candidate profile

Current role
Engineering lead, Payments — fintech (4 yrs)
Experience
8 years total in backend engineering
Team
Leads 6 engineers; owns the routing layer
Production languages
Java, Python (Go: side projects only)
Logistics (stated)
US-remote; four weeks’ notice
Comp target (stated)
$200–220k base

Topic coverage

Covered
5+ years distributed systems experience
“We were processing about 40 million transactions a day across three regions, and I owned the routing layer end to end.”
Partially covered
Experience with the payments domain
“Mostly card-present and ACH. Never touched cross-border or FX — that was a different team.”
Not mentioned
Go in production
Not raised on the call. Resume lists Go under side projects only.

The Read — your verdict

Your criteria
Scout found
Your call
5+ yrs distributed systems
“40M transactions a day across three regions; owned the routing layer end to end.”
Payments domain
“Card-present and ACH. Never touched cross-border — that was a different team.”
Go in production
Not mentioned on the call. Resume lists Go under side projects only.

Coverage is labelled covered, partially covered, or not mentioned — describing what was said. The Yes / Partial / No verdict is the recruiter’s. Scout never scores, ranks, or recommends.

One artifact

Same output, three ways in.

However the candidate was screened, the brief comes out in one consistent shape — so your hiring manager learns to read one thing, not three.

Recruiter-led

You run the call

A speakerphone or Zoom/Teams intake you conduct yourself produces the brief above.

Rosa

Rosa runs the call

An async conversation Rosa conducts on your behalf returns the same brief, against the same rubric.

Campaigns

A resume lands

Analyze a submitted resume and get the same coverage grid, described from the document’s own words.

Hand it off

Built to leave Scout.

Scout’s job ends at the brief. Save it to PDF for the hiring manager, or copy it as clean text that pastes into any ATS without reformatting — no integration required.

No lock-in. Your vault is exportable and deletable on your terms. Scout doesn’t need to live inside your ATS to be useful — it deliberately hands off and gets out of the way.

Get a brief like this on your next candidate.

Free for 30 days · 5 intake calls · no card.

Sample brief — Scout