Introduction

Hiring technical people isn’t always as straightforward as matching a list of skills to a job description. Organizations may struggle to define what they actually need, while candidates can find themselves applying for roles where the expectations don’t match the work they’ll eventually be doing.

In this episode, Ashley Randall joins Jack to look at what happens when the person has the right skills, but the organization may be hiring them for the wrong job.

The Business Perspective

Ashley Randall joins Jack from the other side of the table. She brings more than two decades of experience in human services operations and industrial-organizational psychology. Her perspective focuses less on how to recruit technical people and more on a fundamental question: has the organization correctly identified the problem it needs to solve?

“Leadership and specialized talent alignment is often the most common systemic hurdle.” — Ashley Randall

The conversation looks at how businesses decide which technical specialists they need. It also examines how those requirements become job descriptions and what happens when management expectations don’t match the reality of the technical role.

Hiring Challenges

Ashley identifies the search for the technical “unicorn” as a common problem. Companies look for one candidate who can cover a wide range of skills and responsibilities. In reality, those requirements may not belong in a single role.

The problem can start before recruitment even begins. Businesses may create a job description around the symptoms of a problem instead of examining the underlying workflow. They can then end up hiring someone for the wrong role, regardless of how qualified that person might be.

Evaluating Technical Talent

Avoiding the Unicorn Hunt

Before looking for a candidate, Ashley argues that organizations need to understand what they actually expect that person to do. Are they building something new, improving an existing environment, or expected to do both? Without that distinction, the role can quickly become a collection of unrelated requirements looking for one impossible candidate.

Who Should Evaluate?

Technical candidates also need to be evaluated by people who understand the work. Without technical expertise involved in the hiring process, it becomes much harder to distinguish someone who can actually do the job from someone who simply interviews well and knows the right terminology.

Structural Issues and Role Mismatches

Problems can start when the organization defines the role incorrectly. Ashley explains how companies may confuse different needs. Understanding and improving a workflow, for example, isn’t the same as developing the software behind it.

Hiring someone with the right technical skills won’t help if those skills don’t match the work.

Miscommunication

Communication between technical teams, management, and HR creates another challenge. HR may ask questions that don’t reveal whether a candidate can actually perform the technical role.

Technical specialists face the opposite problem. They may struggle to explain their experience in terms the people making the hiring decision understand.

Process Improvement

Rather than trying to fix a mismatch after hiring someone, Ashley argues that organizations should involve the relevant people earlier in the process. They need to understand the workflow, define the expected deliverables, and bring in people who understand the technical work when deciding what kind of role they actually need.

Aligning those expectations before recruitment begins can prevent organizations from hiring someone for a role they never properly defined in the first place.

“We have to be stakeholders, not take holders.” — Ashley Randall

Culture and Metrics

Hiring the right person only solves part of the problem. Once someone joins the organization, performance metrics and cooperation between teams can determine whether the organization actually makes effective use of that person’s expertise.

Ashley and Jack discuss the problems created when departments operate in silos and when organizational metrics don’t reflect the work people are actually doing. Better communication between leadership, technical specialists, and other departments can help ensure that expectations remain aligned with the reality of the job.

HR and Employee Relations

Jack raises a familiar belief among technical staff: HR is there to protect the company, not the employee. Ashley adds some nuance to that view, arguing that HR still has a responsibility to understand what employees need while also representing the interests of the organization.

The difficulty comes when those two sides are treated as opposing interests rather than problems that need to be balanced.

“If HR cares only about the company and not the individual, that’s a problem that needs addressing.” — Ashley Randall

Building a Bridge

Improving that relationship requires communication in both directions. HR needs to understand the work technical specialists are doing, while technical teams need a way to communicate their needs and concerns to the rest of the organization. Neither side benefits when they operate as separate worlds.

Conclusion

Hiring the right technical person starts with understanding the problem the organization is actually trying to solve. A candidate can have exactly the right skills and still end up in the wrong role if expectations, responsibilities, and measures of success were poorly defined from the beginning.

As Ashley and Jack discuss, many apparent hiring problems aren’t really about finding better candidates. Sometimes the organization needs to take a closer look at the job itself.

Takeaway for Technical Roles

For technical specialists, part of the challenge is translating technical experience into terms the rest of the organization understands. That doesn’t mean simplifying the work, but explaining what the skills are for, what problems they solve, and what the organization can realistically expect from the role.

The same applies on the other side of the table. Businesses need to understand what they are hiring for before looking for someone to fill the position. Getting the right person into the right role depends as much on defining the problem correctly as it does on finding someone with the right skills.