A hiring manager who’s run the same team for many years has a hard time explaining why it’s a good fit for someone new — not because they don’t know, but because they know it so well they’ve forgotten what it’s like not to. A recruiter working that same opening often has the mirror-image problem: they haven’t been there long enough to describe it convincingly at all. Different causes, same result. Neither one can say, in the moment, why this specific role is worth wanting.
This is a well-documented bias: people with specific knowledge consistently fail to accurately imagine what it’s like to lack it, even when it’s directly in their interest to do so (Camerer, Loewenstein & Weber, 1989, doi.org/10.1086/261651).
One Fix, Two Problems
That bias explains the manager’s half. The recruiter’s half doesn’t need a citation — it’s just what happens when you’re new.
Most companies treat this as two different problems needing two different fixes: train the manager to communicate better, give the recruiter more time on the team. Both take months. There’s a faster fix already sitting in front of both of them: the job posting. Written properly — with the actual attributes, the real team dynamics, not boilerplate — it isn’t just an ad a candidate reads once. It’s the same information the manager has trouble saying out loud, and the same information the recruiter hasn’t learned yet, already written down.
Nobody needs a second script. The posting already is one.
The Interview Backwards
This matters most at the exact moment most interviews get backwards. A first conversation with a candidate often turns into a checklist — years of experience, specific tools, can-you-start-Monday — before either side has established why this particular team is worth wanting in the first place. That’s a credit-check conversation happening before anyone’s decided they want to be there. A good first date doesn’t open by asking about someone’s credit score; it gives them a reason to want a second one. The interview should do the same before it does anything else.
A Running Start
Hand either of them the posting’s own language at that moment, and something else happens too: once it’s in their head, most stop reading from it and start describing the role in their own words, better than before — because now they have the right words for something they either always understood but never explained well, or never had the tenure to know at all. It’s a running start either way.A manager or recruiter can build this kind of language on their own, if the original posting was actually written with real thought put into it. That’s the whole method, and it works whether or not you ever use JobWriter. But if this is the exact problem you’re reading this to solve, say so plainly: this is exactly what JobWriter was built to do — write that posting once, with the real thought already in it, so it becomes the script for everyone who has to sell the role afterward, for as long as that posting exists. The actual answer.
