What to do when the requisition is vague

Every recruiter has taken this brief. The hiring manager wants someone senior. They want someone who can take charge. You write it down and leave the room with entirely different jobs in your heads. Six weeks later you are on candidate number eleven. The manager still says the profile is wrong. Vague requisitions are historically treated as a minor annoyance. They are often dismissed as a sign of a busy hiring manager. That era is over.

Regulatory changes across Europe and North America mean a poorly defined job profile is a compliance liability. Vague requirements break automated screening tools. They make legal pay equity impossible. Next quarter, talent acquisition leaders must mandate structured intake processes. You must translate vague requests into auditable outcomes. The market moves too fast to accommodate endless iterations of a single search. You have to force the hiring manager to define exactly what the new employee will execute.

The financial cost of ambiguity

A requisition lacking specific outcomes drains corporate resources at a staggering rate. A 2022 Society for Human Resource Management study places the average cost per hire at $4,700. That baseline number assumes a standard, functional hiring timeline. Stalled searches double or triple this cost through wasted interview hours and lost department productivity. The damage extends beyond the recruitment budget. Candidates experience a disjointed process when the requirements are undefined. They answer repetitive questions and receive conflicting information from different interviewers.

A manager asking for a self-starter is describing an emotional outcome rather than a measurable technical skill. When recruiters accept this vague language, pipelines fill with candidates who look good on paper but fail technical screens. The fundamental business problem is that managers describe what they need in behavioral outcomes. They do this because that is how they experience their own workday. They know they need relief from a specific operational pain.

Your job is translation. You cannot afford to guess what that pain is. You must diagnose it accurately during the first conversation. If your intake process takes ninety minutes and generates a document with fourteen sections, the manager will not remember any of it. Neither will the interview panel. You need a fast, precise method to extract the actual requirements.

European compliance demands objective criteria

European legislation is actively eliminating the space for vague job descriptions. The European Union Pay Transparency Directive, known formally as Directive 2023/970, forces a structural change. Member states must adopt these rules into national law by June 7, 2026. This directive applies to employers with 100 or more workers. It requires companies to base pay structures on objective, gender-neutral criteria.

If your requisition asks for leadership presence or strong communication skills, you cannot objectively defend the salary band. You must tie compensation to specific technical outputs and measurable experience. Vague intake notes will fail audit. You must prove why one candidate commands a higher salary than another. You can only do this if the initial requisition establishes clear, numeric baseline requirements.

European recruiters face immediate pressure from the EU Artificial Intelligence Act. Approved in March 2024, this legislation classifies recruitment and applicant sorting software as high-risk systems under Annex III. If you use automated tools within your applicant tracking system to rank candidates against a vague job description, you risk systemic bias. The algorithm has to guess what a strong leader looks like. It will typically default to historical data favoring specific demographics.

Talent teams must replace abstract adjectives with concrete technical requirements before feeding any profile into an automated matching system. You need to audit your enterprise software configurations. Ensure matching algorithms run on hard skills rather than inferred traits. You cannot rely on an algorithm to interpret what a manager meant when they asked for someone who can own a process. General Data Protection Regulation requirements also mandate data minimization. You cannot legally collect and process personality assessments if those traits are not explicitly required by the role.

North American pay transparency limits wish lists

North American regulators are attacking vague requirements through pay transparency mandates. A hiring manager asking for a hybrid junior-to-senior profile usually wants the recruiter to test the market. They want to see what talent is available before committing to a budget. This approach is no longer legal in major economic hubs.

California Senate Bill 1162 went into effect on January 1, 2023. It mandates pay scale disclosures on all job postings. Penalties range from $100 to $10,000 per violation. You cannot post an accurate pay scale if the hiring manager refuses to define the seniority level during the intake meeting. You must lock in the exact level of responsibility before writing the external advertisement.

Colorado enforces similar rigidity. Updates to Part 4 of the Equal Pay for Equal Work Act, effective January 1, 2024, require employers to include application deadlines on public postings. You cannot leave a vague job open indefinitely while the manager waits for inspiration. You must run a defined search within a specific timeframe.

New York City Local Law 144 enforces bias audits on automated employment decision tools. Companies face fines up to $1,500 per violation for non-compliance. If your screening criteria consist of undefined soft skills, your algorithmic tools cannot pass an independent bias audit. Recruiters operating in these jurisdictions must force managers to commit to a specific scope of work before generating a requisition. You must refuse to open searches based on broad wish lists. Internal equity is another major factor. When you hire based on vague criteria, you invite pay discrimination claims from existing employees doing identical work.

The failure of trait-based intake forms

Standard intake forms invite vague answers. They ask the manager to list required traits. Managers respond with generic terms like proactive, resilient, and collaborative. These words mean nothing on a resume. They mean even less during a thirty-minute phone screen. You cannot recruit against an adjective.

You must shift the conversation from traits to deliverables. The fastest translation tool available is a single question asked three different ways. You must interrogate the actual work rather than the theoretical person. This requires managing the meeting tightly. Do not let the hiring manager read from a previous job description. Those documents are usually outdated the moment they are written.

Force them to talk about the immediate future of their department. If they cannot articulate the daily operational reality, you cannot expect a candidate to understand the role. A vague brief guarantees a poor candidate experience. Top tier talent will abandon an interview process if the hiring manager cannot clearly define success.

Ask what the first six months look like

The fastest way to translate a vague request is to focus on the calendar. Do not ask the manager to draft a job description. Ask them what the person is doing in week two. Ask what will visibly change in the department by month six. Answers to these questions provide concrete metrics.

A manager might say the new hire needs to rebuild the onboarding flow by month four. They might expect support ticket volume to drop by 15 percent by month six. These are testable outcomes. You can build an interview scorecard around rebuilding an onboarding flow. You can test a candidate on their strategies for reducing ticket volume. You cannot build a valid scorecard around a vague desire for stakeholder management.

If the manager cannot describe what the employee will achieve in the first six months, the role is not ready to open. Treat this as a useful finding rather than a failure. It is better to delay a requisition than to open a search blindly. Document this delay in your applicant tracking system. Tag the requisition as pending scope definition. This protects your recruitment metrics from artificial inflation caused by unprepared hiring managers.

The cloning trap and how to use it safely

Every manager has a specific person in mind when they open a role. This is usually a former colleague or a high-performing current team member. Ask the manager who they want to clone. Then ask what specific actions that person took that made them effective.

You will get specific operational details you would never have extracted from a standard form. You will learn exactly how this phantom candidate solved problems. However, you must manage the cloning impulse carefully. You will sometimes discover that the mental model is a person from a company ten times your size. The manager might be picturing someone who had massive budget support and a team of analysts.

Your role might offer zero budget and require manual data entry. This is a necessary conversation to have during the intake meeting. It is far better to uncover this misalignment on day one than after four rejected finalists. Force the manager to separate the person from the environment. Ask if the clone would still succeed under your current company constraints. If the answer is no, the requisition is broken. You must adjust the expectations to match your reality.

Force the trade-off

Every requisition requires compromises. Hiring managers rarely volunteer them. You must ask what they are willing to trade away. This is the tactic that ultimately saves a difficult search. Give the manager a forced choice.

Ask if they prefer deep domain knowledge or strong general management ability. Ask if they want someone who has operated at global scale or someone who has built a department from zero. Force them to choose between a fast initial output and a long-term strategic runway. Managers often hate these questions. That reaction is exactly why the mechanism works.

A brief without a defined trade-off produces endless pipelines with zero offers. Candidates will always fail on at least one undocumented criteria. You must establish the primary requirement and the acceptable weaknesses before sourcing begins. You must know what flaws the manager will tolerate. Every candidate has flaws. If the manager demands perfection, you will never fill the role. Get them to verbally agree to the necessary compromises.

Write it down and force a correction

Write these compromises down immediately. Two paragraphs are sufficient. Do not create a massive slide deck. State clearly what the person will do, what matters most, and what the manager agrees to give up. Send this short text back to the manager.

Ask them to correct it rather than approve it. People correct errors more honestly and rigorously than they review approvals. They want to fix your mistakes. Let them. Use this corrected document as the strict baseline for the entire search.

Structured intake documents prevent subjective rejections later in the process. When the manager provides feedback on candidate seven that contradicts the initial brief, you have a baseline to reference. If they reject a candidate for lacking enterprise software experience, but previously agreed to trade that for startup agility, you must highlight the discrepancy. Do this immediately and clearly.

Stalled searches usually mean the target profile shifted without the recruiter knowing. Do not accept a vague rejection as valid feedback. Force the manager to map their rejection to the six-month outcomes you agreed upon. If the requirements truly changed, close the requisition. Open a new one with the updated criteria.

Systematize the intake in your applicant tracking system

You must build these translation steps into your recruitment software. Do not rely on individual recruiters to remember the questions. Configure your Workday or Greenhouse instance to demand objective criteria. Remove the open text fields that encourage managers to write paragraphs of corporate jargon.

Replace them with mandatory fields requiring specific deliverables for the first ninety days. Implement a drop-down menu that forces the hiring manager to select their primary trade-off before they can submit the requisition for financial approval. This shifts the administrative burden back to the business. It forces them to think critically before demanding headcount.

Train your interview panels to grade against these specific deliverables. If the requisition is translated properly, the interview scorecard should write itself. Each interviewer takes one of the required outcomes. They test the candidate solely on their ability to execute that specific task. This eliminates the overlapping, unstructured interviews that frustrate candidates and yield useless feedback.

Aligning the panel to the new reality

The hiring manager is only one part of the problem. The interview panel often operates on an entirely different set of assumptions. If the requisition is vague, every interviewer invents their own version of the job. One person tests for technical depth while another tests for executive presentation skills. The candidate fails because they cannot simultaneously satisfy four contradictory job descriptions.

You must circulate the translated, two-paragraph brief to the entire panel. Do this forty-eight hours before the first interview. Require each panelist to confirm they understand the specific outcomes required. Assign them a single, defined area of investigation tied directly to the six-month calendar goals.

If a panelist provides feedback outside their assigned area, disregard it. If they reject a candidate based on vague feelings about personality, push back. Require them to point to a specific failure in the candidate's ability to deliver the required operational outcomes. This discipline elevates the talent acquisition function. It transforms recruiters from order takers into operational partners.

Calibrate with the first three candidates

Even the most rigorous intake process requires real market validation. You must calibrate the requisition using the first three candidates you source. Present these profiles to the hiring manager within four days of opening the search. Do not wait for a full pipeline. Ask the manager to review these specific resumes against the agreed six-month outcomes. This immediate feedback loop exposes any remaining assumptions.

A manager might look at a highly qualified candidate and reject them for lacking industry specific experience. If industry experience was not in your two paragraph brief, you have uncovered a hidden requirement. You must stop the search immediately. Revise the documentation and adjust the salary band if necessary.

This fast calibration prevents you from spending three weeks sourcing the wrong profile. It forces the manager to face the reality of the talent pool. If the manager rejects all three calibration profiles, the requisition is still too vague. You must return to the forced trade-off questions. Do not proceed with full scale sourcing until the manager can definitively accept at least one calibration profile as a valid target.

Next steps

Audit your current open requisitions older than forty days. Identify any roles where the required six-month outcomes are not explicitly documented. Schedule fifteen-minute reset calls with those hiring managers immediately.

Ask them the forced trade-off questions. If they cannot define the specific technical outputs required, pause the search. Update your intake templates in your applicant tracking system by the end of this month. Remove generic competency checklists and replace them with mandatory fields for week-two deliverables.

Implement a strict rule requiring a designated salary band linked to objective technical criteria before any role goes live. Train your sourcing team to reject intake forms that rely on personality adjectives. Require concrete verbs and measurable business outcomes for every new headcount requested next quarter.