04 Recruitment Marketing
The Explanation
Problem
Strong companies are often badly understood.
The explanation chain
Complexity
What you actually build
Confusion
What candidates hear
Low trust
Doubt replaces curiosity
Weak hiring
Strong candidates don't engage
Every unexplained complexity is a hiring cost. Clarity is not a marketing exercise — it's an operational one.
Why this matters
Many hiring problems begin long before the job is posted.
Technical companies routinely under-explain themselves. The team knows exactly what they build and why it matters. Candidates — particularly the strong ones who have options — often don't. The gap between internal clarity and external understanding is where hiring stalls.
A candidate who doesn't understand what the company does can't evaluate whether the problem is interesting. A candidate who can't evaluate the problem can't become genuinely excited about the role. A candidate who isn't excited has little reason to prioritise your process over three others in their inbox.
The explanation problem is not a marketing problem. It's a hiring problem — with a marketing-adjacent solution. Companies that explain themselves clearly hire faster, at lower cost, from stronger candidate pools.
Founder reality
Before the next search opens, test your explanation quality:
Could a strong engineer who knows nothing about us describe what we build after reading our careers page?
Can we explain what makes our technical problem genuinely interesting in two sentences?
Do we rely on insiders to 'sell' the company to candidates in the interview — rather than the company speaking for itself?
Have we ever asked a declined candidate why they passed — and was confusion part of it?
Does our public-facing content help candidates understand the work — or just the mission statement?
If the answer to most of these is uncertain, the explanation problem is costing real hiring outcomes.
The framework
Four stages of the explanation problem
Each stage compounds the one before it. Fixing explanation early prevents friction downstream.
01
Complexity — the product is hard to explain and nobody has tried
Technical products often involve layers of abstraction, specialised terminology, and non-obvious value propositions. When founders and teams don't invest in translating this complexity into legible explanation, it defaults to jargon — which candidates interpret as either confusion or arrogance.
02
Confusion — candidates can't form a clear picture of what they'd be joining
Without a clear explanation, candidates fill the gap with assumptions — often unflattering ones. Is this a solution looking for a problem? Is the team small because the product hasn't worked? Is the technical challenge genuinely hard, or just poorly described? Confusion breeds doubt.
03
Low trust — doubt replaces genuine curiosity
Strong candidates are good at assessing opportunities. When a company can't clearly explain itself, the trust signal is negative. The implicit message is: if they can't explain their product clearly, what else is unclear about how they operate?
04
Weak hiring — the best candidates deprioritise the process
Candidates with multiple options don't spend time decoding confusing companies. They engage with the clearest, most compelling opportunity available. The explanation problem doesn't just lose candidates who decline — it loses candidates who never engaged at all.
Common mistakes
01
Delegating explanation to the interview
Relying on a great founder pitch in the interview assumes the candidate made it to the interview. Strong candidates often self-select out before applying if the company is poorly explained externally.
02
Confusing mission with explanation
'We're building the future of X' is a mission statement, not an explanation. Candidates need to understand what the product does, who uses it, and what makes the technical problem interesting — not the aspiration.
03
Over-indexing on NDA-sensitive details
Many companies withhold explanation because the product is sensitive. There is always something that can be shared — the problem category, the engineering challenge, the type of users. Excessive secrecy reads as having nothing interesting to say.
04
Writing career content for investors, not candidates
Investor messaging and hiring messaging serve different audiences. TAM, market size, and category leadership matter to investors. System design, technical challenge, and team culture matter to engineers.
Example scenario
A cybersecurity infrastructure startup, 35 people. Consistently losing strong candidates to larger competitors despite a more interesting technical problem.
The explanation audit
Careers page: three paragraphs of mission language. No description of the technical problem. No engineering team content.
LinkedIn company page: last post 4 months ago. No technical content.
Founder LinkedIn: occasional thought leadership. No content about what the company actually builds.
GitHub: private. No public technical presence.
The fix
Careers page rewritten: specific description of the security problem, the technical approach, and the engineering challenges.
Founder published three technical pieces in 8 weeks — what the company is building and why it's a hard problem.
One engineering blog post per month from the team, explaining a real system decision they'd made.
The outcome
Inbound applications from strong candidates increased 40% over 10 weeks. Candidate drop-off before first interview reduced by half. Two senior hires made from candidates who cited the technical content as the reason they applied.
Takeaway
Explanation is not a marketing cost. It's a hiring investment.
Every hour spent making your company legible to candidates pays back in better applications, faster processes, and stronger hires. Start with the simplest question: can someone who doesn't know us understand what we build?
Related thinking
Recruitment Marketing
Why Nobody Understands Your Company
A strong product can still feel invisible.
Recruitment Marketing
Hiring Is Also Marketing
Hiring starts long before the interview.
Recruitment Marketing
Technical Teams Often Feel Invisible
Strong engineering teams are often poorly explained.
Continue reading
Why Nobody Understands Your Company