Published April 6, 2026Updated September 7, 2026
Find the candidate pack example closest to the way you are hiring, copy the structure, and replace the sample content with the specifics of your role. This page is about execution. If you need the definition, evidence, and full framework first, read what a candidate information pack is.
What these examples are
The worked examples below are illustrative, not customer case studies. They use fictional role contexts to show the level of specificity a useful candidate pack can contain. The goal is to give you something concrete to adapt without pretending there is one universal pack for every search.
A useful candidate pack example does not just show you which headings to use. It shows how much context a candidate needs to decide whether the opportunity is worth pursuing.
Start with a live candidate pack example
Before reading the written examples, open the Role.so demo. It includes a complete candidate pack in both personalised and reusable form, so you can see how the information below works as an actual candidate-facing page rather than a PDF outline.
What the strongest candidate pack examples have in common
The content changes by hiring motion, but the best examples usually answer the same decision questions:
- what the person is being hired to accomplish
- why the role exists now rather than six months ago or six months from now
- who the person will work with and report to
- what compensation, location, and working arrangements actually look like
- what the interview process asks of the candidate
- which aspects of the role may not suit everyone
- what the candidate should do next if they are interested
The examples below deliberately vary the emphasis. An executive-search pack needs a stronger mandate and business context. An outbound pack needs a sharper reason to care. An inbound pack can be broader because the candidate has already chosen to investigate the role.
Candidate pack example #1: executive search — VP Sales
Scenario: a Series B B2B SaaS company has grown quickly through founder-led and mid-market sales. It is hiring a VP Sales to build a repeatable enterprise motion.
Illustrative opening:
The business has grown from roughly £4m to £11m ARR in two years. The next stage is not simply to add more sales capacity: it is to build a repeatable enterprise motion that can support the company’s next phase of growth without depending on the founders to close strategic deals.
| Section | Example content |
|---|---|
| Mandate | Build the enterprise sales motion, improve forecasting discipline, hire the next layer of sales leadership, and reduce founder dependency in strategic deals. |
| What success looks like | Within 90 days: diagnose the funnel and team. Within six months: introduce a clear enterprise operating cadence. Within twelve months: show that larger deals can be generated and closed through a repeatable process. |
| Team and reporting line | Report to the CEO. Lead 8 account executives and 3 SDRs initially, with budget to add leadership as the team grows. |
| Compensation | £150k–£180k base, performance-related variable compensation, and meaningful equity. Exact equity depends on experience and scope. |
| Role realities | The sales process is inconsistent today, CRM hygiene is weak, and several strategic relationships still sit with the founders. This is a build-and-fix mandate, not a mature machine to inherit. |
| Process | Search-partner conversation, CEO interview, commercial working session, leadership-team meetings, final board conversation, references. |
Why this example works: it gives a senior candidate the business inflection point, the mandate, the organisational reality, and the trade-offs. It does not waste the first half of the pack on generic company adjectives.
For this type of search, the pack should feel closer to a concise investment case for the role than to a conventional job advert. See the dedicated retained-search candidate pack use case if this is your main hiring model.
Candidate pack example #2: retained search — Head of Data
Scenario: a private-equity-backed services group has grown through acquisitions. The retained search is for its first group-level Head of Data.
Illustrative opening:
This is not a greenfield data role. The group has grown through twelve acquisitions, and the underlying businesses still use different systems, reporting definitions, and operational processes. The first Head of Data will create enough consistency for leaders to trust group-level reporting without pretending the integration work is already complete.
| Section | Example content |
|---|---|
| Why the role exists | Management reporting is fragmented across acquired businesses, making it difficult to compare performance and prioritise operational improvements. |
| First priorities | Agree core definitions, map the source systems, establish a pragmatic data model, and produce a credible roadmap rather than attempting a full-platform replacement immediately. |
| Stakeholders | Work closely with the CFO, COO, portfolio-company leaders, and the PE operating team. The role starts with a small central team and significant influence across local businesses. |
| Constraints | Data quality varies materially by business. Some integration decisions will be political as well as technical, and the role needs to improve trust before attempting sophisticated analytics. |
| Search process | Search-partner qualification, CFO meeting, case discussion using a representative integration problem, COO meeting, final leadership conversation. |
Why this example works: retained candidates need to understand both the upside and the mess. Saying that the data estate is fragmented is more useful than claiming the company is “data driven.” The pack also gives the search partner one approved source of truth to reuse throughout the assignment.
Candidate pack example #3: recruitment agency — Senior Product Designer
Scenario: an agency is hiring a Senior Product Designer for a fintech client. The recruiter needs to make the opportunity feel credible without writing as if they are the employer.
Illustrative opening:
We are representing a profitable fintech that is rebuilding the product experience used by small finance teams to manage cash flow and payments. The design team is moving from reactive feature delivery to clearer product ownership, and this hire will work directly with the Head of Product on the highest-usage workflows.
| Section | Example content |
|---|---|
| Client context | Profitable fintech, roughly 140 employees, serving small and mid-sized finance teams. The agency should distinguish confirmed client facts from its own interpretation. |
| Role scope | Own discovery and interaction design across payments and cash-flow workflows, partnering with one product manager and six engineers. |
| Why a candidate might care | The role has direct access to customers, a senior product partner, and enough product maturity to improve existing high-volume workflows rather than design speculative features. |
| Practical details | £80k–£95k, UK remote with one London team day per month, permanent employment, no sponsorship for this search. |
| Agency next step | Book a 25-minute recruiter conversation. The recruiter will confirm fit, answer questions, and share the client name before submission where the search terms allow it. |
Why this example works: it is transparent about the recruiter’s role. Agency candidate packs become weaker when they imitate a client careers page and hide who is actually communicating with the candidate. Keep the client story strong, but make the agency relationship and next step explicit.
Candidate pack example #4: outbound sourcing — Staff Backend Engineer
Scenario: an in-house recruiter is approaching passive engineers who are not actively applying. The pack is linked from a short personalised sourcing message.
Illustrative opening:
You would be joining the team responsible for a payments API processing millions of requests each day. The immediate challenge is reliability rather than greenfield feature work: two services need stabilising before the team can complete a larger platform migration.
| Section | Example content |
|---|---|
| Why now | Transaction volume has outgrown parts of the current architecture, and the team needs another senior engineer who can improve reliability while shaping the migration path. |
| First 90 days | Understand the failure modes of two critical services, improve observability, remove the highest-risk reliability issues, and propose a staged migration plan. |
| Team | Five backend engineers, one engineering manager, one product manager, and a shared platform team. This is an individual-contributor role with technical leadership expectations. |
| Compensation and work setup | £95k–£120k plus equity. Remote in the UK, one London engineering day per month, and participation in the production on-call rota. |
| Low-friction CTA | Interested enough to explore it? Book a 20-minute conversation. Not interested? Decline without applying. |
Why this example works: passive candidates need a reason to spend attention before they need a complete application journey. Lead with the technical problem, the scope, and the trade-offs. Do not make someone read a company-history essay before they understand why you contacted them.
Role.so can personalise a reusable pack for targeted outreach while keeping the underlying role content consistent. Open the personalised candidate pack demo to see the pattern in practice.
Candidate pack example #5: inbound hiring — Growth Marketing Manager
Scenario: candidates arrive through search, social posts, referrals, and job boards. The pack is public and reusable rather than personalised.
Illustrative opening:
We have strong founder-led demand and a growing base of product-led signups, but no repeatable paid or lifecycle acquisition engine yet. This role will own the transition from opportunistic growth activity to a measurable acquisition system across content, lifecycle, and selected paid channels.
| Section | Example content |
|---|---|
| Role outcomes | Build a channel baseline, improve activation-oriented lifecycle campaigns, run focused acquisition tests, and create a reporting cadence the team can use to decide where to invest. |
| Current state | Organic and founder-led channels are working, but attribution is inconsistent and paid acquisition has not been operated systematically. |
| Candidate requirements | Hands-on B2B growth experience, comfort working across analytics and execution, and evidence of learning from small experiments rather than simply increasing spend. |
| Practical details | £65k–£80k, hybrid London two days per week, permanent role, 25 days holiday plus public holidays. |
| Application process | Apply with LinkedIn or CV, recruiter conversation, hiring-manager interview, paid practical discussion using a supplied dataset, final founder conversation. |
Why this example works: inbound candidates can handle more detail because they are already evaluating the company. The pack should answer practical questions before the application and help unsuitable candidates self-select out before either side spends time on interviews.
Candidate pack example #6: confidential search — General Manager
Scenario: a search firm is replacing a current General Manager. The company identity cannot be disclosed in the first outreach, but the candidate still needs enough information to decide whether to engage.
Illustrative opening:
We are conducting a confidential search for a General Manager to lead a UK business unit within a larger international group. The current leader remains in post, so the company name is being withheld at this stage. We can still share the mandate, scale, reporting line, location expectations, compensation range, and process before asking you to invest significant time.
| Section | Example content |
|---|---|
| What can be disclosed | UK business unit, approximately £70m revenue, around 400 employees, international parent, multi-site operations, Midlands location. |
| Mandate | Improve operating discipline, rebuild trust between the central team and site leaders, and deliver a two-year margin-improvement plan without compromising service quality. |
| Compensation | £160k–£190k base plus bonus and standard executive benefits. The range can be disclosed even if the company name cannot. |
| Confidentiality boundary | State clearly what is withheld and why. Do not invent vague employer-brand language to compensate for missing facts. Share the company identity at the agreed stage of the search. |
| Next step | Confidential 30-minute conversation with the search partner. Candidates who meet the initial criteria receive the fuller client briefing at the next stage. |
Why this example works: confidentiality should reduce unnecessary disclosure, not reduce clarity about everything. A strong confidential candidate pack is explicit about the information it cannot yet share and unusually precise about the information it can.
See candidate packs for confidential searches for the workflow in more detail.
Compare the six candidate pack examples
| Example | What matters most | Personalisation | Best next step |
|---|---|---|---|
| Executive search | Business inflection point, mandate, leadership context, compensation, trade-offs. | Usually high. | Speak with the search partner. |
| Retained search | Client context, mandate, stakeholder map, constraints, approved search narrative. | High for priority prospects. | Qualification conversation. |
| Recruitment agency | Credible client context, recruiter role, confirmed practical details. | Useful but not essential. | Recruiter call or submission discussion. |
| Outbound sourcing | Why this person should care, concrete challenge, compensation, low-friction CTA. | Very useful. | Short exploratory call or decline. |
| Inbound hiring | Complete role context, requirements, practical details, application process. | Usually unnecessary. | Apply. |
| Confidential search | Mandate, scale, compensation, disclosure boundary, timing of fuller information. | High. | Confidential search-partner conversation. |
Real public candidate pack examples worth studying
The worked examples above are intentionally easy to adapt. It is also useful to inspect how real organisations structure candidate information in public recruitment processes.
- Role.so live demo. Open the demo catalogue to see a web-based candidate pack in reusable and personalised form.
- GOV.UK. The Disability and Access Ambassador candidate information pack is a useful example of a formal public-appointment pack.
- UK Research and Innovation. The Director of Security and Resilience candidate pack shows how a senior public-sector opportunity can be packaged with substantial organisational and process context.
These examples serve different hiring models. Do not copy their length or tone automatically. Copy the principle: give candidates enough specific information to make a better decision.
Weak candidate pack copy vs stronger copy
Generic candidate-pack language often sounds polished while saying very little. The easiest upgrade is to replace claims with concrete context.
| Weak copy | Stronger copy |
|---|---|
| Join a fast-growing company at an exciting stage of its journey. | Revenue has grown from £4m to £11m in two years, and the company is now building its first repeatable enterprise sales motion. |
| You will make a real impact from day one. | Your first 90 days are focused on stabilising two critical services and proposing a migration plan the team can execute over the following year. |
| Competitive salary and excellent benefits. | £95k–£120k plus equity, remote in the UK, one London team day per month, and participation in the production on-call rota. |
| We move fast and are looking for someone comfortable with ambiguity. | The operating model is still being built, several decisions remain founder-led, and the person joining will need to create structure rather than inherit it. |
A candidate pack should help someone understand the actual opportunity. If a sentence could describe almost any company, it is probably taking space without helping the decision.
Copy this candidate pack structure
If none of the six examples matches your role exactly, start from the same seven-part framework used in the candidate information pack guide:
1. Role and outcomes
Explain the mandate, scope, first priorities, and what success looks like. Avoid repeating the job title in paragraph form.
2. Team and reporting line
Name the manager or reporting level, describe the immediate team, and show the working relationships that matter.
3. Company and context
Explain what the organisation does, its stage or operating context, and the event or problem that created the role.
4. Compensation and employment terms
Give a meaningful salary range where possible, plus variable pay, equity, contract type, and benefits that materially affect the decision.
5. Working arrangements and logistics
Be explicit about location, remote or hybrid expectations, travel, hours, start-date constraints, and work eligibility.
6. Hiring process and next step
List the stages, approximate timeline, assessments, and the immediate action you want the candidate to take.
7. Role realities and trade-offs
Say what will be difficult, unfinished, constrained, or unsuitable for some candidates. This is often the section that makes the pack feel credible rather than promotional.
Need a blank starting point?
Use Role.so's starter content template if you want the structure without the worked sample copy.
Turn a candidate pack example into a live Role.so page
Once the structure is right, Role.so lets you turn it into a candidate-facing page rather than another static document.
- start from a reusable pack structure for the role
- replace generic claims with role-specific context, outcomes, compensation, process, and trade-offs
- personalise the page when you are approaching priority candidates directly
- publish the pack and share the same source of truth across outreach, referrals, and follow-up
- use engagement and decline feedback to see where candidates respond or disengage
Role.so can be used alongside an ATS rather than replacing it. Interested candidates can continue into your existing application or scheduling workflow, while the candidate pack handles the explanation and decision context before that step. If you are evaluating the tooling itself, see candidate pack software.
View the live Role.so examples or start creating your own candidate pack.
Frequently asked questions
A candidate pack example shows completed content for a specific hiring situation, so you can see the level of detail and wording in context. A template gives you the empty structure to fill in. Use examples for judgment and templates for production.
It can be. PDFs are common in formal and public-sector recruitment, but a web-based pack is easier to update, share, personalise, and measure. The right format depends on the hiring process and any formal documentation requirements.
The core role information can stay the same, but the emphasis should change. Outbound packs should surface the reason to care quickly and can be personalised. Inbound packs can carry more complete application context because the candidate has already chosen to investigate the role.
Long enough to answer the important decision questions without forcing the candidate through repetitive employer-brand copy. For many roles, clear sections on the role, team, company context, compensation, working arrangements, process, and trade-offs are more useful than a fixed page or word count.
Prioritise the business context, why the mandate exists now, the outcomes expected from the hire, leadership relationships, compensation, search process, and the difficult parts of the assignment. Senior candidates usually need the investment case for the role, not a longer job description.
Use the pack as a client-approved candidate briefing that clearly distinguishes confirmed client information from the recruiter's own role in the process. Make the client story credible, disclose practical details early, and keep the recruiter as the explicit next step.