Product update

Every question about the role, in one turn

The AI researches your job description first, then asks whatever it cannot settle itself, up to eight questions at once. You answer once and the brief is built.

All posts
EL
The EmployLabs team
· 4 min read
In short

EmployLabs resolves a job description by researching what it can first, then asking up to eight clarifying questions in a single turn rather than asking you what it can find out itself. The recruiter answers once and the brief is built, instead of being led through one question per message. The questions come from the real gaps in that description rather than from a fixed form.

The brief that turns into an interrogation

Most tools that take a job description and try to build something from it ask about it one question at a time. You paste the description, you get a question, you answer it, you get another question. Each exchange is short and reasonable on its own, and the whole thing is exhausting, because a brief that should have taken five minutes has become a twenty-message interrogation conducted at the pace of a chat window.

What happens next is predictable. Recruiters abandon it halfway. Not out of impatience, but because the shape of the conversation gives no indication of how much is left. After the eighth question there is no way to tell whether the ninth is the last one or the first of another twelve, and a task with no visible end competes badly with everything else in an afternoon.

The half-finished brief is then worse than either extreme. The role carries some of the answers and not others, and nobody remembers which. The questions that were never reached get resolved later by assumption, which is precisely what asking them was supposed to prevent.

Work out the ambiguity first, then ask once

On EmployLabs the order is reversed. When a job description arrives, the AI works through it first. It researches what it can rather than asking you, and asks only about the points wherethe description could reasonably mean more than one thing and the difference would change who ends up being contacted. Only then does it ask, with up to eight questions.

And it asks them all in one turn. You see every open question at once, answer them in a single pass, and the brief is built. There is no second round produced by your answers to the first, because the ambiguity was worked out before the asking started rather than discovered one reply at a time.

A brief should be one turn with every question in it, not twenty turns with one question in each.

Seeing the whole set is the point

Answering ten questions at once is not merely faster than answering ten questions in sequence. It is a different task. The set is visible, so you can see what it will cost you before you start, and choose to do it now instead of abandoning it in the middle.

The questions also inform each other. Read together, they often show that two of them are really the same decision, or that answering the third makes the seventh irrelevant. Answered one at a time that never becomes apparent, and you commit to the first answer without knowing what it implies for the rest.

It is also the honest version of the interaction. A drip of questions conceals the true cost of the brief and reveals it only once you are too far in to stop. Showing all of it up front respects the fact that a recruiter is deciding whether to spend the next few minutes on this role or on something else.

Questions about the role, not a form to complete

The questions are not a fixed questionnaire applied to every job. They come from this description and its particular gaps. A job description that already states its salary band plainly is not asked for the band again, and a description that is precise about the engineering but vague about who the person reports to gets asked about reporting rather than about the engineering.

That is why the number of questions differs from role to role. A carefully written description generates few, because there is little left to resolve. A description assembled from an old template generates more, because the ambiguity is really there, and finding it now is far cheaper than finding it in the replies three weeks later.

  • No question you have already answered. If the description says it, the description is believed, and you are not asked to type it a second time.
  • No question that does not change the search.Ambiguity that makes no difference to who gets contacted is not worth a recruiter’s attention.
  • No hidden second round. The set you are shown is the set, so the brief is finished when you have answered it.

How to use it

  1. Read all the questions before answering any of them. They were written as a set and they are quicker to answer as one.
  2. Treat an unexpected question as information about the description. If you are being asked something you thought was obvious, the description did not say it, and everyone reading it afterwards would have guessed too.
  3. Forward the set to the hiring manager when an answer is genuinely theirs. A short list of specific questions is a much easier thing to send than a request to review a brief, and it tends to come back the same day.

Common questions

How long does it take to brief the AI on a new role?
One turn. EmployLabs reads the job description, researches what it can, and asks up to eight clarifying questions at once. You answer the set in a single pass and the brief is built, rather than being taken through one question per message.
Why not ask the questions one at a time like a chatbot?
Because a drip of one question per reply turns a five-minute brief into a twenty-message interrogation with no visible end, and recruiters abandon it halfway. A half-answered brief then leaves some decisions to assumption, which is what asking was meant to prevent.
Are the questions the same for every job?
No. They come from genuine ambiguity in the description you supplied. A job description that already states its salary band is not asked for it again, so a precise description produces few questions and a vague one produces more.

Related reading

All posts →

See it on one of your own roles

Upload a job description and watch the pipeline run before you commit to anything.