What the hiring manager said, and what the job description kept
The intake holds the distinctions that decide the hire. Almost none of it survives into the job description, and everything downstream gets built on the sanitized version.
Here is a pattern that repeats on almost every requisition.
In the intake meeting, the hiring manager says something like this:
“I need someone who has actually owned a service in production, not just shipped features. The last two hires could code but froze during an incident. I care more about how they debug than which framework they know.”
Specific. Opinionated. Full of the distinctions that actually decide the hire.
By the time it reaches the job description, it reads:
“5+ years backend engineering experience. Proficiency in Go or Java. Experience with microservices and AWS. Strong problem-solving skills.”
Sanitized, generic, and interchangeable with a thousand other reqs.
Then everything downstream gets built on the second version. The search strings. The screening criteria. The prescreen questions. Forty candidates get measured against requirements the hiring manager never said mattered most.
The intake is the most valuable artifact in recruiting
It is also the most consistently discarded. In most teams it already exists, recorded or written down. It just never gets opened again after the meeting ends.
Every tool we build starts by putting it back in front of the resume.