Appendix D. Template Library
1. Search Brief Template
Field Complete
Role
Business problem
Client / hiring manager
Mandatory signs
Desirable signals
Exclusions
Job title alternatives
Donor companies
Adjacent companies
Sources and search routes
First-message angles
Initial call questions
Feedback SLA
Example:
Field Example
Role Senior Backend Engineer
Business problem Strengthen the team responsible for payment circuit reliability
Mandatory signs High-load backend experience, incidents, observability, responsibility for production services
Donor companies Fintech infrastructure, billing, marketplace core teams
First-message angles Critical circuit reliability, transaction scale, deep engineering ownership
Feedback SLA Calibration profiles – 24 hours, interviews – 24 hours
2. Client Brief Script
What business problem does this hire solve?
What will the person own?
What outcomes will show success?
Which 3 requirements are truly mandatory?
How is that visible in a profile?
Which types of experience have worked or not worked before?
What compromises are possible?
What constraints are fixed?
How quickly will feedback come?
3. Requirements Classification Matrix
Requirement Mandatory Desirable Signal Noise Observable Sign
4. Candidate Portrait Canvas
Block Notes
Work performed
Environment
Tools
Projects
Job titles
Communities
Public traces
Motivation
Risks
First-message angle
5. Search Hypothesis Builder
People who did [work] in [environment] may be a fit because [reason].
I will find them via [job titles], [companies], [keywords], [communities], [public traces].
I will verify on [number] profiles and measure [proportion of relevant profiles].
6. Market Map Template
Pool Why Relevant Source Job Titles Keywords Risk Priority
Example:
Pool Why Relevant Source Job Titles Keywords Risk Priority
Fintech Similar payment LinkedIn, Backend reliability, May lack direct B2B High infrastructure or references, Engineer, payments, SaaS context transactional engineering blogs Platform Kafka, B2B SaaS- circuit PostgreSQL Engineer
7. Donor Company Matrix
Company Why Relevant Teams Job Titles Signals Priority Notes
8. Boolean Query Testing Log
Date Source Query Viewed Relevant Noise Next Change
Example:
Date Source Query Viewed Relevant Noise Next Change
14 Jun LinkedIn "Backend 20 6 Much noise. Add payment platform OR AND support Engineer" and reliability, analyst- remove profiles
(payments OR billing) AND Kafka support
9. LinkedIn Profile Assessment Map
Candidate Mandatory Environment Level Transferability Message Risk Decision
Signs Angle
10. First Message Formula
Hello [name].
I noticed [specific fact from the profile].
We are looking for someone for [role/problem] where [link to candidate's experience] matters.
This could be of interest if [value from the candidate's perspective] is important to you.
Would it be appropriate to [simple next step]? If not, that is fine.
Example:
Hello Anna.
I noticed your experience with backend services for payment flows and production system observability.
We are looking for a senior engineer to tackle transactional circuit reliability, where incidents, Kafka and PostgreSQL matter.
I can send a short brief if this area of responsibility is of interest. If now is not the right time, that is fine.
11. Follow-Up Sequence
Follow-up 1:
Just circling back to the message above. I reached out because of [specific fact]. Shall I send details?
Follow-up 2:
Closing this from my side. If [topic] becomes relevant later, I would be happy to continue the conversation.
12. Candidate Relevance Assessment Map
Dimension Score 1–3 Facts Uncertainty
Mandatory work
Environment
Scale/level
Transferable skills
Motivation
Risk
Example:
Dimension Score 1–3 Facts Uncertainty
Mandatory work 3 Profile shows responsibility for Need to clarify scale payment backend services and of workload incident response
Environment 2 Fintech infrastructure, but not Check domain B2B SaaS transferability
Scale/level 2 Senior role and multi-team Need calibration with projects tech lead
Motivation 1 No obvious job-search signals Check in first in profile contact
13. Weekly Update for the Client
Role:
Week:
Hypotheses tested:
Profiles reviewed:
Candidates contacted:
Responses:
Interested responses:
Qualified initial calls:
Interviews:
Key rejection reasons:
What we learned about the market:
Decision needed:
Next plan:
Example:
Role: Senior Backend Engineer
Week: 14–18 Jun
Hypotheses tested: fintech infrastructure, billing platforms, marketplace core teams
Profiles reviewed: 80
Candidates contacted: 18
Responses: 5
Interested responses: 2
Qualified initial calls: 1
Interviews: 0
Key rejection reasons: compensation expectations, limited direct production ownership
What we learned about the market: billing platforms yield more relevance than marketplace core teams
Decision needed: agree to expand to platform engineers from fintech infrastructure
Next plan: review 30 profiles in the new pool and rewrite the message angle for reliability
14. Funnel Metrics Dashboard
Role Viewed Saved Contacted Responses Interested Qualified Interviews Offers Key Blocker
15. Sourcer-to-Recruiter Handoff Checklist
Candidate link.
Source and hypothesis.
Facts on mandatory requirements.
First contact history.
Candidate motivation.
Compensation and location notes.
Initial call notes.
Open questions.
Recommended next step.
16. CRM / ATS Cleanliness Checklist
Candidate is linked to the correct role.
Owner is assigned.
Source is recorded.
Stage is up to date.
Notes are factual.
Contact history is visible.
Rejection reason is specific.
Next action has a deadline.
Opt-out from communication is respected.
Duplicate check is complete.
17. 30-Minute Sourcing Sprint Plan
0–5 minutes: review the brief and choose one hypothesis.
5–10 minutes: build or refine the query.
10–22 minutes: review and assess profiles.
22–27 minutes: send or prepare messages for the best candidates.
27–30 minutes: record metrics and the next iteration.
