Most job descriptions are a list of duties and a salary range. They attract everyone and filter for no one. The result is 40 applications from people who aren't a fit, three interviews with candidates who seemed promising, and a hire that doesn't work out in 90 days. Here's how to use AI to write a job description that does the filtering for you.

A job description is the first test a candidate takes — and most businesses don't realize they're the ones failing it. Vague descriptions attract vague candidates. Descriptions written around the role instead of the person produce applicants who can do the job on paper but won't thrive in your environment. This issue walks through the AI workflow for writing a job description that communicates your culture, filters for the traits that actually matter, and attracts candidates who self-select in — or out — before you spend a single hour on interviews.

Within 60 days it was clear the hire wasn't a fit — not because of skill, but because of pace, communication style, and tolerance for ambiguity. None of those things were in the job description. None of them came up in the interview until it was too late.

The job description described what the person would do. It said nothing about how the business operated, what a hard week looked like, what kind of person thrived there, or what kind didn't. The wrong candidates couldn't filter themselves out because they didn't have the information to do it.

Five steps from blank page to a post that filters for fit before the first interview.

Step 1 — Define the person before you define the role (15 minutes).

Before opening Claude, answer these four questions in writing:

What does a great day look like for this person?

What does a hard week look like — and would the right person handle it without escalating?

What's one trait that's made a past hire fail in this role?

What's one trait that's made a past hire succeed that never shows up on a resume?

These answers are the raw material. Without them, Claude generates a generic description. With them, it generates a filter.

Step 2 — Generate the first draft with Claude (15 minutes).

Use this prompt:

"I'm hiring a [role title] for a [business type] in [city]. Here's what I know about the right person for this role: [paste your four answers]. Write a job description that leads with the culture and environment of the business, describes what a typical week looks like in honest terms, lists the three to five non-negotiable traits the right person will have, and ends with a clear application instruction. Do not write a generic list of duties. Write to the person who is perfect for this job and would recognize themselves in it."

Read the first draft out loud. If it sounds like it could have been written for any business in your category, go back to Step 1 and add more specificity.

Step 3 — Add a filter question to the application (5 minutes).

The single highest-leverage addition to any job posting is one specific question that requires a real answer. Use this Claude prompt:

"Based on this job description: [paste draft], write one application question that a qualified, culture-fit candidate would answer specifically and enthusiastically, and that a poor-fit candidate would either skip or answer generically. The question should reveal work style, values, or problem-solving approach — not just experience."

Add this question to the application and state clearly: applications without an answer will not be reviewed. This alone cuts unqualified applicants by half.

Step 4 — Write a culture paragraph that does the real filtering (10 minutes).

Most job descriptions list perks. A culture paragraph describes the environment honestly — including the parts that aren't for everyone. Use this prompt:

"Write a four to five sentence culture paragraph for a [business type] that honestly describes the pace, the communication style, the expectations, and what kind of person thrives here versus what kind of person would find it frustrating. Don't oversell it. The goal is to attract the right person and give the wrong person a reason to move on."

An honest culture paragraph filters out candidates who would have left in 90 days. That saves more time than any interview process.

Step 5 — Post and track response quality, not volume (ongoing).

When applications come in, sort them into three buckets before reading resumes: answered the filter question specifically, answered it generically, or didn't answer it. Only read resumes from the first bucket. Track how many applications you receive versus how many make it to an interview. Over time, a tighter description produces fewer but better applications — that's the goal.

1. Lead with the environment, not the duties.

The first thing a strong candidate wants to know isn't what they'll do — it's whether they'll want to do it here. Lead your job description with two to three sentences about what the business is, how it operates, and what kind of work week is normal. Candidates who are excited by that description will read everything else. Candidates who aren't will move on — which is exactly what you want.

2. Name the traits you can't train.

Skills can be taught. Work ethic, communication style, and how someone handles ambiguity usually can't — at least not quickly. Identify the two or three non-trainable traits that have made past hires succeed or fail and name them explicitly in the description. "You thrive when the plan changes mid-morning" is more useful than "must be adaptable."

3. Be honest about the hard parts.

The fastest way to a bad hire is a job description that only describes the good days. If the role involves early mornings, last-minute schedule changes, or clients who need frequent reassurance, say so. The right candidate will read that and see a challenge. The wrong candidate will read it and self-select out before you spend an hour on their interview.

4. One filter question beats ten interview questions.

A single well-designed application question reveals more about a candidate than most first interviews. It shows whether they read carefully, whether they can communicate in writing, and whether their answer reflects the values you described in the posting. Design it around a real scenario from the role — not a generic "tell me about a challenge you overcame."

5. Rewrite it every time you post it.

A job description that worked six months ago attracted candidates from six months ago. Your business changes. Your needs change. Run the workflow fresh every time you hire, especially if the last hire didn't work out. The description that produced the wrong candidate is usually part of the reason.

Beyond the Bid Circle is a peer community for builders scaling with systems and AI—the same builders who've escaped the 60-hour grind. Swap war stories, shortcuts, and real strategies with people who get it.