Confessions of a Hiring Manager: What 20 Years of Interviews Taught Me

My primary role is Director of IT Procurement and Budget. Human Resources isn’t in my title, and I certainly don’t consider myself an HR professional. Yet over the years, I’ve realized that hiring, developing and managing people is a subtle but very important part of my job.
I hire employees and consultants for my own operation, and I also regularly help colleagues identify consultants to support their areas. That has meant reviewing hundreds of résumés, deciding whom to interview, assessing compensation, evaluating technical and interpersonal skills, participating in structured interviews, and ultimately trying to answer a deceptively difficult question:
Is this person likely to succeed here?
Hiring, of course, is only the beginning. After someone arrives, there is training, development, performance management, retention, career expectations and, occasionally, the difficult determination that a relationship simply isn’t working.
I’ve hired some outstanding people. I’ve also made mistakes.
Anyone who has hired enough people probably has.
And I’ve learned almost as much about hiring from being a candidate myself.
I’ve Said “No” to Some Good Jobs
I’ve interviewed for positions, received offers and walked away because the opportunity didn’t make sense for me.
Early in my career, I passed on a higher-paying position to accept a lower-paying one because I believed the experience would be more valuable over the long term. At that point in my career, I decided that acquiring the right skills was worth more than maximizing my immediate salary.
At another point, I considered leaving government for the nonprofit sector during an economic downturn. The opportunity was interesting, but government offered considerably greater job security. At that particular moment in my life, security mattered more.
Later, I turned down an opportunity to become Comptroller of a prominent nonprofit. The title was attractive, but when I considered pension, healthcare, commute and overall quality of life, staying where I was made more sense.
I also passed on a finance position at a well-known public university. The commute would have been difficult. More importantly, the panel interview gave me pause. Several people I met appeared deeply dissatisfied with the organization’s status quo while simultaneously looking to the incoming person to guarantee that it could be fixed. The proposed salary was also approximately $20,000 below what the incumbent had earned.
I decided it wasn’t the right fit.
Another opportunity offered me only about $4,000 more per year. I would have lost free parking, incurred new commuting costs, encountered worse traffic and assumed responsibility for roughly 200 employees and approximately $200 million in parking revenue.
The title and responsibilities were larger. The actual benefit to me wasn’t.
At some point, every candidate has to ask a perfectly legitimate question:
What’s in it for me?
Employers shouldn’t be offended by that question.
Every serious candidate is already asking it.
Employment Is a Two-Way Value Proposition
Organizations naturally ask candidates, Why should we hire you?
Candidates should be asking, Why should I work for you?
A successful hire requires good answers to both questions.
That’s why I increasingly think of employment as a symbiotic relationship rather than a one-sided transaction.
The organization has objectives it needs the employee to accomplish. The employee has financial, professional and personal objectives that he or she hopes the organization will help fulfill.
The best hires occur where those interests meaningfully overlap.
Salary matters. Skills matter. Career goals matter. Organizational needs matter. Work location matters. Workplace culture matters. Advancement opportunities matter. So do the expectations each side brings to the relationship.
If someone sees a position only as somewhere to collect a paycheck until something better appears, that may not be a great investment for the employer.
But the reverse is equally true. If an organization treats employees as interchangeable resources, it shouldn’t be surprised when employees treat employers the same way.
Salary Satisfaction Matters
Managers sometimes underestimate the difference between someone being willing to accept a salary and actually being satisfied with it.
If a new employee begins on Monday already convinced that he or she is substantially underpaid, you may have hired someone who starts looking for the next job on Tuesday.
For a recent consultant hire supporting one of my primarily administrative functions, I researched what appeared to be an appropriate market rate based on the responsibilities, required experience and comparable work.
Then I asked the candidate what she believed would be appropriate.
Interestingly, she proposed essentially the same hourly rate I had independently arrived at. She even indicated that she would be willing to accept approximately $5 per hour less if necessary to secure the opportunity.
There was no need to push her lower simply because she was willing to accept less.
Our expectations were already aligned.
My objective in hiring isn’t to obtain labor at the lowest possible price. It’s to obtain the right person at a price where both sides believe the arrangement is fair.
Saving a few dollars per hour isn’t much of a victory if the employee leaves six months later and you have to recruit, interview and train a replacement.
Logistics Are Part of Fit
For positions requiring regular in-person attendance, I also pay attention to whether the logistics of getting to the workplace appear sustainable.
That isn’t about assuming that someone who lives farther away will be a poor employee. Plenty of people successfully manage long commutes.
It’s about having a candid conversation about the requirements of the position and whether they realistically fit the candidate’s circumstances.
For many administrative positions, I can teach the work.
I can teach processes, systems, procurement procedures, budgeting practices, spreadsheets and institutional knowledge.
What I can’t control is someone’s transportation environment.
For remote positions, the considerations change. Remote work requires independence, responsiveness, communication, self-management and the ability to produce measurable results without continuous in-person supervision.
The larger lesson is that workplace fit includes the practical conditions under which the work will actually be performed.
Credentials Are Not the Same as Demonstrated Ability
One of my less successful hires taught me an important lesson about assumptions.
I once gave someone an opportunity partly because she was studying quantitative applied mathematics. I assumed that someone pursuing that discipline would naturally be very strong with spreadsheets, data and quantitative administrative work.
I didn’t test those skills.
That was my mistake.
There was also a human element. She had described significant personal tragedies involving her father and brother and their alleged involvement in cleanup efforts associated with Chernobyl. I empathized with what she told me and wanted to give her an opportunity.
Once she joined the team, however, the technical capabilities I had assumed were not at the level I expected. There were also interpersonal and communication challenges, and ultimately it wasn’t a good fit for the team.
I learned two lessons from that experience.
First, never substitute credentials for demonstrated capability.
If Excel is central to the job, test Excel.
If writing is important, evaluate writing.
If the position requires analytical reasoning, give the candidate a realistic problem and see how he or she approaches it.
If communication is critical, create enough interaction during the interview process to assess communication.
A résumé tells you what someone says they can do. A thoughtful selection process should help establish whether they can actually do it.
The second lesson was more personal: empathy should influence how we treat people, but it shouldn’t replace objective judgment about whether someone is right for a particular job.
I still believe strongly in giving people opportunities. I’ve simply learned to validate the assumptions underlying that decision.
AI Can Help Screen Candidates- But It Shouldn’t Make the Decision
Technology has added another dimension to recruiting.
Receiving hundreds of applications for a position isn’t unusual. When 300 or 400 résumés arrive, objectively comparing every candidate becomes a significant undertaking.
I still like to manually review every résumé.
But I also use AI as a second set of eyes.
I might use it to compare applicants against stated requirements, identify experience I may have overlooked, recognize transferable skills or independently rank candidates so I can compare the results with my own assessment.
What I don’t want is an algorithm making the hiring decision for me.
I see AI as a tool for challenging and validating human judgment, not replacing it.
That distinction is important, particularly in public-sector hiring, where fairness, consistency and defensible selection processes matter.
I Prefer Interviews That Feel Like Conversations
Government hiring often requires structure, and for good reason.
When required, I use a formal process- often asking every candidate the same set of approximately ten questions so applicants can be evaluated consistently.
But within that framework, I prefer an interview that becomes a conversation.
I’m less interested in discovering who prepared the most polished interview answers than in understanding how someone thinks.
Why does this person want the job?
What motivates them?
What are they hoping to learn?
What do they want to be doing several years from now?
How do they approach a problem they haven’t encountered before?
What are they expecting from me?
And can I realistically provide it?
Sometimes the most revealing part of an interview occurs after the formal questions are finished.
A conversation can reveal curiosity, judgment, listening skills, communication style and whether the candidate understands what the job actually entails.
Most of My Hires Have Been Excellent
While mistakes provide useful lessons, I don’t want to overstate them.
Most of the people I’ve hired have been excellent.
Many have eventually left the organization, but often that wasn’t because the hiring decision failed. They had developed professionally and reached a point where our organization couldn’t provide the advancement, compensation, responsibilities or new challenges they wanted.
Others simply found interesting opportunities elsewhere- sometimes with impressive organizations inside government and sometimes outside it.
I actually consider that a positive reflection on the selection process.
If someone I hired performs well, develops professionally and becomes competitive for excellent opportunities elsewhere, then I probably identified good talent in the first place.
Retention matters, but retention alone isn’t the measure of a successful hire.
Sometimes a strong employee leaving tells you more about the limitations of the organization’s career ladder than it does about the hiring process.
Good people should have options.
As managers, we’d naturally prefer to retain our strongest employees. But I think there is also something rewarding about hiring someone with potential, giving that person meaningful experience, watching them develop and then seeing them advance—even when their next opportunity takes them somewhere else.
A bad hire and a good employee who outgrows an organization are two very different things.
Organizational Fit Matters
A candidate can be extremely talented and still be wrong for a particular organization.
That doesn’t make the candidate a bad employee.
Someone who thrives in an entrepreneurial environment may become frustrated by extensive governmental approval processes. Someone who prefers highly defined responsibilities may struggle in a position where priorities change frequently. Someone seeking rapid advancement may become dissatisfied in an organization where promotions depend on Civil Service titles, examinations, vacancies or other structural limitations.
That’s why managers should be candid during interviews.
Don’t sell candidates a fictional version of the job.
If the organization is bureaucratic, don’t pretend it isn’t.
If advancement opportunities are limited, don’t imply otherwise.
If the workload is demanding, explain it.
If the person will inherit difficult problems, say so.
A candidate accepting the job you actually have is far more valuable than a candidate accepting the job you marketed to them.
People Don’t Have to Stay Forever for a Hire to Be Successful
I don’t expect everyone I hire to remain with the organization forever.
That’s neither realistic nor necessarily desirable.
What I want is enough alignment that the relationship creates value for both sides for a meaningful period.
If someone joins my operation, learns, contributes, takes on greater responsibilities and eventually advances somewhere else, that can still be an extremely successful employment relationship.
Managers should be developing people, not holding them hostage to the positions in which they were hired.
And when excellent people repeatedly leave because there is nowhere internally for them to go, leadership should recognize what the data may be telling them.
That is no longer primarily a recruitment problem.
It may be a retention problem, a compensation problem, a succession-planning problem or an organizational-design problem.
Probation Has a Purpose
There is another side to hiring that managers sometimes avoid discussing: occasionally, a hire simply doesn’t work.
Hiring someone creates an obligation to give that person a reasonable opportunity to succeed. Managers should communicate expectations, provide appropriate training, offer feedback and distinguish between someone learning a job and someone fundamentally unable or unwilling to perform it.
But compassion shouldn’t become an excuse for avoiding a necessary management decision.
Probationary periods exist for a reason.
They aren’t merely a countdown until permanent employment. They’re an opportunity for both the employee and organization to determine whether the relationship actually works.
If someone consistently cannot perform the job, isn’t meeting clearly communicated expectations or demonstrates that the position simply isn’t a good fit, delaying a necessary decision can create larger problems.
Other employees absorb the work.
Strong performers become frustrated.
Managers spend disproportionate amounts of time compensating for deficiencies.
And the organization suffers.
There are circumstances where additional training, coaching or appropriate accommodation is warranted. There are also circumstances where separation is the responsible decision, subject, of course, to applicable Civil Service requirements, collective bargaining agreements, HR policies and employment law.
Consultants Require Accountability Too
The principle is even more straightforward with consultants.
A consultant is retained to provide expertise, capacity or defined deliverables.
If that value isn’t being delivered, management has an obligation to address it.
That doesn’t mean terminating someone because of one mistake or one difficult week. It means establishing expectations, identifying deficiencies, communicating them, allowing a reasonable opportunity for correction where appropriate, and then making a decision.
Keeping a poorly performing consultant indefinitely because ending the engagement feels uncomfortable isn’t responsible stewardship of public resources.
At the same time, managers should remain human.
People get sick. Families experience emergencies. Good employees have bad weeks. People make mistakes.
Context matters.
The management challenge is distinguishing between a temporary problem affecting an otherwise strong performer and a sustained pattern demonstrating that the arrangement isn’t working.
Being Human Doesn’t Mean Avoiding Difficult Decisions
Letting someone go is unpleasant.
I think it probably should be.
If ending someone’s employment becomes emotionally meaningless to a manager, that’s a problem of its own.
But empathy doesn’t require paralysis.
A manager can treat someone respectfully, communicate clearly, follow the appropriate process and still conclude that an employment relationship needs to end.
Some of the worst personnel problems aren’t created by managers being too harsh. They’re created when managers postpone difficult conversations.
They wait.
They hope the problem resolves itself.
They compensate for the employee.
They redistribute the work.
They gradually lower expectations.
Eventually, a manageable personnel issue becomes an organizational problem.
Being human doesn’t mean avoiding difficult decisions.
It means making them fairly, appropriately and with dignity.
Hiring Is Ultimately About Matching
After years of interviewing people, being interviewed myself, accepting jobs, declining jobs, hiring excellent employees, making a few hiring mistakes, managing staff and overseeing consultants, I’ve become convinced that hiring is fundamentally an exercise in matching.
You’re matching skills to responsibilities.
Compensation to expectations.
Career goals to organizational opportunities.
Work arrangements to personal circumstances.
Personality and working style to the team.
Experience to what can reasonably be taught.
Credentials to demonstrated capability.
And one person’s expectations to an organization’s reality.
The candidate with the most impressive résumé isn’t automatically the best hire.
The highest-paying job isn’t automatically the best career move.
An excellent employee who leaves isn’t automatically a retention failure.
And someone who doesn’t succeed in one position isn’t necessarily a bad employee.
Sometimes it’s simply the wrong match.
So I’ve come to believe that the most important question in hiring isn’t simply:
“Can this person do the job?”
It’s something broader:
“Does this relationship make sense for both of us- and have we done enough to know?”
If employers and candidates asked that question more candidly at the beginning, I suspect we’d have fewer bad hires, fewer unhappy employees, better retention and stronger organizations.
And in government, where every position ultimately exists to help deliver something to the public, getting that decision right matters far beyond the interview room.






Join the discussion
Members can read and add comments on every article.