Category: Talent Advisory

  • Applicant Volume Is Not Recruiting Success

    Applicant Volume Is Not Recruiting Success

    In the current job market a large applicant count tells an employer remarkably little.

    Applications can now be generated, distributed, submitted, sorted, and rejected with very little human involvement. Job platforms recommend openings based on profile data. Candidates use saved information, one-click applications, and AI-assisted materials. Employers distribute the same role across multiple channels while automated systems move people into (or out of) the funnel.

    The result is activity at extraordinary scale…But activity is not alignment.

    A role that attracts 800 applicants and produces no credible interviews has not performed well. It has generated volume without producing evidence that the right people understood the opportunity, recognized themselves in it, and wanted to pursue it.

    The question is not, “How many people applied?”

    It is, “What is the applicant volume telling us about the search?”


    High volume may mean the role was poorly defined

    Employers often interpret a large response as proof that a posting reached the market successfully. It may only prove that the posting reached the market broadly.

    If most applicants are unqualified in similar ways, that pattern deserves investigation. The title may be attracting the wrong professional audience. The responsibilities may be broad enough to describe several different jobs. The seniority may be unclear. The compensation, location expectations, reporting relationship, or actual decision-making authority may be missing.

    The description may also fail to distinguish between what is mandatory and what is merely preferred.

    That distinction matters. If a license is legally required, candidates should know it is non-negotiable. If industry experience is useful but transferable experience could work, it should not be presented as an absolute barrier. If the hiring manager wants a particular background but would reconsider it for someone with stronger adjacent capabilities, the description should reflect that reality.

    When every qualification is written with equal emphasis, candidates are forced to decide which requirements the employer genuinely means. Recruiters and screening systems are forced to make the same guess.

    Clarity is not cosmetic. It is part of the search strategy.

    An open posting should represent an active opportunity

    Companies also need better discipline around whether a posted role is actually being hired.

    A position may remain visible after funding has paused, priorities have changed, an internal candidate has emerged, or the hiring team has stopped reviewing applicants. Some roles are posted continuously to collect potential talent rather than fill an immediate vacancy. Others remain online because no one has taken responsibility for closing them.

    Those distinctions are largely invisible to the candidate.

    The damage extends beyond the abandoned application. A person may apply for a role that is reasonably aligned, receive no meaningful response, and conclude that the company does not review applications or that its postings cannot be trusted.

    When the company later advertises a position for which that same person is an exceptional match, the earlier silence becomes part of the recruiting process. The candidate may ignore the role, assume it is not active, or decide that engaging with the organization is not worth repeating.

    An inactive posting does not simply waste today’s applications. It can suppress tomorrow’s best ones.

    If an organization wants to build a future talent pool, it should say so. A talent community, expression-of-interest page, or clearly identified evergreen pipeline is different from presenting a hypothetical need as an active vacancy.

    A profile, an applicant, and a candidate are not the same thing

    Modern recruiting systems make it easy to surface profiles. That convenience has blurred an important distinction.

    A profile is someone whose background appears potentially relevant.

    An applicant is someone who has expressed interest by applying.

    A candidate is someone whose background has been evaluated, who understands the opportunity, and whose interest has been confirmed.

    These terms should not be treated as interchangeable.

    This is especially important when an employer works with a recruiter or sourcer. Finding a resume in a database and forwarding it to a client is not candidate presentation. The person may not know about the role. They may not be interested. Their compensation, location, availability, or career objectives may make the opportunity impossible. The resume may also be outdated.

    Presenting someone as a candidate without having contacted them transfers the actual recruiting work back to the employer while creating the appearance that sourcing has occurred.

    If a recruiter submits fifteen or twenty people at once for a professional role, that volume should raise questions. Either the recruiter has not been given enough information to exercise judgment, is not paying close attention to the requirements, or has not conducted a meaningful screen.

    A hiring team does not need another delivery mechanism for search results. It needs informed judgment before its time (and the candidate’s) is consumed.

    Recruiter calibration must happen before sourcing begins

    A recruiter cannot identify qualified candidates when the hiring team has not agreed on what qualified means.

    The recruiter needs more than a job description. They need to understand the business problem behind the hire, the capabilities required to address it, the experiences that could transfer, and the reasons an otherwise impressive person would not succeed in the role.

    They also need to know where the organization has flexibility.

    Which qualifications are truly mandatory? Which are evidence of a capability that could be demonstrated another way? What would make the hiring manager consider someone outside the expected industry, title progression, or educational background? What did the previous person lack? What must the next person do differently?

    Without those answers, sourcing becomes an expensive calibration exercise conducted through human beings. Recruiters send profiles, hiring managers react to them, and the definition of the role changes after each batch.

    A strong search begins with enough shared understanding that the recruiter can explain not only why someone appears qualified, but why this person is worth the hiring team’s attention.

    A long-open role should trigger diagnosis, not another repost

    Some searches are legitimately difficult. The talent may be scarce, the geography restrictive, or the competition intense.

    But if a role has been open for months without producing a single qualified interview, “there are no good candidates” is not an adequate diagnosis.

    The search itself is the first place to look.

    Where is the process failing?

    • If the role receives impressions but few applications, the title, compensation, employer reputation, or basic proposition may not be competitive.
    • If it receives many applications but almost no qualified ones, the description, targeting, distribution, or requirements are probably misaligned.
    • If recruiters conduct numerous screens but advance very few people, the sourcing criteria or recruiter calibration may be wrong.
    • If qualified candidates interview but no one is selected, the decision-makers may not agree on what they want—or the interview process may not be producing useful evidence.
    • If offers are extended but repeatedly declined, compensation, speed, leadership, flexibility, or candidate trust may be the actual problem.

    Reposting the same description resets the date. It does not repair the search.

    A chronically open role is not merely a recruiting inconvenience. It is operational data. The organization should be able to identify which stage is failing and change the conditions producing that failure.

    Distribution should be designed for the people the company needs

    Posting everywhere is not the same thing as recruiting strategically.

    Broad job boards can be appropriate for some roles. Others require targeted professional communities, direct outreach, referrals, industry associations, alumni networks, geographic partnerships, or recruiters with access to people who are not actively applying.

    The channel should follow the talent market.

    Employers should also distinguish between visibility and interest. A posting may attract large numbers of low-intent applications because it is widely recommended, unusually easy to apply to, or titled in a way that catches a broad audience. None of those conditions establishes that the role is compelling to the people most capable of doing it.

    The relevant question is not where the company can generate the most applications. It is where qualified people are likely to encounter the opportunity, understand its value, and take it seriously.

    Measure the quality of movement, not the amount of traffic

    Applicant volume is a marketing metric. Recruiting success requires more.

    A useful recruiting dashboard should reveal:

    • Which sources produce qualified applicants rather than raw applications
    • How many applicants become credible screens
    • How many screens produce interviews
    • Whether interviewers agree on what they are evaluating
    • How quickly viable candidates receive human contact
    • Where strong candidates withdraw
    • Why offers are accepted or declined
    • Whether previously engaged candidates return for future roles

    These measures show whether the process is creating informed movement toward a hire. A total application count does not.

    The objective is not to fill the top of the funnel until the organization can no longer see through it. It is to design a search precise enough to attract credible possibilities, responsive enough to preserve their interest, and disciplined enough to recognize when the problem is not the candidates.

    Sometimes 500 applications indicate extraordinary market interest.

    Sometimes they indicate that the organization has asked the market an unclear question, and received 500 different interpretations.

    By Melissa Brandt  |  Melissa Brandt & Associates

  • What a Good Interview Should Actually Accomplish

    What a Good Interview Should Actually Accomplish

    The purpose is not to perform a familiar set of questions. It is to determine what this candidate could solve, and whether the opportunity makes sense for both sides.

    A candidate joins a video interview. On the interviewer’s screen are an applicant-tracking profile, the submitted résumé, recruiter notes, LinkedIn history, and perhaps an automated summary of the candidate’s background.

    The organization has access to more information than hiring teams could have imagined a generation ago. And yet the conversation begins: “Tell me a little about yourself.”

    The problem is not that this is always a bad opening question. It is that the interviewer frequently has no plan for what should follow. They move through standardized prompts, record fragments of the answers in the hiring platform, and complete an evaluation form after the call. The process is structured, documented, and technologically supported, but may still reveal little that was not available before the interview began.

    A strong interview is not defined by the platform hosting it, the scorecard attached to it, or whether every required question was asked. It is a prepared, responsive inquiry designed to determine whether this candidate can succeed in this role, within this organization, under the conditions that actually exist.

    More importantly, it should determine what this particular person may be able to solve.

    Every position exists because an organization has work that needs to be done, problems that need to be addressed, or opportunities it is not yet equipped to pursue. The job description may define the general territory, but the interview should explore the potential match between the organization’s needs and the candidate’s particular capabilities.

    What has this person encountered before that resembles the conditions here? What do they understand that the organization currently lacks? Which problems could they approach differently? Where might they strengthen the role rather than merely occupy it?

    That makes the interview a process of mutual discovery. The organization is learning what the candidate could contribute, while the candidate is deciding whether the role, leadership, resources, and business conditions would allow that contribution to matter. Both parties arrived because there was enough interest to begin a conversation. The interview should determine whether that interest can become a credible working proposition.


    Ten goals for a useful interview

    1. Define what the organization needs someone to solve

    Before evaluating a candidate, the interviewer must understand why the role exists now. What is not working? What needs to change? Which opportunities are being missed? What must the person accomplish that the organization cannot accomplish (or is not accomplishing) without them?

    Without that clarity, the interview collapses into qualification matching. The hiring team asks whether the candidate has held similar titles, used familiar systems, or completed comparable tasks without determining whether that experience equips them to address the organization’s actual needs. The job description provides boundaries. The business problem provides the reason for the conversation.

    2. Enter with a roadmap, not a script

    The resume, job description, recruiter notes, work samples, and earlier conversations should shape a preliminary view of the candidate before the interview begins. What appears especially relevant? What remains unclear? Where does the candidate’s experience align, and where does that alignment need to be tested?

    Preparation does not mean deciding in advance. It means entering the conversation knowing what evidence is still needed.

    3. Use the resume to find the story behind the record

    A resume documents roles, dates, responsibilities, and selected accomplishments. The interview should uncover the context those facts cannot provide. What was happening inside the organization? What problem was the candidate brought in to solve? What authority and resources did they actually have? Which outcomes belonged to them, and which were the result of a larger team?

    The objective is not to repeat the resume aloud. It is to understand what the resume means.

    4. Follow the answer, not merely the question list

    A prepared interviewer should have a roadmap, but a productive conversation will not always follow it in order. An unexpected comment may reveal more than the next scheduled question.

    Good interviewers listen for what deserves another question. They ask for clarification, test inconsistencies, and pursue details that change their understanding of the candidate. A rigid script can create consistency, but it can also cause the interviewer to miss the most valuable evidence offered during the conversation.

    5. Replace polished claims with specific evidence

    Candidates know they are expected to describe themselves as strategic, collaborative, adaptable, and results-oriented. Asking whether they possess those qualities rarely produces useful information.

    Ask where those qualities became necessary. What decision did they make? What alternatives did they consider? Who disagreed? What changed because of their involvement? The goal is not to collect the correct vocabulary. It is to understand how the candidate operates when the quality being discussed is actually required.

    6. Separate interview fluency from job capability

    Some candidates are exceptionally skilled at interviewing. Others are more compelling when discussing real work than when delivering polished answers to anticipated questions.

    Unless presentation under interview-like conditions is central to the role, conversational polish should not become a substitute for capability. The interviewer must distinguish between someone who presents a persuasive account of competence and someone whose experience demonstrates it.

    7. Examine judgment, not just outcomes

    A successful result does not automatically prove that the decisions behind it were sound. Nor does an unsuccessful result necessarily indicate poor judgment.

    A useful interview explores what the candidate knew at the time, which constraints shaped the decision, what risks they recognized, and what they would do differently now. This shows how the person thinks, adapts, and learns when circumstances are imperfect.

    8. Explore what this particular candidate could make possible

    Candidates who satisfy the same basic requirements are not interchangeable. Each brings a different combination of experience, judgment, relationships, ideas, and ways of approaching the work.

    A strong interview considers more than whether the candidate can perform the role as currently defined. It asks which problems this person may be especially equipped to solve, where they could improve the role, and what capabilities they might introduce that the organization had not originally considered. Sometimes the strongest candidate is not the person who most precisely resembles the previous employee. It is the person who offers the most credible response to what the organization needs next.

    9. Make the operating reality part of the conversation

    Every role operates within conditions that may not appear in the job description: unclear authority, competing stakeholders, limited resources, organizational resistance, inherited problems, or a manager with a particular working style.

    Those conditions should be discussed directly. The candidate’s questions, interpretations, and challenges are evidence too. What do they notice? Which assumptions do they test? What risks do they identify? The organization is not simply deciding whether it wants the candidate; the candidate is deciding whether the organization offers a credible opportunity to do the work.

    10. Leave with evidence that can support a decision

    “Strong candidate,” “good energy,” and “not sure about fit” are reactions, not findings. By the end of the interview, the interviewer should be able to identify what was learned, which examples support the assessment, what remains unresolved, and whether another conversation would produce genuinely new information.

    If several people are involved, each should have a defined area to evaluate and a reason for being there. More interviewers do not automatically produce more knowledge. The process becomes useful only when each conversation contributes distinct evidence to the decision.


    The interview should change what the organization knows

    A good interview does not need to eliminate every uncertainty. It should replace broad assumptions with better evidence, reveal what the candidate could solve, and clarify whether the organization can offer the conditions that person would need to succeed.

    If the hiring team leaves knowing nothing that could not have been learned from the application, the interview did not accomplish its purpose. It was performed, recorded, and completed, but it did not meaningfully advance the decision.

    The measure of a strong interview is not how many questions were asked. It is whether both sides now understand the possibility in front of them more clearly.

    By Melissa Brandt  |  Melissa Brandt & Associates

  • A Five-Interview Process Is Not Evidence of Rigor

    A Five-Interview Process Is Not Evidence of Rigor

    A candidate speaks with the recruiter, the hiring manager, a department leader, a panel of prospective colleagues, and finally an executive who was added late in the process.

    By the fifth conversation, the candidate has explained the same career transition three times, offered the same examples of leadership and problem-solving, and asked increasingly creative versions of the same questions. The interviewers do not appear to know what was discussed in earlier rounds. Several describe the role differently.

    The company may believe it is being thorough.

    The candidate may reasonably conclude that the company does not know how to make a decision.

    More interviews do not automatically produce better evidence

    Some positions legitimately require several conversations. A C-suite executive, board-facing leader, confidential hire, or person entering an unusually complex cross-functional role may need to meet multiple stakeholders. Even then, each conversation should serve a distinct purpose.

    The problem is not the number five itself. It is a process in which five interviews repeatedly evaluate the same qualities because no one has designed a coherent way to reach a decision.

    Additional evidence can improve a hiring decision. Repeated exposure to the same candidate is not necessarily additional evidence.

    If the recruiter, hiring manager, department head, and executive all independently ask the candidate to “walk me through your background,” the organization has not created four layers of rigor. It has recreated the first interview four times.

    What an excessive interview process may reveal

    A prolonged process often points to problems that began before the candidate entered it.

    The role may not have been defined clearly. Interviewers may disagree about which capabilities matter most or even what the person will be expected to accomplish. One leader may view the position as operational while another expects it to drive transformation. Additional interviews are then used to search for agreement that should have existed before recruitment began.

    The process may also reflect unclear decision authority. A hiring manager ostensibly owns the role but cannot make the hire without informal approval from several colleagues. Stakeholders are added because excluding them feels politically risky, not because they have something specific to assess.

    In other cases, decision-makers simply do not trust one another’s judgment. Each person wants individual access to the candidate rather than relying on a structured evaluation completed by someone else.

    More interviews can create the appearance of diligence while allowing the organization to postpone uncertainty. Instead of deciding which evidence is sufficient, it asks for another meeting.

    That is not rigor. It is risk aversion without process discipline.

    The candidate is paying for the indecision

    Every additional round has a cost.

    Candidates may need to rearrange work, invent explanations for repeated absences, coordinate childcare, prepare new materials, or protect the confidentiality of a search from their current employer. They continue investing time and emotional energy without necessarily learning anything new about the opportunity.

    Strong candidates are often participating in other processes. A company that adds stages without warning or leaves long gaps between them may lose the candidate it was trying so carefully to evaluate.

    The experience also communicates something about the organization. When interviewers repeat the same questions, contradict one another, or appear unaware of what has already occurred, candidates are given a preview of how information and authority may function after they are hired.

    A needlessly complicated interview process does not merely inconvenience candidates. It can cause the most discerning ones to withdraw.

    What a disciplined process looks like

    A rigorous interview process does not have to be short, but it should be designed.

    Each stage should have:

    • A defined purpose
    • Specific competencies or evidence to evaluate
    • Interviewers selected for a clear reason
    • Questions that do not unnecessarily duplicate earlier rounds
    • A shared method for recording and comparing observations
    • A decision-maker with actual authority
    • A timeline communicated to candidates in advance

    Multiple stakeholders do not always require multiple appointments. A structured panel can allow several people to participate while reducing repetition and giving everyone access to the same evidence.

    Interviewers should also know what has already been assessed. That does not mean sharing another interviewer’s conclusions before they form their own. It means understanding their assignment. One interviewer might evaluate technical depth, another cross-functional influence, and another management judgment. Their findings can then be considered together.

    The objective is not to see how many people like the candidate. It is to collect enough relevant evidence to determine whether that person can perform the work.

    Candidates are entitled to understand the process

    Candidates can reasonably ask early in the process:

    • How many stages are anticipated?
    • Who will participate?
    • What is each stage intended to evaluate?
    • Who makes the final decision?
    • What is the expected timeline?

    A clear answer suggests that the organization has designed the process deliberately. A vague or continuously changing answer is useful information too.

    Not every position can be evaluated in two conversations, and speed alone does not make a hiring process effective. But complexity should come from the demands of the role—not from internal confusion about the decision.

    If an organization cannot explain what the fifth interview will reveal that the first four did not, it probably does not need a fifth interview.

    By Melissa Brandt  |  Melissa Brandt & Associates

  • When a Vacancy Calls for More Than a Replacement

    When a Vacancy Calls for More Than a Replacement


    Rethinking the Work Before Beginning the Search

    A position opens, and someone retrieves the last job description.

    The document is revised, circulated among stakeholders, and expanded to reflect everything the organization hopes the next employee might accomplish. New responsibilities are added. Old requirements remain because no one is certain whether they can safely be removed. Preferred credentials become mandatory. The experience of the previous incumbent quietly becomes the model for the next one.

    By the time the role reaches the market, the organization appears to have defined what it needs.

    Often, it has only produced a more polished description of what it already knows.

    A job description can document reporting relationships, responsibilities, qualifications, and compensation classification. What it cannot do automatically is determine whether those elements still reflect the work the organization needs performed. Yet once the document is approved, it begins governing the entire hiring process: recruiters source against it, screening systems filter for it, interviewers evaluate candidates through it, and qualified people are rejected for failing to resemble the theory of the role embedded within it.

    The result is a peculiar form of precision. An organization can run a disciplined, consistent, carefully documented search for the wrong person.


    A vacancy is information, not merely an instruction to replace

    When someone leaves, the default organizational response is usually replacement. The title existed, the budget existed, and the work must go somewhere. Opening the requisition feels like the practical next step.

    But a vacancy is also one of the few moments when an organization can examine a role without being constrained by the person currently occupying it. Before asking who should fill the position, leaders should ask what the departure reveals.

    What work had the role actually come to include? Which responsibilities had quietly migrated elsewhere? What remained undone? Where did the employee struggle because the role was poorly designed, under-resourced, or internally contradictory? Which contributions proved unusually valuable even though they never appeared in the official description? And has the business changed enough that replacing the same title would preserve a structure that no longer serves it?

    Exit interviews can be unusually valuable here, provided they are treated as operational evidence rather than a final administrative ritual. A departing employee may be able to identify competing priorities, missing authority, repetitive bottlenecks, invisible labor, or responsibilities that could be redistributed more sensibly. That account should not be accepted uncritically, but neither should it disappear into a file after the employee leaves.

    The correct outcome of vacancy analysis is not always a replacement. It may be an internal promotion, a redesigned role, two narrower roles, a shift in reporting relationships, investment in a different capability, or a decision that the old position is no longer necessary. Automatically refilling the position answers the easiest question—who replaces this person—before the organization has asked the more important one: what does the business need now?

    The people closest to the work are often missing from the analysis

    Job descriptions are frequently written by people who do not encounter the role’s daily reality. Human resources may own the document. A department head may approve it. A senior leader may add strategic expectations. Each may understand part of the position, but none necessarily sees how work reaches the role, where it stalls, which relationships make it possible, or what colleagues have learned to compensate for.

    Organizations nevertheless often begin with existing documentation and performance data rather than interviewing the people who possess the richest operational knowledge: current employees.

    That inquiry should extend beyond anyone who holds the same title. It should include the manager, peers, direct reports, internal clients, and people performing adjacent work. Those employees can identify where handoffs fail, which capabilities are genuinely scarce, what the written process omits, and which parts of the job require judgment rather than procedural compliance.

    They can also expose two different kinds of blind spot. The first is where the previous employee had room to improve the role: work that was routinely delayed, relationships that remained weak, or capabilities the organization needed but never received. The second is where the previous employee expanded the role through strengths that were never formally recognized. Perhaps that person translated effectively between technical and commercial teams, stabilized a difficult client relationship, mentored junior employees, or saw emerging risks earlier than others. If those contributions mattered, the organization must decide whether they belong in the redesigned role—not simply lose them because they were absent from the old document.

    This is the practical purpose of job analysis. The U.S. Office of Personnel Management describes it as examining the tasks performed, the competencies required to perform them, and the relationship between the two. The relevant knowledge comes from people with direct, current experience of the work. The job description should be an output of that inquiry, not its starting assumption.

    The incumbent is evidence, not the template

    The person who previously held a role inevitably shapes how the organization understands it. Their strengths become associated with the position. Their limitations may cause work to move elsewhere. Their background begins to look like the natural route into the job.

    That history is useful, but it is not a neutral specification.

    Hiring in the image of a successful predecessor can preserve valuable capability. It can also prevent the organization from seeing how the role should evolve. Hiring against an unsuccessful predecessor creates the opposite danger: the search becomes an exercise in finding someone unlike the last person, even when the problem involved unclear authority, conflicting expectations, weak management, or an impossible span of responsibility.

    In either case, the organization risks confusing a person’s performance with the design of the role itself.

    A better review separates four questions: What did the previous employee do? What should the role have required? What does the organization need next? And which conditions must exist for the next person to succeed? Those answers may overlap, but they should never be assumed to be identical.

    The organization must look beside the vacancy, not only into it

    Roles do not operate as isolated boxes on an organizational chart. Work crosses boundaries, accumulates in informal places, and changes as technology, customers, regulations, strategy, and team capability change. A vacancy therefore cannot be understood by examining only the empty box.

    Leaders should look at adjacent roles before authorizing a replacement. Has another employee already developed the capability to assume the work? Is that person performing much of it without the title, authority, or compensation? Could responsibilities be redistributed in a way that creates a legitimate internal advancement opportunity? Have two roles evolved toward substantial overlap? Is the vacancy revealing a missing capability elsewhere rather than a need to recreate the departed position?

    This wider view can uncover internal candidates who would be invisible in an external search. It can also prevent a common organizational mistake: hiring externally for a role that an existing employee is already demonstrating the capacity to perform, while leaving that employee responsible for training the newcomer.

    Internal hiring is not automatically the correct answer. Moving work among existing employees can become disguised understaffing, and promotions should not be offered without appropriate authority, compensation, and support. The point is not to avoid external recruitment. It is to understand the system before deciding which intervention it requires.

    A title is not cosmetic in an algorithmic labor market

    Even when the work has been defined correctly, the wrong title can sabotage the search.

    Titles have always communicated level, function, and professional identity. Today they also act as discovery infrastructure. Job boards, search engines, recruiting platforms, and recommendation systems use titles and profile histories to decide which opportunities candidates see and which candidates recruiters are shown. A title that is idiosyncratic, inflated, outdated, or misaligned with the market can route the opportunity toward the wrong audience before anyone reads the description.

    This matters especially when internal language differs from external convention. A title that makes perfect sense inside one company may describe a different function everywhere else. Conversely, retaining a familiar title because “that is what the role has always been called” may conceal that the job has moved into a new discipline, level, or scope.

    Choosing a title therefore requires both internal and external analysis. Internally, it should represent the role’s authority, accountability, and relationship to adjacent positions. Externally, it should use language that qualified people recognize and that modern search and recommendation systems can interpret accurately. The title is not merely the label placed on a finished job description. It is one of the mechanisms that determines who encounters the opportunity at all.

    A grocery list of skills is not a theory of success

    Many job descriptions become inventories of qualifications: a degree, a number of years, industry experience, software familiarity, communication skills, strategic thinking, leadership, and an assortment of preferred attributes. The longer the list, the more rigorous the role appears.

    But a list of skills does not explain what the person is being hired to change.

    The better starting point is the business problem. What is currently happening that must improve? What outcomes should exist after six months or a year? Which obstacles are technical, which are structural, and which depend on relationships or influence? What must the person know upon entry, and what can a capable person learn?

    This distinction matters because capability is contextual. The candidate who satisfies every visible requirement may still be poorly suited to the actual environment. A person can possess the nominal communication skill while being unable to build trust with this team, translate between these stakeholders, or deliver unwelcome information to this leadership group. Another candidate may lack one preferred credential while possessing precisely the judgment, adaptability, and credibility the situation requires.

    That does not justify returning to intuition, chemistry, or an undefined notion of culture fit. Communication and interpersonal requirements should be made more specific, not less. Does the role require resolving conflict between technical and commercial teams? Influencing leaders without formal authority? Communicating risk to a skeptical board? Managing people through substantial change? Those are assessable demands. “Excellent communication skills” is mostly a phrase.

    Hiring is not improved by abandoning requirements. It is improved by tracing requirements back to the work.


    Selection rigor cannot rescue an inaccurate role

    The consequences of a weak job definition extend through every stage of hiring.

    Recruiters search for the wrong profile. Applicant-tracking systems filter against outdated language. Interviewers ask structured questions about competencies that are no longer central. Assessments measure what the document says rather than what the work requires. Compensation is benchmarked against a title that may not describe the actual scope. Candidates receive conflicting accounts of the position because stakeholders never resolved their differences before the search began.

    The process can still look exemplary. It can be standardized, documented, efficient, and consistent. None of those qualities establishes that the organization is measuring the right things.

    Employment-selection guidance reflects this connection. The Equal Employment Opportunity Commission advises employers to ensure that selection procedures are job-related, properly validated for their intended positions and purposes, and updated when job requirements change. A hiring method cannot be meaningfully job-related if the employer is working from an obsolete or inaccurate account of the job.

    Technology magnifies the consequence. The more efficiently a platform matches candidates to a faulty description, the faster the organization excludes people who could solve the real problem. Artificial intelligence may improve drafting, sourcing, matching, or assessment, but it cannot decide which inherited assumptions deserve to survive. If the organization gives it the wrong theory of the role, it can operationalize that theory at scale.

    Define the work before defining the candidate

    A useful job description should be the final expression of a discovery process. Before drafting it, the organization should be able to answer several questions:

    • Why does this role need to exist now?
    • What business problem or opportunity is it expected to address?
    • What outcomes should the person produce in the first six to twelve months?
    • What work is actually essential to those outcomes?
    • What has changed since the role was last filled?
    • What did the previous employee contribute that the document failed to capture?
    • Where did the role, its design, or its surrounding system create preventable difficulty?
    • What do the manager, peers, direct reports, and internal clients know about the work?
    • Could an internal employee assume the role with appropriate development, authority, and compensation?
    • Should adjacent roles or reporting relationships change before the vacancy is filled?
    • Which capabilities must exist on entry, and which can be learned?
    • Which credentials are genuinely necessary, and which are merely familiar proxies?
    • What title will accurately communicate the work to both people and algorithmic systems?

    Only after those questions have been answered does it make sense to describe the candidate. Even then, the goal is not to imagine a flawless person. It is to identify the evidence that would demonstrate an ability to perform the work in this environment.

    The distinction is consequential. When organizations begin with the candidate profile, they tend to reproduce prior patterns: the same titles, backgrounds, credentials, and industries. When they begin with the work and its intended outcomes, they create room to recognize transferable capability, unconventional experience, and internal potential.

    The job description should describe a decision the organization has actually made

    A job description cannot compensate for unresolved strategy. If leaders disagree about the role’s priorities, authority, level, resources, or definition of success, polishing the language will not make the job coherent. It will merely transfer the ambiguity to recruiters and candidates.

    The strongest candidates often detect that ambiguity quickly. They ask which problem takes priority, who owns the decision, why the previous person left, how success will be measured, and whether the resources match the expectations. Their questions may appear challenging because they expose decisions the organization has postponed. That challenge can itself be valuable evidence—particularly in executive, transformation, turnaround, and newly created roles, where the person hired may need to revise the organization’s original understanding of the problem.

    The job description is not the job. It is a claim about the job: what matters, what success requires, and why a particular combination of work belongs together. Before using that claim to attract, screen, assess, and reject people, an organization should know how it arrived there.

    Otherwise, it may spend months searching for the perfect candidate to fill a role that exists only on paper.


    Sources

    U.S. Office of Personnel Management, “Job Analysis.” https://www.opm.gov/policy-data-oversight/assessment-and-selection/job-analysis/

    U.S. Office of Personnel Management, “Assessment and Selection.” https://www.opm.gov/policy-data-oversight/assessment-and-selection/

    U.S. Equal Employment Opportunity Commission, “Employment Tests and Selection Procedures.” https://www.eeoc.gov/laws/guidance/employment-tests-and-selection-procedures

    U.S. Department of Labor, O*NET. https://www.dol.gov/agencies/eta/onet

    By Melissa Brandt  |  Melissa Brandt & Associates

  • The First Wall

    The First Wall

    Efficiency, bias, and the hidden false-negative problem in automated hiring


    AI can support hiring without being entitled to decide who receives human consideration.

    What happens when the first person to evaluate a candidate is not a person at all?

    Employers are increasingly using automated assessments to screen applicants before a recruiter or hiring manager becomes involved. These systems may evaluate recorded interviews, written responses, games, simulations, technical exercises, and behavioral assessments and then help determine who advances.

    The appeal is easy to understand. Automation promises speed, consistency, lower costs, and relief for recruiting teams overwhelmed by application volume. Every candidate can receive the same assessment, and thousands of results can be processed quickly. The process also produces something organizations find particularly persuasive: a score that appears objective.

    But a standardized score is not the same thing as an objective judgment. Every automated assessment begins with human decisions about which qualities matter, how those qualities should be measured, and what successful performance looks like. The system then introduces another layer of risk through the data, correlations, proxies, and probabilistic inferences it uses to evaluate candidates. It can inherit human assumptions and biases, generate errors of its own, compound the two, and apply the result consistently at scale.

    At each stage, uncertainty is converted into something that looks increasingly like fact. The greatest risk is not simply that the system might make a mistake. It is that qualified or exceptional candidates may be eliminated before anyone encounters them—and the organization may never acquire the evidence needed to discover what it missed.


    Why the first wall matters

    AI can reduce administrative burden through scheduling, workflow management, and information organization. Once candidate evidence exists, it can summarize structured interviews, map examples against a rubric, identify inconsistencies for human review, evaluate direct demonstrations of technical skill, and help recruiters compare large amounts of information. In those uses, a responsible person can examine both the evidence and the system’s interpretation of it. The ethical balance changes when the system controls who receives that human review, because an error at that stage can remove a candidate before anyone has the opportunity to recognize it.

    Asynchronous video assessment introduces an additional limitation by removing the interaction that makes a skilled interview informative. A recruiter can follow an unexpected answer, distinguish nervousness from lack of competence, clarify an apparent contradiction, or discover that the original job specification is wrong. An automated assessment evaluates the candidate against assumptions established in advance. It cannot question those assumptions or negotiate meaning with the candidate.

    These limitations matter most in executive, confidential, scarce-talent, succession, turnaround, and transformation searches. In those settings, evaluation and recruitment occur simultaneously. The strongest prospect may not be an applicant, may refuse an impersonal audition, or may understand the business problem differently from the organization that designed the assessment. That difference may be precisely the value the company needs.

    The validation loop has a missing half

    Once the system is in use, the employer can compare assessment scores with the performance of candidates who advanced and were ultimately hired. It cannot make the same comparison for rejected candidates because they never entered the organization and generated no performance data.

    That distinction matters. Evidence that high-scoring candidates sometimes become successful employees does not prove that low-scoring candidates would have failed or that the system identified the best available talent. Because the assessment determines who becomes available for later measurement, it also shapes the evidence used to validate itself.

    The system may therefore prevent the organization from collecting the very information that would reveal its false negatives.

    If the system favors candidates who perform well in solitary recorded auditions, the company hires more of them and acquires more evidence about them. Candidates who think brilliantly in dialogue but speak awkwardly to a camera disappear from the dataset. The loop can become self-confirming.

    Even the observed performance data are filtered through offer acceptance, manager quality, assignment distribution, early turnover, subjective ratings, and promotion politics. A model can end up optimizing for the organization’s existing definition of success while leadership believes it is identifying talent objectively.

    Consistency may not equal fairness

    Standardized questions and job-related scoring rubrics can improve a hiring process vulnerable to affinity bias, fatigue, intuition, and irrelevant impressions. But repeatability proves only that the same method was applied. It does not establish that the method is fair or that it measures the right things.

    Bias can enter through the definition of success itself. If a model is developed around employees the organization already considers successful, it may learn patterns influenced by who received the best assignments, strongest sponsorship, most valuable territories, or greatest access to promotion. Historical performance data do not arrive morally neutral. They contain the history of the organization that produced them.

    Automating those patterns does not neutralize them. It can make them more difficult to see and easier to apply consistently at scale.

    The transcription problem comes first

    Anyone who regularly uses voice-to-text knows that clear speech does not guarantee an accurate transcript. Proper names disappear, familiar words become unrelated ones, and regional pronunciations become statements the speaker never made. In a text message, that is inconvenient. In a scored employment assessment, it can alter the evidence used to evaluate a candidate.

    Consider someone with a pronounced Boston accent, a Southern dialect, a speech disability, an unfamiliar cadence, or English as an additional language. If the transcription is inaccurate, the assessment may analyze words the candidate never said. Even if every word is captured correctly, another question remains: Is the candidate’s linguistic style genuinely related to job performance, or is it simply different from the speech most heavily represented in the system’s development and validation data?

    Evidence suggests that these errors have not affected all speakers equally. In a 2020 peer-reviewed study of systems developed by Amazon, Apple, Google, IBM, and Microsoft, researchers found an average word error rate of 35 percent for Black speakers, compared with 19 percent for white speakers. Error rates also varied by location and were positively correlated with the density of African American Vernacular English features in the speech samples. Some systems have improved since the study was conducted, but progress has not been uniform, and employers may still be using older or insufficiently tested technology. When a transcript becomes the basis for a candidate score, uneven transcription error becomes an employment-selection risk.


    Do not confuse probabilistic inference with knowledge of human potential. The system’s most dangerous error may be the candidate it rejects so early that the organization never learns what it lost.

    This does not mean that all AI-enabled hiring tools present the same concerns. A representative technical exercise is fundamentally different from a system that attempts to infer empathy, initiative, judgment, or leadership potential from language or behavior. Platforms that exclude facial recognition or have discontinued facial analysis have removed important sources of risk, but questions involving transcription, competency design, proxies, scoring thresholds, validation, and human oversight remain.

    The relevant question is not simply whether an employer uses AI. It is whether a particular tool, used for a particular role and decision, measures something sufficiently job-related to justify the authority it has been given.

    The law recognizes risk, but compliance is not proof of wisdom

    Federal employment law does not contain an AI exception. The Equal Employment Opportunity Commission has made clear that an employer’s use of AI can violate Title VII when a seemingly neutral practice produces unjustifiable disparate impact. The Americans with Disabilities Act creates additional concerns when a tool screens out qualified people with disabilities, fails to provide reasonable accommodation, or elicits disability-related information.

    State and local regulation is developing as a patchwork:

    Illinois. The Artificial Intelligence Video Interview Act requires notice, an explanation of how the technology works and what it evaluates, and applicant consent before AI analyzes a video interview. It also provides deletion rights and requires demographic reporting when an employer relies solely on AI analysis to determine who receives an in-person interview. Since January 1, 2026, the Illinois Human Rights Act has also prohibited discriminatory employment uses of AI and required notice of covered uses.

    New York City. Local Law 144 requires covered automated employment decision tools to undergo an independent bias audit, publication of audit information, and advance candidate notice.

    Maryland. Employers must obtain written consent before using facial-recognition technology to create a facial template during an employment interview.

    California. Employment regulations effective October 1, 2025 clarify that automated decision systems can violate the Fair Employment and Housing Act, require covered automated-decision records to be retained for at least four years, and address disability-related inquiries. Separate privacy regulations establish additional automated-decision requirements on a phased schedule.

    Colorado. Beginning January 1, 2027, covered automated systems used in consequential decisions, including employment, will be subject to disclosure and recordkeeping requirements, rights to correct inaccurate personal data, and an opportunity to request meaningful human review following an adverse outcome.

    These protections matter, but a bias audit, disclosure, or consent form is not a certificate of truth. A system may produce similar selection rates across demographic groups while rejecting excellent candidates from every group because it measures conformity more effectively than potential. Nondiscriminatory, statistically valid, and strategically wise are three different standards.

    The employer remains responsible for how the technology is deployed: which competencies are measured, how results are weighted, where cutoffs are set, whether accommodations and human review are meaningful, and whether the tool is appropriate for the role. Purchasing a validated product does not make every use of it valid.


    A more defensible standard

    Organizations do not need to choose between rejecting AI and surrendering judgment to it. A responsible system begins with job analysis, favors direct demonstrations of work over inferred personality, validates the full selection process for the actual role and population, tests transcription quality across relevant speech groups, provides an accessible alternative, and preserves meaningful human review before rejection.

    It also examines false negatives deliberately. That may require independent human review of randomized rejected responses, parallel scoring in which the model does not control advancement, monitoring each selection stage for adverse impact, and tracking whether automation actually improves quality of hire rather than merely reducing recruiter time.

    Those safeguards may reduce some of the promised efficiency. That is not evidence that they are excessive. It is evidence that consequential judgment was never costless.

    The question is not whether AI belongs in hiring. It already does, and it can improve poorly structured processes. The question is what authority it should be granted.

    Use AI where the evidence is direct, the method is demonstrably job-related, limitations are disclosed, candidates can request accommodation or correction, and a person remains accountable for the decision. Use it to organize information, reduce administrative burden, strengthen consistency, and surface questions worth investigating.

    Sources and further reading

    1. Koenecke et al., “Racial disparities in automated speech recognition,” PNAS (2020).

    2. U.S. EEOC, “What is the EEOC’s role in AI?”

    3. U.S. EEOC and Department of Justice, disability discrimination and AI hiring guidance.

    4. Illinois Artificial Intelligence Video Interview Act.

    5. Illinois Human Rights Act, Public Act 103-0804.

    6. New York City Department of Consumer and Worker Protection, Automated Employment Decision Tools.

    7. Maryland HB 1202, Chapter 446.

    8. California Civil Rights Department, employment regulations addressing automated decision systems.

    9. California Privacy Protection Agency, Automated Decisionmaking Technology regulations.

    10. Colorado Attorney General, Colorado Anti-Discrimination in AI Law rulemaking.

    This article provides general information about hiring practice and regulatory developments; it is not legal advice.

    By Melissa Brandt  |  Melissa Brandt & Associates

  • Beyond Filling Roles: Why Strategic Talent Advisory Matters

    Beyond Filling Roles: Why Strategic Talent Advisory Matters

    Hiring decisions begin before the search

    When a position opens, the immediate question is often: How quickly can it be filled?

    Sometimes speed is critical. But before an organization begins searching for candidates, it must determine whether it is searching for the right person, for the right role, under the right assumptions.

    Has the work changed since the position was last filled? Does the existing job description reflect what the organization needs now? Could an internal employee be ready to step into the role? Are the expectations realistic, the reporting relationships sound, and the measures of success clear?

    These are not merely recruiting questions. They are business questions—and the quality of the answers shapes every decision that follows.

    Beyond traditional recruiting

    Traditional recruiting generally begins with an approved position and focuses on finding qualified candidates to fill it. Strategic talent advisory begins earlier.

    It examines the business problem behind the vacancy, the outcomes the organization needs, and whether the proposed role is designed to produce them. It may involve challenging an inherited job description, clarifying responsibilities, evaluating the external talent market, considering internal capability, or identifying weaknesses in the selection process before they become costly hiring mistakes.

    Melissa Brandt & Associates partners with organizations that need more than additional recruiting capacity. MB&A provides executive search, recruiting strategy, hiring-process consulting, and fractional recruiting support grounded in a broader understanding of how talent decisions affect organizational performance.

    The objective is not simply to fill an opening. It is to help the organization make a sound decision about the work, the role, and the person entrusted with it.

    What strategic talent advisory looks like in practice

    A strong talent adviser helps an organization ask questions that can easily be overlooked once the urgency of a search takes over:

    • Why does this role need to exist now?
    • What business problem or opportunity should it address?
    • What has changed since the position was last filled?
    • Which qualifications are essential, and which are inherited preferences?
    • Does the title accurately reflect the work and attract the appropriate candidates?
    • What should success look like during the first six to twelve months?
    • Could an internal employee assume the role with appropriate development and support?
    • Are the interview and assessment methods actually measuring what matters?

    Answering these questions can change the search itself. The organization may discover that it needs a different level of experience, a different reporting structure, a more accurate title, or a capability that was missing from the original description. In some cases, it may determine that replacing the previous position is not the best solution at all.

    That is the difference between processing a requisition and advising on a talent decision.

    Technology increases the need for judgment

    AI-enabled recruiting tools can help organizations draft materials, organize information, identify candidates, and manage high application volume. Used responsibly, technology can improve efficiency and support a more disciplined hiring process.

    It can also apply weak assumptions more efficiently.

    An automated system cannot determine whether an outdated job description reflects the organization’s current needs. It cannot resolve disagreement among leaders about the purpose of a role. It cannot decide whether a familiar credential is genuinely necessary or simply inherited from previous searches. If the underlying definition of the job is wrong, technology can accelerate the search without improving the decision.

    The relevant question is not whether an organization uses AI. It is where automation adds value, where human judgment remains essential, and whether the process is built on an accurate understanding of the work.

    What organizations need now

    Employers are operating in a market shaped by changing technology, evolving workforce expectations, competition for specialized talent, and growing pressure to make decisions quickly. Meeting those conditions requires more than speed.

    Organizations need:

    • Hiring strategies connected to business priorities
    • Executive search support for consequential leadership roles
    • Accurate role definition before recruitment begins
    • Selection processes that are structured, relevant, and defensible
    • Practical judgment about where technology supports hiring and where it should not replace human review
    • Flexible recruiting expertise when internal teams need additional capacity or specialized support

    These needs do not always require a large consulting engagement. Sometimes an organization needs a trusted adviser to identify the right questions, clarify the decision, and help execute the search with greater discipline.

    Better hiring begins with a better understanding of the problem

    With nearly two decades of recruiting and executive-search experience, Melissa Brandt & Associates helps organizations move beyond the assumption that every vacancy is simply a position to be filled.

    MB&A works with business leaders to define hiring needs, strengthen selection practices, identify leadership talent, and build recruiting approaches appropriate to the organization’s actual goals.

    This publication will examine the decisions beneath hiring: how roles are defined, how candidates are evaluated, where conventional practices create hidden risk, and how organizations can use technology without surrendering judgment.

    Because the strongest hiring process is not necessarily the one that moves fastest. It is the one that begins with an accurate understanding of what the organization needs—and why.

    If your organization is reconsidering a critical role, strengthening its recruiting process, or preparing for an executive search, Melissa Brandt & Associates can help bring clarity, rigor, and experienced judgment to the decision.

    By Melissa Brandt  |  Melissa Brandt & Associates