Choose a fictional example or sketch your own brief. Everything stays in this tab. No live research, model calls or outreach.
Try your own brief +
See how to frame the search. This does not generate candidates or reuse the example profiles as matches.
SCOUTExample company / Engineering / early team
Who could do this exceptionally well?
Start with what the role demands. Research the market deeply. Hire exceptional folks, whether or not they’re looking.
Fictional worked example · Illustrative3 profiles · fictional, not candidatesNo outreach sent
The role brief is available below. Enable JavaScript to explore the prepared research and try the review controls.
The mandate / Example company
Founding Engineer
Take an AI workflow from a promising prototype to a dependable product that customers use every day.
Location to agreeEngineering / early teamBrief v1
The work behind the title
Own the path from customer problem to running software: integrations, evaluation, observability and the judgment to keep the system simple. This is hands-on product engineering, not a mandate to build a large team.
Invented role, companies and people. No real hiring mandate.
01
Own a problem end to end
Follow one example from the user need through implementation, deployment and support.
02
Make failure legible
Explain how failures were detected, reproduced and prevented without hiding them behind a model.
03
Choose the small system
Show a time a simpler design beat a fashionable or more elaborate one.
04
Learn with customers
Describe a product assumption that changed after watching someone use the work.
Start with the mandate. Now find where the relevant work is happening.
2 starting pools
Follow the work.
These invented research pools illustrate where to look and which evidence to follow. No live search runs here.
Illustrative pool / product ownership
Small product teams
Small teams can expose broad ownership. Team size alone does not prove it.
Start with the work
Tools people depend on
→
Follow the evidence
The people who built and maintained them
Example integration diary · no external sourceArtifact → maintainer → collaborators
A fictional account of replacing a fragile prototype with a monitored customer workflow.
What to investigate
Trace authorship and maintenance responsibility; look beyond the person presenting the work.
Different remits. Different evidence. A qualified shortlist still needs direct validation.
Evidence before assumptions
Make your own call.
Investigate the person behind the profile. Change a priority, challenge the evidence and decide what to learn next.
3 of 3 profiles
P0 Investigate firstP1 Promising, with a questionP2 Adjacent or feasibility gapResearch priorities, not hiring verdicts.
Product builder · Initial P0
Avery Chen
Fictional profile · no real employer Location and willingness to move are unknown
The sample shows broad ownership from customer discovery through operations. Worth investigating whether that depth survives a more demanding system.
The question that changes the case
Did they own the hard parts or mainly assemble existing components?
Ask for one specific example, their personal contribution and the tradeoffs. Seek disconfirming evidence.
Read the evidence +
All evidence below is invented for this demonstration. It is not a claim about a real person.
Illustrative work sample
Invented sample: built a document-review workflow, added a failure queue and changed the interface after five customer observation sessions.
View source · no external source
What we do not know
Interest, availability, compensation and references are unknown. A public artifact would not establish these.
View source · no external source
What could make this the wrong person?
A single successful small tool may not transfer to a larger production system.
What would change the priority?
Direct evidence of ownership at the required scope would raise priority. A mismatch in the work or mutual interest would lower it.
Why this might be valuable to them
A hypothesis to ask about, not a motivation we know: more ownership over a difficult problem and the chance to work closely with its users.
A route to a useful conversation
No relationship is established. First check whether a colleague genuinely knows them; ask before requesting an introduction.
Next action
Validate the evidence, then decide whether there is a useful reason for a conversation. Nothing is sent by this demo.
Try an interview probe +
Walk me through something you shipped that people depended on. Which decisions were yours, and what happened after launch?
Work in Notion? There’s a surface for that, too.+
Optional workspace surface
Bring the review into your workspace.
A Notion surface can place the brief, research packets and a priority board alongside an embedded Scout view.
Scout runs independently here. You don’t need a Notion account, and changes in this demo don’t sync to any workspace.
Illustrative layout only. This does not display or connect to a private search.
N Scout / Example workspace •••
◎
Founding Engineer
Illustrative workspace. Not a live connection.
Scout · Embedded viewWho could do this exceptionally well?