A candidate opportunity brief should explain what the company is trying to accomplish, why this role matters, and what joining would feel like in practice. It helps someone decide whether to explore the job before either side invests in a long process.
A company pitch and a job description each cover part of that question. The opportunity brief connects them. It should make the work understandable without promising outcomes the company cannot guarantee.
Build the brief around the decision to join
Use this outline in a page or short email:
- Customer problem: Who needs the product, and what difficulty does it address?
- Current starting point: What already exists, and what remains uncertain?
- Role contribution: What would this person own and change?
- Working relationship: Who sets priorities, and who provides support?
- Practical conditions: Approved compensation information, location, travel, and working arrangements.
- Hiring process: What conversations come next and what each will assess?
- Open questions: What should both sides explore before deciding?
Use approved information. A private roadmap or an unannounced customer does not become public simply because it would strengthen the pitch.
Describe the opportunity without inflating it
A fictional engineering brief might say: “The product works for an initial workflow. This role will make customer setup repeatable and help choose which requests belong in the core product.”
That tells a candidate more about ownership than “join a rocket ship.” It also creates useful questions: Who currently handles setup? How are product priorities decided? What support is available?
State limitations with the same clarity. If there is no engineering manager yet, explain who will provide feedback. If leadership scope may grow, separate the current responsibility from the possible future.
Check whether the story survives a handoff
Ask the recruiter or interviewer to explain the opportunity back without reading the brief. Listen for missing context and accidental promises.
If different interviewers describe different roles, resolve the disagreement internally. A candidate should not have to reconcile conflicting versions of the company's plans.
Keep a dated approved version and identify the owner. When responsibilities or work arrangements change, update the brief and tell candidates already in process.
Use candidate questions as a diagnostic
Repeated questions can reveal omissions. If candidates consistently ask whether the job is mostly implementation or product work, add a direct explanation. If they ask about management responsibility, clarify the actual team structure.
Do not interpret every question as an objection to overcome. Some questions reveal a legitimate mismatch. A clear brief gives both parties permission to recognize it earlier.
Pair this document with the candidate motivation interview. For information boundaries, use the confidential recruiter briefing guide.