The job is the pitch

Most recruiting outreach assumes the candidate is the product and the company is the customer.

We build a funnel, increase volume, tune response rates, and complain that the people we want are difficult to close. The message changes around the edges, but the basic proposition is usually the same: we are hiring, you seem qualified, would you like to talk?

When that message is sent broadly to people who are not qualified or have no reason to move, it does more than waste a recruiter's time. It teaches the market that the company does not know who it needs.

You cannot outreach your way out of a job nobody understands.

The first recruiting question should not be where to find more candidates. It should be why a specific kind of person would find this work unusually valuable now.

In practice, strong candidates tend to become reachable for a few overlapping reasons. They are unhappy with their current job at exactly the right moment. They are waiting for scope, promotion, or compensation that is not coming. Or they see novel work that extends something they already know into a direction they want to learn.

There is a fourth reason: desperation. Layoffs, a difficult market, or graduating without a job can make someone responsive. Desperation may create timing, but it does not create durable motivation. It works when one of the other reasons is present too.

This means the pitch cannot simply be that the company is growing or pays well. Those facts may matter, but they do not explain why this work should interrupt the trajectory of a person who already has options.

Companies often pitch their category instead of the opportunity. “We are an AI platform” may accurately describe the business, but it tells a candidate almost nothing about what they could change, what they would learn, or why their particular experience matters.

A stronger pitch explains the transition the person would help create. What exists today? What should exist a year from now? Which part of that change genuinely depends on the judgment they have developed elsewhere?

That can be a reason to move. It also creates an obligation. If the company sells a transformative role and the actual job is repetitive delivery work with a fashionable label, recruiting has borrowed excitement from a future it is not building.

For a team doing automation work, the promise can be concrete: automate yourself out of your current work so you can do more interesting things.

The weekly question becomes: how do I never do this task again?

That is not a promise that automation eliminates the person. It is a claim that the team's purpose is to turn repeated delivery into systems, then move its attention to the next problem. The work should expand the person's judgment rather than trap them in an increasingly efficient grind.

The interview is evidence of the job

Once the pitch earns a conversation, the interview process has to test the things the job actually needs.

For technical hiring in AI, I care about three areas.

The first is fundamentals. Using ChatGPT is not evidence that someone understands the mechanics, failure modes, or tradeoffs of the systems they want to build. I do not expect every candidate to arrive with the same background. I do expect curiosity deep enough that they have tried to understand what is happening below the interface.

The second is motivation. Money matters, and pretending otherwise makes the conversation less honest. It is still useful to understand whether the candidate wants to improve a system, increase their impact, or extend their expertise—or merely found the highest current bidder. A difficult technical environment needs people who care what becomes better because they joined.

The third is communication. This is not a proxy for accent, personality, or performing confidence in an interview. It is whether the candidate can engage in a candid technical conversation: explain what they know, admit what they do not, ask useful questions, and update when the evidence changes.

A low pass rate late in the process is not just a candidate-quality problem. It may mean the earlier screens are measuring the wrong things or refusing to make decisions. If candidates repeatedly reach an onsite coding interview without the fundamentals needed to pass it, the company is transferring the cost of an unclear filter onto candidates and interviewers.

Rejection still communicates the culture

Companies often describe interviews as mutual evaluation, then behave as though that stops the moment they decide not to hire someone.

Useful feedback to a rejected candidate is difficult. Legal risk, inconsistent interviewer notes, and sheer volume all push companies toward a generic rejection. There are legitimate limits to what can be promised.

But when the process has enough evidence to reject someone, it should usually have enough evidence to offer something constructive. A specific explanation gives the candidate a chance to learn and demonstrates that the company meant what it said about investing in growth and candor.

The point is not to turn rejection into free coaching or invite every decision to be relitigated. It is to leave the person with more than the knowledge that several hours of their time disappeared into a process.

The same principle applies when selling candidates who passed. If every dinner includes only managers, the candidate learns how management describes the culture. Include people with different roles, experiences, and levels, and the candidate can learn whether the culture survives contact with the team.

Hiring is one of the earliest places where a company's stated culture becomes observable behavior.

An interviewer who treats the work as a burden is selling the job. A team that cannot explain where the candidate would land is selling the job. A rerouting decision nobody can explain is selling the job. A thoughtful rejection is selling the job too.

Interviewers sometimes need both the carrot and the stick. Better and different colleagues expand the team's perspective and fill product gaps it cannot see from inside itself. The wrong hire can become a negative multiplier whose confusion, avoidance, or weak judgment consumes the people around them.

That does not mean hiring only people who resemble the existing team. It means taking seriously that every hire changes what the team can notice, discuss, and produce.

The company is not only choosing a candidate. Throughout the process, it is providing evidence for or against the story it told them.

The job is the pitch. The interview reveals whether it is true.