Chapter 03. Candidate Portrait and Search Hypotheses
How to Use This Chapter
Open this chapter after the brief, when you already understand what work the person must do. Do
not start with job titles: first describe the environment, tasks, public traces, and transferable
experience traits.
Remember in One Phrase
The candidate portrait is not an ideal-person avatar — it is a set of observable traits you can use
to build and test search hypotheses.
| If Your Task Is | Go to Section | What You Get |
|---|---|---|
| Translate requirements into profile facts | Observable profile traits | A checklist of signals to verify |
| Find adjacent talent pools | Obvious and adjacent profiles | A broader market without losing relevance |
| Formulate search hypotheses | Hypothesis builder | Testable search routes |
| Build a one-page portrait | Candidate portrait canvas | A working document for the team |
Quick Chapter Map
1. Describe the work being done.
2. Find the observable traits of that work.
3. Lay out obvious and adjacent profiles.
4. Formulate 3–5 hypotheses to test.
Minimal Start
In 30–40 minutes, take the approved brief and fill in the portrait canvas across five rows:
work, environment, tools, job titles, and public traces. Then write 3 hypotheses and test each
against 10 profiles. For role examples, see Appendix E.
Principle
The candidate portrait is only useful when it helps you search, evaluate, and write the first
message. It should describe the work, environment, traits, and likely motivation — not an
invented "perfect person portrait."
Example
A weak portrait for Data Engineer: "5+ years, Python, SQL, cloud, communication." A useful portrait:
"Owned batch or streaming pipelines, worked with complex product or revenue data, understands
orchestration and data quality, collaborates with analysts and product teams; may be called
Analytics Engineer, Data Platform Engineer, BI Engineer, or Data Infrastructure Engineer."
Observable Traits
Launched projects.
Tools used.
Domains and task types.
Company environments where the person has worked.
Public work: repositories, portfolios, talks, articles, case studies.
Communities and events.
Career trajectory and growth in scope of responsibility.
Product, client, revenue, or operational context.
Obvious and Adjacent Profiles
Type What It Looks Like Risk When to Use
Obvious Exact job title, exact Overheated and expensive High-confidence target
industry, exact stack
Adjacent Similar work under a Needs calibration Smart market expansion
different title or in a
different domain
Query and Hypothesis
Search query: "Product Manager" AND onboarding AND SaaS
Hypothesis: "Product managers who owned onboarding or activation in B2B SaaS with product-led
growth or a hybrid sales model may be better suited to solve the activation task. I will search
through job title variants, keywords onboarding/activation/self-serve/PLG/lifecycle, and
companies with a similar model."
Hypothesis Builder
People who did [work] in [environment] may be a fit because [reason].
I will find them through [job titles], [companies], [keywords], [communities], [public traces].
I will test the hypothesis against [number] profiles and measure [share of relevant profiles].
Example Hypotheses for Senior Backend Engineer
1. Engineers from payments, fintech, marketplaces, booking, or e-commerce are a fit because of
transaction scale and reliability requirements.
2. Platform engineers from companies with a large event stream are a fit if they have owned
distributed systems, observability, and incident resolution.
3. Backend engineers who write or speak about scaling, queues, databases, and reliability may
be strong passive candidates.
4. Adjacent industries with strict availability or audit requirements can provide transferable
experience.
5. Former tech leads who returned to an individual contributor role can cover a senior level
without people management.
If you need support across different role types, review the cross-cutting cases in Appendix E:
the same method is shown for Backend Engineer and BDM.
Candidate Portrait Canvas
Block Questions
Work Performed What has the person built, sold, analysed, designed, or
operationally run?
Environment What environment trained them?
Tools Which tools are mandatory, adjacent, or optional?
Signals Which traits in a profile matter?
Job Titles What might this be called?
| Block | Questions |
|---|---|
| Communities | Where do these people speak, write, or participate? |
| Motivation | Why might they be interested in a move? |
| Risk | What looks relevant but does not fit? |
| First-Message Angle | Which specific message angle to use? |
Key Takeaways / Where to Go Next
Take away a set of hypotheses, not one "correct" query. If the hypotheses are ready, move to
Chapter 4 to verify where the market actually has the right people and which constraints to
present to the client.
