How to Write a People-First Job Description That Screens for Values Before the First Interview

Every recruiter knows the feeling. You send a shortlist of three candidates to a client. Two get rejected after the first interview, not because they lacked skills but because they "did not feel like a fit." The client cannot articulate what was missing. They just knew it was not there.

That rejection did not start in the interview room. It started in the job description.

The typical job ad is a demand list. "Must have 5+ years of X. Proficiency in Y required. Expert-level Z." It reads like a procurement form, not an invitation. It tells candidates what to bring to the table but says nothing about who they will be working alongside or what kind of person thrives in that environment.

For a placement-conscious recruiter, this is a leverage point most of your competitors are ignoring. A better job description does not just fill a role faster. It fills it with someone who stays.

Why the standard job description is your biggest screening failure

Imagine screening 150 resumes because a client insisted on a laundry-list JD that attracted anyone with a pulse and a keyword match. Now imagine screening 40 resumes from candidates who read the same role described differently and self-selected in or out based on values.

The second scenario is not hypothetical. It is just uncommon because most recruiters write job descriptions the way they have always been written.

The problem compounds when you place someone who looked great on paper but washed out in month four because the company's actual working style clashed with what the JD implied. Your stick rate takes the hit. Your client relationship takes the hit. And the cost is invisible because nobody traces it back to the job ad.

The three signals a people-first JD sends that a traditional one does not

A values-forward job description does three things a skills-only JD cannot.

First, it signals who should not apply. Most JDs are afraid to repel anyone. A people-first JD names the environments and working styles that would frustrate someone. "You will spend most of your day on solo deep work with one structured standup" tells a collaboration junkie to self-select out before they waste your time.

Second, it describes the team, not just the role. Candidates join companies but they quit managers and teams. A short paragraph about the people they will work with, how they communicate, and what they care about gives candidates something to attach to beyond the compensation.

Third, it embeds values in the requirements themselves. Instead of "strong communication skills," write "you default to over-communicating in writing because you know async teams live or die on documentation." That sentence screens for a specific behavior, not a generic attribute.

A recruiter's template for the people-first JD

Here is a structure you can adapt for any client placement.

Opening: What this role actually does for the company. Skip the "we are a fast-growing innovative leader in the X space." Start with one sentence about the real problem this hire solves. "We are losing renewals because nobody owns post-sale onboarding end to end. This role exists to fix that."

Team snapshot. Three sentences. Who they report to. Who they collaborate with daily. How the team communicates. "You will report to the VP of Product, sit on a six-person team that works heads-down most of the day, and syncs in a 20-minute standup at 9:30. We use Notion for async updates and Slack for quick questions."

What success looks like at 90 days. Specific, observable outcomes. Not "hit the ground running." Try: "By month three, you will have mapped every step of the current onboarding flow, identified the top three friction points with data, and shipped one fix that measurably reduces time-to-value."

Values in practice. Instead of a bulleted list of corporate values nobody believes, describe what behaviors get rewarded and what behaviors get coached. "We celebrate people who flag problems before they have solutions. We coach people who wait for permission."

The honest trade-offs. This is the section most JDs skip and most candidates wish existed. Name the hard parts. "This is not a role for someone who needs a lot of face time with leadership. Your manager travels two weeks a month and you will need to drive your own priorities."

When you write a JD this way, you are not just describing a job. You are running a structured hiring scorecard before the first resume arrives. The candidates who apply have already self-screened on the criteria that matter most.

How to get clients on board

Some clients will push back. They will say you are limiting the pipeline. Here is the data-forward argument.

A recruiter who places on a standard JD might make three placements in a quarter with one washout. A recruiter who places on a values-forward JD might make two placements with zero washouts. The second recruiter has a better reputation, a stronger client relationship, and a higher effective hourly rate because they are not re-filling the same role for free.

Frame it as a competitive advantage. Tell the client: "Most candidates see twenty job descriptions a day that look identical. Ours will be the one that makes them stop scrolling because it actually describes the job they would be doing and the people they would be doing it with."

Better yet, show them. Take their current JD and rewrite it side by side. The difference is usually stark enough to make the case on its own.

One change you can make today

Next time a client sends you a JD, find the "requirements" section. Count how many bullet points describe skills and how many describe behaviors. If the ratio is 10-to-0, you have a demand list, not a job description.

Pick the three most important behaviors this hire actually needs. Rewrite those three bullet points as specific, observable behaviors. Send it back to the client with a note: "I tightened this up to attract the kind of person who will stick. Let me know if I misrepresented anything."

Most clients will not push back. The ones who do are usually the ones who do not know what they want, which is its own signal.

A job description is the cheapest screening tool in your stack. Most recruiters are not using it. The ones who do have shorter fill times, higher stick rates, and clients who trust them enough to stop shopping around.