The One Hiring Task That Takes 10 Minutes and Changes Everything
Most job descriptions are just a list of requirements. Here's what they're actually supposed to do — and how getting them right changes every step of hiring that follows.
Most job descriptions follow the same format. A paragraph about the company. A list of responsibilities. A list of required qualifications. Maybe a note about benefits. Posted to a job board, and the applications start coming in.
There's nothing technically wrong with this. It communicates the basics. But it's also doing almost none of the work a job description is actually supposed to do.
A job description isn't just a signal to candidates that you're hiring. It's the first step in defining what you're actually hiring for — and when that step is done badly, every step after it gets harder. You attract the wrong candidates, you ask the wrong questions in interviews, and you make decisions against criteria that were never clearly defined in the first place.
Getting this right takes about ten minutes. And it changes more of what follows than almost anything else in the hiring process.
What most job descriptions actually say
Take a typical job description for a Sales Associate role at a small retail or service business. It probably says something like:
"We're looking for a motivated, customer-focused team player who can work in a fast-paced environment. Responsibilities include managing customer inquiries, processing transactions, maintaining store appearance, and supporting team members. Requirements: 1-2 years of experience in a customer-facing role, strong communication skills, ability to work weekends."
Candidates read this and nod. It sounds reasonable. It sounds like most job descriptions they've seen.
But the person writing it hasn't answered the questions that actually matter:
- How much autonomy does this role require on day one?
- What does it look like when someone succeeds here in the first 90 days — specifically?
- What pattern of behaviour has caused people to fail in this role before?
- How does the team communicate, and does this candidate need to match that style to fit?
None of that is in the description. Which means the hiring process that follows is built on a foundation of vague requirements, and the decision at the end of it is inevitably more gut-based than it needs to be.
The three things a useful job description actually does
1. It describes the work, not just the role
There's a difference between a list of responsibilities and a description of what the work actually involves day to day.
"Managing customer inquiries" tells a candidate what the job category is. It doesn't tell them that this is a high-volume environment where they'll be handling fifteen interactions an hour with minimal supervisor availability, where they'll need to make judgment calls independently rather than escalating everything. That's a different role than one where inquiries come in slowly and a manager is always nearby.
The more specifically you describe what the work actually looks like, the better the self-selection you get. Candidates who would struggle in your environment opt out before you have to figure it out in an interview. Candidates who would thrive recognize themselves in the description and apply.
2. It defines success, not just requirements
"1-2 years of experience" tells you roughly what someone has done before. It tells you very little about whether they'll succeed in this specific role.
A useful job description goes further: what does success look like at 30 days? At 90? What would make you, three months in, say that this hire worked?
For that Sales Associate role, success at 90 days might look like: completes their task list independently without needing reminders, has learned the team's informal communication norms and operates within them, handles the busy period without freezing or needing constant direction.
Those are specific, observable outcomes. They're very different from "strong communication skills." And they become the criteria against which you actually evaluate candidates — which makes the interview far more productive.
3. It signals what the culture actually is — not what you want it to sound like
This is where most job descriptions go most wrong.
"Fast-paced environment, team player, passionate about delivering exceptional customer experiences" appears in approximately every job description ever written. It signals nothing, because every company says this.
What actually signals something: being specific about how the team works. "We communicate informally and quickly — people ask questions directly rather than waiting for meetings or sending long emails. If you work best with formal processes and written procedures, this probably isn't the right fit."
That level of specificity will turn some candidates off. That's the point. The ones who read it and think "that sounds exactly like how I prefer to work" are the ones you want.
The part most people skip: failure signals
Here's the question almost no job description answers — and almost no hiring process formally asks: what does failure look like here?
Not catastrophic failure. The more common kind. The employee who seemed fine in the interview but three months in is constantly needing reminders, or frequently overwhelmed by pace, or creating friction because their working style conflicts with the team's.
If you've seen this pattern before, you know what it looks like. Articulating it — even just for yourself, before you start interviewing — changes what you look for.
For the same Sales Associate role: someone who fails here typically asks for clarification repeatedly on tasks they've already been shown, needs a lot of reassurance before acting independently, or prefers formal structure in an environment that doesn't have it. That's not a bad employee. It's a mismatch.
When you know what mismatch looks like, you can design your interview to surface it before the hire — not discover it after.
You don't need a polished document
One misconception about getting job descriptions right is that it requires significant time or HR expertise. It doesn't.
The questions you need to answer before you start hiring are:
- What does the work actually look like day to day?
- What does success look like at 90 days — specifically?
- What pattern of behaviour has caused problems in this role before?
- How much autonomy does this role require from the start?
- How does your team actually communicate and work together?
Even rough answers to these questions — a few sentences each — give you more to work with than a polished list of requirements. You can always clean up the language for the job posting. The substance is what matters.
This is exactly what TeamSyncAI's calibration process walks you through. In about five minutes, it asks you the questions that produce the inputs for a complete hiring system — interview questions, evaluation criteria, success indicators — all calibrated to the specific reality of your role and team.
The job description you post to candidates is the public-facing version. The calibration that drives your interview process is the part that actually makes the hire.