How to Hire Purple Squirrels Without Chasing a Fantasy
A purple squirrel is recruiting shorthand for the candidate who seems to fit every line of a role at once: the right education, the right skills, the right experience, and the right personality.
The problem is not that such people never exist. The problem is that job descriptions often turn a manageable set of requirements into an impossible checklist. This guide shows how to keep the useful parts of the purple squirrel idea while building a hiring process that actually reaches rare, high-fit candidates.
What a purple squirrel means in recruiting
The term describes a candidate who matches a role so closely that they feel almost unreal. In practice, the label usually hides a mix of genuine requirements and wishful extras. A useful first step is to separate the two. Ask which qualifications the person cannot do the job without, and which ones would merely be pleasant to have. That distinction changes the search from a hunt for a perfect specimen into a focused search for a capable person.
Purple squirrels are valued for three reasons. They can bring fresh solutions to a sector, they can lift output and performance, and they can make an employer more attractive to other strong candidates over time. Those are real benefits, but they do not require a candidate to satisfy every possible preference on day one.
What rare candidates tend to look for
Strong candidates usually weigh more than a salary figure. They look at the work itself, the people they would report to, the atmosphere of the workplace, the principles the company follows, and whether the role offers a path forward. A hiring team that can speak clearly about those points is easier to trust.
This matters because a rare candidate is also evaluating the employer. If the process feels slow, vague, or dismissive, the candidate may lose interest even when the role is a good fit. The practical lesson is to treat the hiring conversation as a two-way exchange from the first contact.
Widen the search before narrowing the shortlist
A narrow search produces a narrow pool. Posting in more than one place raises the chance that the right person sees the role. General job boards and search-driven listings can reach a broad audience, while specialist communities can reach people who already work in the field. Social platforms can add another route, especially when the role is easy to explain in a short post.
The careers page deserves the same attention. It should say what the company stands for, describe the work in a way that sounds human, and be easy for search engines to read. A page that is clear about the role and the culture does more than a page that lists every possible requirement.
Assess what people can do, not only what they have done
A strong résumé is a starting point, not a conclusion. A practical task, a coding exercise, or a structured work sample can show how a candidate handles the actual demands of the role. The goal is to test the must-have capabilities in a way that reflects the job.
This is also where transferable experience earns its place. A candidate who has solved a similar problem in another setting may be a better fit than someone who matches the job title but not the work. Skill-based assessment looks at capability, potential, and evidence of doing comparable tasks, rather than at a perfect sequence of past roles.
Keep the process human
Rare candidates often have options. A process that leaves them waiting without updates, or that gives no useful feedback, makes it easy for them to choose elsewhere. Clear communication and timely responses are not extras; they are part of the offer.
A simple rule helps: every candidate should know what happens next and when. That applies to interviews, assessments, and the final decision. A positive experience does not guarantee a yes, but a poor one makes a no much more likely.
Do not limit the search to one location
Remote work widens the pool without lowering the standard. A candidate who is a strong fit may live far from the office, and remote contracts can be handled with electronic signature tools. Widening the geography can also support diversity and inclusion, which in turn strengthens how the employer is perceived.
The point is not to hire remotely for its own sake. It is to avoid rejecting a strong candidate for a reason that has nothing to do with their ability to do the job.
Separate must-haves from nice-to-haves
The most common way to lose a good candidate is to keep adding requirements. A recruiter who is excited by a new skill may forget the core need, and a candidate who could do the job well may be rejected for lacking an extra. The result is a longer search, a higher cost, and sometimes no hire at all.
A useful discipline is to write the must-haves first and treat everything else as optional. Then check the shortlist against culture fit, team cohesion, and the practical realities of the role. A checklist is a tool, not a substitute for judgment.
A decision checklist before you start sourcing
Use this checklist to test whether the role is genuinely rare or merely over-specified.
- List the tasks the person must perform in the first three months.
- Mark each requirement as must-have or nice-to-have, and delete any nice-to-have that cannot be justified.
- Name at least two sourcing routes: one broad and one specialist.
- Write one work sample that tests a must-have capability.
- Decide who will respond to candidates and within what time frame.
- Confirm whether the role can be done remotely or in another location.
- Agree the salary range and the negotiation limits before the first interview.
If the list still reads like a description of three different jobs, the role is not rare; it is unclear. Split it or simplify it before going to market.
Worked example: rewriting a requirement set
Suppose a team asks for a senior developer who knows five programming languages, has managed a team, has worked in three industries, and can start immediately. That combination may exist, but the search will be slow and expensive.
A more practical version keeps the core: strong ability in the main language, evidence of shipping production work, and willingness to learn the rest. Team management becomes a nice-to-have unless the role truly requires it on day one. The search can then include candidates with transferable experience from adjacent fields, and the work sample can test the main language directly. The role is still demanding, but it is no longer defined by an arbitrary count of extras.
Rare candidate or wishful job description?
A genuinely rare candidate is hard to find because the combination of skills is uncommon. A wishful job description is hard to fill because it asks for more than the work requires. The two look similar from the outside, but they call for different responses.
If the search has run for a long time with no suitable applicants, check the requirements before blaming the market. If the must-haves are clear and the pool is still empty, the role may need a different sourcing route, a wider location, or a longer hiring timeline. If the must-haves keep growing, the problem is the brief.
Intake field map for the hiring brief
A short, structured brief makes the checklist usable. Capture the following fields before sourcing begins:
- Role title and core purpose
- Must-have capabilities, each tied to a task
- Nice-to-have capabilities, each with a reason
- Sourcing routes, including at least one specialist community
- Assessment method for each must-have
- Location and remote eligibility
- Salary range and negotiation limits
- Response owner and expected reply time
- Target start date and decision date
This map keeps the conversation focused on the work rather than on an ever-growing list of preferences.
Frequently asked questions
What is a purple squirrel in recruiting?
It is a candidate who appears to match a role across education, skills, experience, and personality. The label is useful as a shorthand, but it can encourage teams to ask for more than the job really needs.
Do purple squirrels actually exist?
Yes, in the sense that some candidates are unusually strong fits for a particular role. The difficulty is that a job description can turn a realistic fit into an impossible checklist. The practical task is to define the must-haves clearly and then search widely.
How can a recruiter attract rare candidates?
Post in more than one channel, including specialist communities; make the careers page clear and easy to find; assess capability with a work sample; and keep communication timely. Rare candidates often have choices, so the process itself becomes part of the pitch.
What is the difference between must-have and nice-to-have skills?
A must-have is a capability the person needs to perform the core tasks of the role. A nice-to-have is a preference that adds value but is not essential on day one. Keeping the two separate prevents good candidates from being rejected for lacking an extra.
Does remote hiring help with rare candidates?
It can widen the pool by removing a location constraint. Remote contracts can be handled with electronic signature tools, and a wider geography can also support diversity and inclusion. The decision should still rest on the candidate's ability to do the work.