We've Learned How to Screen Applicants. Have We Forgotten How to Hire People?

Spend a little time on LinkedIn, particularly among those looking for employment, and you will see a growing frustration with the hiring process. Applicants describe submitting résumés for jobs they believe they are qualified for, only to receive rejection notices, sometimes within minutes. Recruiters describe being overwhelmed by hundreds of applications for a single opening, many from people who don't meet the basic requirements. Employers are turning to technology, including artificial intelligence, to manage the volume, while applicants are using the same tools to improve their résumés and increase their chances of being noticed.
Both sides have legitimate concerns, and both are trying to work within a system that has become increasingly complicated. But I wonder whether we have become so focused on making recruiting more efficient that we have lost sight of what really matters: hiring the right people.
I don't believe artificial intelligence is the problem. Like any technology, its value depends on how we use it, the information we provide, and the decisions we expect it to support. Used properly, AI can help employers review applications, identify relevant experience, and reduce administrative work. Used poorly, it can speed up an ineffective process, rejecting potentially excellent applicants before anyone has taken the time to consider what they might bring to the organization.
But I think the problem begins long before someone submits a résumé. If we want to improve hiring, we need to look at how we prepare managers, develop job descriptions, evaluate applicants, and support employees after they join us.
Hiring Begins Before the Job Is Posted
Throughout my career, I have hired people for positions ranging from entry-level employees to management and leadership roles. One thing I have learned is that hiring is a skill, and it is not something a person automatically knows how to do because they have been promoted into management.
We spend considerable time teaching managers how to supervise employees, manage budgets, address performance problems, and meet operational expectations. Yet we often give those same managers the responsibility of selecting the people who will determine their department's success without teaching them how to make those decisions.
Before we can evaluate applicants, we need to understand what we are hiring them to do. That sounds obvious, but I question how often employers take a serious look at a position before posting it.
Who writes the job description? Who decides which qualifications are required and which are preferred? Who determines that a particular degree, certification, or number of years of experience is necessary?
Ideally, those decisions should involve the hiring manager, human resources, recruiting, and others who understand the position. Each brings valuable knowledge, but the manager responsible for the work must have a meaningful role in deciding what successful performance requires.
I have always believed that every line in a job description should have a purpose and a reason for being there. Every responsibility and qualification should relate to the work, the environment in which it will be performed, or the results the employer expects.
If we require a bachelor's or master's degree, why? If we require a particular certification, what knowledge or ability does it establish? If we require ten years of management experience, what are we expecting those ten years to demonstrate?
Education matters, and earning a degree is an accomplishment worthy of recognition. Certifications can demonstrate important knowledge and specialized training, and experience certainly has value. But none of these, by themselves, guarantees someone can do the job successfully.
Five years of managing people does not necessarily mean five years of managing people well. A military or law enforcement background does not automatically prepare someone to lead security in a hospital. A person may have held an impressive title for years without developing the judgment, leadership ability, or interpersonal skills needed in another setting.
On the other hand, someone whose career has taken a less traditional path may have exactly the experience and abilities we need.
We need to understand the difference between qualifications that are truly necessary and those we have simply become accustomed to requiring.
Using Technology Without Losing Good Candidates
Once we understand the position and its requirements, technology can help us identify qualified applicants.
I don't believe every application must receive a complete review by a person. When hundreds of people apply for one opening, that may not be practical. Automated screening can help identify those who meet the basic requirements and allow recruiters to spend more time evaluating promising candidates.
But the results are only as good as the criteria used to make those decisions.
If a position legally requires a professional license, it makes sense to exclude applicants who don't have it. However, if a degree is preferred but equivalent experience is acceptable, the screening system should recognize that difference rather than automatically rejecting someone who has demonstrated the necessary skills through years of work.
We should also be careful not to confuse automated screening with artificial intelligence. Someone receiving a rejection within minutes may have been eliminated by a simple rule in an applicant tracking system rather than an AI evaluation. In either case, someone established the requirements that led to that decision.
Which raises a question I believe deserves more attention: how often do employers check whether their screening systems are working as intended?
We measure time-to-fill, cost-per-hire, and other recruiting statistics, but do we examine how many qualified people may have been rejected before the hiring manager ever saw their applications? Do we occasionally review rejected résumés to determine whether our criteria are helping us identify good candidates or causing us to overlook them?
Efficiency matters, but our goal should not be to eliminate applicants as quickly as possible. It should be to find people who have a reasonable chance of succeeding in the position.
Technology should help us accomplish that goal.
Interviewing Is a Management Skill
Once we identify qualified applicants, we face another important responsibility: getting to know the people behind the résumés.
Many years ago, while serving in the Air Force in a law enforcement position, my supervisor handed me a book and instructed me to read it. The book was Questioning Techniques and Tactics by Jeffrey L. Kestler, part of the Trial Practice Series. It was written primarily for attorneys to help them develop questioning strategies and examine witnesses. At first glance, it might have seemed an unusual book to give me, but I found it extremely valuable.
When I read something, particularly material written for another profession, I try to understand how its lessons might apply to my own work. This book explored how to plan questions, the psychology behind questioning, and how to approach people with different personalities and communication styles. It taught me that effective questioning involves much more than asking something and recording the answer. It requires preparation, careful listening, observation, and knowing when a response deserves further attention.
Years later, after leaving the military and moving into leadership positions where I was responsible for hiring employees, I discovered those same lessons were useful in job interviews. Certainly, interviewing a prospective employee is not the same as questioning a witness, and the goals are very different. But knowing how to plan a conversation, listen and observe carefully, understand how people communicate, and recognize when to ask another question are skills that apply to both.
That experience shaped how I conduct interviews. I learned to pay attention not only to what people say, but how they explain their decisions, describe their experiences, and respond when asked to look at a situation from another perspective. Sometimes the most useful information comes from a question you hadn't planned to ask, prompted by something the applicant said that deserves a closer look.
The purpose of questioning is discovery. In a job interview, we should be trying to learn something about a person that we didn't know when the conversation began, rather than simply confirming what we've already read on their résumé.
I have always viewed interviewing as somewhat similar to dating. Both parties want to make a good impression, and both tend to present the version of themselves they believe the other person wants to see. During the first conversation, people are often nervous, guarded, and careful about their answers. As they become more comfortable, the discussion can become more natural.
For management positions, I have generally preferred at least three meaningful interactions before making a hiring decision. Not because three interviews guarantee a better choice, but because I want opportunities to understand how someone thinks, communicates, makes decisions, and responds to different situations.
These meetings do not all need to be formal interviews across a conference table. A telephone call or a relaxed conversation can be just as useful when it serves a clear purpose. Sometimes removing the formality allows people to speak more freely and gives both sides a better opportunity to understand each other. I have also found myself recognizing someone's potential long before they ever considered applying for a position. Through everyday conversations and interactions, you can learn a great deal about how people think, communicate, and treat others. As a manager, I believe you should always be looking for good people, whether you have an opening or not.
However, a good interview requires more than a prepared list of questions. Managers need to recognize important details in an answer and know how to follow up without losing sight of what they are trying to learn.
I have participated in interviews where we were instructed to ask every candidate the same questions and avoid anything that wasn't on the approved list. I understand why consistency, fairness, and legal compliance matter, and I agree that everyone should be evaluated against the same job-related standards.
But that should not prevent us from exploring an applicant's answers.
If I ask two management candidates how they handled a difficult employee performance issue, their responses may lead to completely different follow-up questions. One may describe terminating an employee, while another may explain how additional training solved the problem. In both cases, I want to understand how they reached their decisions, what alternatives they considered, how they treated the employee, and what they learned.
The follow-up questions may be different, but I'm evaluating the same leadership abilities.
We can maintain fair and consistent standards without making every interview an identical conversation.
We also need to recognize the limits of our observations. Confidence does not always mean competence, and a quiet or nervous applicant may have excellent leadership skills. How someone communicates can provide useful information, but we should not make assumptions about their character based on a first impression. We need to ask questions that help us understand their judgment, experience, and ability to work with others.
There is another benefit to taking this approach. When candidates realize the interviewer is genuinely listening, asking thoughtful questions, and showing interest in their experiences, they become more involved in the conversation. They can see that the employer is interested in understanding who they are rather than simply moving them through a series of prepared questions.
And we should remember that an interview works both ways. Applicants are also deciding whether the organization and its leaders are people they want to work with.
Stop Looking for the Perfect Candidate
One of the biggest mistakes I believe employers make is creating job descriptions around an ideal person who arrives with every skill, qualification, and ability we could possibly want.
We want extensive experience, advanced education, multiple certifications, technical knowledge, strong leadership skills, excellent communication abilities, and a proven record of success. As that list grows, so does the possibility that we're searching for someone who may not realistically exist, while overlooking people who could perform the job very well.
There is nothing wrong with wanting highly qualified employees, but hiring always involves some uncertainty. Even the most impressive résumé cannot guarantee success.
I believe managers need to distinguish between what a person must know when hired and what can reasonably be taught or developed.
I can teach someone an organization's policies, procedures, reporting systems, and daily operations. Given enough time and the proper resources, I can help an employee develop technical skills and improve in many areas.
But there are other qualities that are much harder to develop, especially when a manager must also keep a department operating.
Think about empathy, integrity, good judgment, emotional control, and the ability to treat people with respect during stressful situations. These qualities can improve over time, but we cannot assume that someone who repeatedly struggles with them will change simply because they have been hired.
In hospital security, for example, I want to know how an applicant might respond to an upset family member, a frightened patient, or a nurse asking for help during a difficult situation. Technical knowledge is important, but so is the ability to remain calm, communicate respectfully, understand what others are experiencing, and make sound decisions.
Someone may have extensive law enforcement experience and still struggle to understand the role of security in a healthcare setting. Another person may have less traditional experience but show the judgment, interpersonal skills, and willingness to learn that could make them an excellent employee.
Neither should automatically be selected or rejected based on their background alone. We need to consider what the job requires, what the applicant can demonstrate, and what we can realistically teach.
The goal should not be to find someone who requires no development. We should be looking for a person who has the essential abilities and the potential to succeed with good leadership, training, and support.
Hiring Is the Beginning of Our Responsibility
We spend a great deal of time trying to select the right employee, but what happens after that person is hired?
During my Air Force career, we used Job Qualification Standards, or JQS, to document and manage proficiency. These were not hiring tools. They were living records that identified the tasks, knowledge, and skills individuals were expected to demonstrate at their assigned skill levels.
As people advanced, their progress was evaluated and documented. When someone failed to perform a task properly, that item could be reopened, additional training assigned, and a new completion date established. The purpose was not simply to show that training had occurred, but to confirm that the person could perform the work to the required standard.
That lesson has stayed with me throughout my career.
Training is not the same as proficiency, and completing a course does not necessarily mean someone can successfully apply what was taught.
Many employers rely heavily on orientation, annual training, and periodic performance reviews without having a practical method for identifying individual skill gaps and helping employees improve.
We should establish clear expectations, evaluate performance, provide mentoring, document progress, and address problems with appropriate corrective action. We also need to recognize that not every mistake is a training problem. Poor equipment, inadequate staffing, unclear procedures, and ineffective leadership can all contribute to failure.
A manager's job involves more than deciding whether an employee is meeting expectations. It includes understanding why someone is succeeding or struggling and taking appropriate action.
Employees remain responsible for their conduct and performance, but employers must also provide an environment where people understand their roles and have the training, tools, leadership, and support they need to succeed.
A hiring decision isn't proven successful when someone accepts the job offer. We learn whether we made a good choice through the employee's performance, growth, and contributions over time.

A Shared Responsibility for Better Hiring
Improving how we hire should not become an argument between recruiters, HR professionals, hiring managers, applicants, or those developing the technology used in recruiting.
Each has an important role.
HR and recruiting professionals bring knowledge of employment practices, compensation, legal requirements, and candidate management. Department leaders understand the work, the skills required, the operating environment, and what good performance looks like. Applicants have a responsibility to present their qualifications honestly, and technology can help everyone manage their part of the work.
But these efforts need to be coordinated, with clear expectations about who is responsible for making decisions.
Who determines which qualifications are truly required? Who confirms that automated screening reflects those requirements? Who makes sure managers know how to conduct interviews and evaluate applicants? Who examines whether the hiring process is producing good results? And who is responsible for helping employees grow after they are hired?
These are questions organizations should be asking together, not opportunities to assign blame.
Filling a vacancy quickly and following every required procedure are important, but they do not tell us whether we hired someone who can contribute to the organization's success. We should also be looking at how well our employees perform, whether they remain with us, and how effectively we help them develop.
Rethinking What Successful Hiring Looks Like
We will never eliminate uncertainty from hiring. Even an experienced manager, using good information and sound judgment, can make a decision that doesn't work out. People are complicated, workplaces change, and previous success does not guarantee future results.
But we can make better decisions by preparing managers to understand the positions they need to fill, identify necessary qualifications, and recognize the skills and potential that applicants bring. We can use technology to support that work while checking whether our screening methods are excluding people we should be considering. And we can continue investing in employees after they join us rather than expecting them to arrive with every skill they will ever need.
Most importantly, we should remember that the people applying for our jobs are more than the information contained in their résumés.
Behind every application is a person with experiences, abilities, strengths, and potential that may never be fully captured in a two-page résumé or a list of predefined qualifications.
I am not suggesting that we lower our standards or overlook essential requirements. I am suggesting that we make sure those standards have a purpose, that our hiring methods help us recognize capable people, and that those making the decisions know how to evaluate them.
Perhaps the question isn't simply whether we need better technology to screen applicants. Perhaps we should also be asking whether we have adequately prepared our managers to recognize, hire, and develop the people our organizations need.
After all, we aren't simply filling positions. We're building organizations, developing future leaders, and making decisions that affect both our institutions and the lives of the people who work within them.
If we expect managers to make better hiring decisions, we need to invest in teaching them how to hire, just as we invest in teaching them how to perform every other important management responsibility.




Comments