The Worst Hiring Brief Ever: How OVI's AI Recruiter Turns a Terrible Intake Call Into a Job Spec
By Chris Weinmann, Founder, OVI
Every recruiter has had this call
Vague. Contradictory. Slightly panicked.
"I need a developer. The computer kind. Full stack or backend — actually, what's the difference? Senior, but I only have junior salary. Fluent in every programming language. And German, English, and Arabic. Starts this week."
That is not a brief. That is a cry for help wearing a job description.
So we decided to be that hiring manager on purpose.
No forms. A four-minute call.
This is OVI's new onboarding flow. There is no 40-question intake form. You get on a call with your AI recruiter, talk like a normal human — or, in this case, a terrible one — and she asks the questions a good recruiter would ask.
Four minutes later you have a proper requirement profile.
In the video, Chris plays the worst hiring manager of all time. The AI still gets a job spec out of him.
What we threw at her
The brief was designed to fail:
- Full stack or backend, but also "I need everything"
- Senior talent on a junior budget
- Fluent in all programming languages
- Fluent in German, English, and Arabic
- Start date: this week. Basically yesterday.
A form would have accepted all of that and launched a unicorn search. A junior recruiter might have nodded, written it down, and spent three weeks explaining why the market is empty.
The AI did not nod along.
She didn't take the brief. She negotiated it.
First she translated the confusion. Full stack means front end and back end. Backend is deeper in one area. Then she asked the only useful question: which one matches what you're actually building right now?
When the answer stayed impossible, she named it. Senior plus junior salary in an expensive market thins the pool to nearly nothing. Three languages plus every programming language is not a person. That's a unicorn.
Then she pushed: what's the actual must-have — seniority in one or two core languages, or owning the stack end to end?
When "starts this week" got stacked on top, she was blunt. A senior full-stack developer, fluent in three languages, paid at junior rates, starting this week does not exist. Not one. Pick the real constraint: seniority, stack breadth, languages, or start date.
That's the moment a human recruiter earns their fee. The AI did it on the first call.
The pushback worked. Budget got more flexible. Immediate joiners stayed in play. Then she locked what was actually true instead of what was wished for.
What got locked in
From a chaotic rant, she created a Full Stack Developer role and wrote down the real bar:
- Full-stack capability, not "every language on earth"
- Senior level: 5+ years shipping production code
- Experience range: 5 to 10 years
- Then she asked for the actual stack — React, Node, Python — instead of accepting "fluent in all programming languages"
She also explained what happens after the call, because a brief that sits in a Google Doc is still just a brief.
After the brief: post, hunt, or promote
Once the intake is wrapped, you get three options. Tick one, two, or all three:
- Create the role and post it. People apply inbound.
- Search cold talent. OVI hunts passively for people who already fit the bar.
- Promote internally if you already have candidates in mind.
That's the point of a real requirement profile. Screening, sourcing, and inbound all need the same constraints. If the intake is a unicorn, every channel fails the same way.
This is the hiring-manager twin of our worst-candidate AI interview test. There, OVI stayed professional when the candidate was impossible. Here, she stays professional when the brief is impossible — and she doesn't let you ship it that way.
Why this replaces the intake form
Most ATS onboarding rewards whoever can fill boxes fastest. The hiring manager who is vague on a call is even vaguer in a form. Nobody pushes back. The search goes live. Recruiters spend the next three weeks delivering bad news.
A good recruiter's job in intake is not transcription. It is constraint. Name what cannot be true. Force the trade-off. Lock what is real.
That is now the first four minutes of OVI.
I said "senior but junior salary" and "starts yesterday." She still got a job spec out of me.
Watch the call.
What is OVI's AI recruiter onboarding?
OVI's new onboarding is a voice call with an AI recruiter instead of a 40-question intake form. You talk like a normal hiring manager. She asks the questions a good recruiter would ask, pushes back on contradictions, and locks a requirement profile in about four minutes.
Can an AI turn a messy hiring brief into a job spec?
Yes — if it is allowed to negotiate, not just transcribe. In this video the hiring manager asked for senior talent on a junior salary, fluency in every programming language plus German, English, and Arabic, and a start date of this week. The AI named the unicorn, forced a trade-off, then locked a Full Stack Developer role with senior-level production experience.
Does OVI's AI recruiter push back on unrealistic requirements?
That's the point of the intake. She explains trade-offs (full stack vs backend, senior vs junior budget, three languages vs one), says when a combination does not exist in the market, and asks which constraint actually matters: seniority, stack breadth, languages, or start date.
What can you do with the brief after the call?
Once the brief is wrapped you can create the role and post it for inbound applicants, search cold talent (passive hunt), promote internally, or do all three. The AI shows selection cards at the end so you tick what you want.
How is a voice intake better than a 40-question intake form?
Forms reward whoever fills boxes fastest and never push back. A vague hiring manager becomes an even vaguer form. A call lets the AI clarify stack, seniority, budget, languages, and start date in conversation, then lock only what is real so screening and sourcing are not hunting a unicorn.