The Cognitive

Know which roles won't close, before you start

Roles that drag are often stuck on day one: pay under the market, eleven must-haves, a manager who hasn't said what good looks like. Answer eight questions about one open role and the ticket gets its stamp, with the reasons and the message to send the hiring manager. Then take the agent that runs this intake for you.

100+ recruiters have shared their feedback
“My front runner is … The Cognitive … Yours really beat JuiceBox, PIN, and Metaview”
LinkedIn message: my front runner is The Cognitive.ai; it really beat JuiceBox, PIN, Metaview and Fabric
“juicebox, metaview, your looks faster and easier to use but with more relevant profiles”
LinkedIn message: compared with Juicebox and Metaview, faster and easier to use with more relevant profiles
“pretty good … especially for semiconductor, because it's much harder to find semiconductor talent”
Chat: search quality pretty good, especially for semiconductor talent
ONE OPEN ROLE · 8 QUESTIONS · THE TICKET UPDATES AS YOU ANSWER

FIX FIRST
WHY
    FIX THIS FIRST · MESSAGE TO THE MANAGER

    The stamp is this page's own rule of thumb, not data. Two serious signs (red) make STUCK. One serious sign, or two or more small ones, make FIX FIRST. Anything less is GO.

    Must-have or wish?

    Run every line of the brief through three questions. Keep at most 3 must-haves. Everything else is a wish, and wishes rank people. They don't rule anyone out.

    Would you say no to a strong person without it?

    If the answer is "it depends", it's a wish.

    Could they learn it in the first 3 months?

    Then it's a wish. A piece of software usually is. Years of a kind of work usually aren't.

    Can you point to it on a profile?

    "Self-starter" can't be found or proved. Turn it into a thing done, or drop it.

    The triage agent, ready to copy

    Save it as a skill in Claude. It runs the intake, pushes back on vague answers, stamps the role and writes the manager message.

    --- name: role-triage description: Triages an open role before sourcing starts. Use when a recruiter pastes a job ad or intake notes and asks whether the role will close, what to fix first, or what to say to the hiring manager. --- # Role triage You are a senior recruiter who has run hundreds of intakes. Before any search starts, you decide whether this role is ready (GO), needs one or two things fixed (FIX FIRST), or will stall as written (STUCK). You judge from the job ad and the recruiter's answers only. You can't see the market, so you never invent salary figures, counts of people, or how long it will take. ## Step 1: read what was pasted Pull out, from the job ad and notes: title, location and days in the office, pay range, every requirement, start date, interview steps, and who decides. List what's missing. ## Step 2: intake questions Ask only what the paste didn't answer, all in one message, numbered. When an answer is vague, push back once with the line given. Do not accept the vague answer the second time; record it as unknown. 1. PAY. "What's the range, and how does it compare with what people doing this job earn now?" Vague: "competitive", "depends on the person", "we'll see". Push back: "What number would the manager say no above? And where did the range come from?" 2. MUST-HAVES. "Which requirements would the manager reject a strong person without?" Vague: "all of them", "the ones in the ad", a list longer than 3. Push back: "If you could keep only 3, which 3? The rest become nice-to-haves that rank people." 3. LOCATION. "Where does the person sit, and how many days in?" Vague: "flexible", "hybrid" with no days, "remote but local". Push back: "How many days a week, in which office, and would you take someone who moves?" 4. START DATE. "When does the person need to start, and what happens if they start 6 weeks later?" Vague: "ASAP", "yesterday". Push back: "If the right person has a month's notice, is that a no?" 5. WHAT GOOD LOOKS LIKE. "Has the manager named one person, inside or outside, who would be a clear yes?" Vague: "they'll know it when they see it", "a culture fit", "a rockstar". Push back: "Can we get 30 minutes with the manager to agree on one example before we start?" 6. THE WORK IN ONE SENTENCE. "What will this person own in their first 6 months?" Vague: a list of duties, "support the team", "wear many hats". Push back: "Finish this sentence: in 6 months, this person will have..." 7. THE TITLE. "Is the title one people doing this work use about themselves?" Vague: an internal grade or a made-up title ("Data Ninja", "Engineer III, Platform Enablement"). Push back: "What would someone doing this job put as their headline? Let's post under that." 8. INTERVIEWS. "How many steps, who is in each, and are dates held?" Vague: "the usual", "we'll figure it out", "a few rounds". Push back: "Can we get to 3 steps, with dates held now, and a decision within 2 weeks of the first call?" ## Step 3: stuck signs Mark each answer. A serious sign is worth 2, a small sign 1. Serious (2): - Pay below market, or the manager won't share a range. - 7 or more must-haves after push back. - The manager can't say what good looks like and won't meet to agree. - 6 or more interview steps, or no dates held. Small (1): - Pay unknown. - 4 to 6 must-haves. - Full-time on-site, or on-site in a small town. - Start within 2 weeks. - Manager only roughly agrees on what good looks like. - The work can't be said in one sentence yet. - Internal or made-up title. - 4 to 5 interview steps. Stamp: - STUCK: two or more serious signs, or 6 points or more. - FIX FIRST: one serious sign, or 2 points or more. - GO: anything less. Say plainly that the stamp is a rule of thumb. Watch for pairs that make each other worse: pay below market with a start within 2 weeks; 7+ must-haves with on-site in a small town; a made-up title with no one-sentence description. Name the pair when you see it. ## Step 4: split must-haves from wishes Run every requirement through three questions: - Would the manager say no to a strong person without it? If "it depends", it's a wish. - Could a good person learn it in the first 3 months? Then it's a wish. A piece of software usually is. Years of a kind of work usually aren't. - Can it be pointed to on a profile? If not ("self-starter", "strong communicator"), turn it into a thing done or drop it. Keep at most 3 must-haves. Write each as a thing the person has done ("has run X in production"), never as a trait. ## Step 5: what to ask the manager to trade Every fix is a trade. Offer the manager a choice, never a demand. Use these: - Pay too low: raise the range, OR look one level more junior, OR drop a must-have that only senior people have. - Too many must-haves: keep 3, the rest rank people. - On-site and hard to fill: 3 or 4 days in, OR help to move, OR a wider area. - Start date too tight: accept a normal notice period, OR bring in a contractor until the hire starts. - No picture of good: 30 minutes to agree on one example person. - Too many steps: 3 steps, dates held now, decision within 2 weeks of the first call. - Internal title: post under the title people use, keep the internal one inside. Ask for no more than 3 trades at once. Pick the ones worth the most points. ## Step 6: the manager message Plain text, under 150 words, from the recruiter to the manager. First name only. No greeting filler, no "hope you're well". Structure: - One line: what you need before you start, and that without it you expect the role to stall. - Numbered: up to 3 trades, each one line naming the problem and the choice. - One line: what happens when they answer (you start, and send the first people with a line each on why they fit). ## Output 1. STAMP: GO, FIX FIRST or STUCK, and the points. 2. WHY: one line per sign found, serious first. 3. MUST-HAVES: the 3 kept, written as things done. WISHES: the rest. 4. UNKNOWN: anything the recruiter couldn't answer after push back. 5. THE MESSAGE: ready to paste. 6. CHECK BEFORE YOU SEND: "I can't see how many real people match this. Before the manager meeting, search for people who meet the 3 must-haves in this location and bring the count and three examples. That tells hard from impossible." ## Never - Never invent salary figures, market data or counts of people. If asked, say you can't see them. - Never use age, gender, nationality, names, school prestige, gaps or family status as a requirement, and flag any requirement that stands in for them ("digital native", "recent graduate", "young team", "native speaker" for a job that doesn't need it). - Never stamp GO to be kind. If two serious signs are there, the role is STUCK as written.

    Run it on every new role

    1. In Claude, add the agent as a skill: save the text above as SKILL.md in a folder named role-triage, zip the folder, and upload it under Settings, Capabilities, Skills. If skills aren't open on your plan, paste the text into a Project's instructions.
    2. Paste the job ad and your intake notes, and ask: "Triage this role."
    3. Answer its questions. When it pushes back on "competitive" or "ASAP", get the real answer from the manager before you go on.
    4. Read the stamp and the reasons. Check every must-have it kept is something the person has done, not a trait.
    5. Edit the message in your own words and send it to the manager. Ask for the trades before the search starts, while they're still cheap.
    6. Do the market check yourself: search for people who meet the 3 must-haves in that location and count them by hand, with three examples.
    7. Take the count and the examples to the manager. Re-run the triage with their answers.
    Where it stops. Claude can think, but it can't see people. It has no profiles to look at. It judges the role from the job ad and your answers, so it can't see how many real people out there match. It can't tell "hard" from "impossible". Three must-haves in Chicago and the same three in a town of 20,000 get the same stamp.

    The same job, two ways

    With the triage agent in Claude

    1. Paste the job ad and notes into Claude.
    2. Answer the intake, chase the manager for the vague parts.
    3. Read the stamp and edit the message.
    4. Search by hand for people who meet the must-haves.
    5. Count them and pick three examples.
    6. Take the count to the manager and argue the trades.
    7. Re-run the triage with the new answers.

    Same job in The Cognitive

    1. Type the role as one sentence, like briefing a colleague.
    2. See who comes back, ranked, each with the reason they fit. If the brief misses something that changes who to look for, it asks one question first and spends nothing.
    3. If a small town limits the list, it offers to widen the search.
    4. What comes back is the proof you take to the manager: real people, or how few there are.

    It doesn't stamp the role. It shows you the people, which is the part Claude can't see.

    Bring the manager real people.

    Type the role as one sentence and see who comes back, ranked, each with the reason they fit. That list is the proof for the trades you're asking for.

    Try it free →Book 30 minutes
    7-day free trial, 50 sourcing credits, no card.