The wrong way to write a job description — and why it is filtering out your best candidates before they apply.

A job description is usually written by someone who already knows what the role is. A hiring manager who has a clear picture of the person they want, the skills they need, and the experience that would make someone credible for the position. They sit down and write what they know. The result is a document that makes complete sense to them and systematically filters out the people they actually want to hire.

This is one of the most consistent patterns we see from the hiring side. Roles that sit open for months while the founding team insists the talent simply does not exist. Then we read the job description and the problem becomes obvious immediately. The role was never written to attract the right person. It was written to describe the ideal person, which are two entirely different documents.

What a job description is actually supposed to do

A job description has one job: convince the right person that this role is worth their time to pursue. That is it. It is not a compliance document. It is not a record of every task the person will ever do. It is not a wish list of qualifications that would make the hiring manager maximally comfortable. It is a piece of communication directed at a specific reader, and it succeeds or fails based on whether that reader finishes it and thinks yes, this is for me.

Strong candidates at the mid-to-senior level are not desperate. They have options. They read a job description the way a customer reads a product page: quickly, skeptically, and with a clear question in mind. Can I do this work, will it move my career forward, and does this company seem like a place where someone like me would thrive. If the job description does not answer those questions clearly and quickly, they move on.

Five ways job descriptions filter out strong candidates

Across the roles we have worked on at ConsultBae, five patterns appear repeatedly in job descriptions that struggle to attract strong applicants.

Requirements lists that describe a unicorn, not a person. Eight-plus years of experience. Proficiency in twelve tools. A track record in three different functions. A degree from a top institution. Each requirement feels reasonable in isolation. Together they describe someone who either does not exist or is already in a role better than the one being offered. Strong candidates read this list, count two or three gaps, and talk themselves out of applying. The candidates who apply anyway are often the ones who match every line on paper and not much else in practice.

Corporate language that signals the wrong culture. Phrases like "dynamic fast-paced environment," "self-starter," "wear many hats," and "competitive compensation" have been used so many times they have stopped meaning anything. To a strong candidate reading them, they signal one of two things: either the company has no distinct identity and is using borrowed language to fill space, or the company has a specific identity and is hiding it behind generic phrases. Neither reading encourages an application.

Scope that is so vague the role sounds undefined. "You will own growth." "You will drive strategic initiatives." "You will work cross-functionally to deliver outcomes." These descriptions tell the candidate nothing about what they will actually do on a Tuesday morning. A strong candidate who is evaluating whether this role is a genuine step forward in their career cannot make that assessment from a description this abstract. They cannot picture themselves in it, so they do not pursue it.

No information on compensation. Compensation opacity is one of the most reliable ways to lose strong candidates before a single conversation happens. Mid-to-senior candidates have a clear sense of their market value. When a job description offers no range, they assume either the range is below market or the company is not serious about transparency. Both assumptions lead to the same outcome: they do not apply, or they apply with low commitment and drop out the moment a better-specified opportunity appears.

A responsibilities list with no definition of what success looks like. Fifteen bullet points describing tasks tells a candidate what they will do. It says nothing about what winning looks like in this role, what the company actually needs from this person, or how this role connects to something that matters. Strong candidates at the senior level are not looking for a list of tasks. They are looking for a problem worth solving and evidence that this company has the clarity and environment to let them solve it.

What candidates actually read a job description for

A strong candidate reads a job description in under two minutes the first time. They are not reading every word. They are scanning for three things: whether the role is a real step forward for them, whether the company seems like a place where their kind of work is valued, and whether there are any signals that would make them immediately rule it out.

The signals that make strong candidates rule a role out fast are usually not the obvious ones. It is rarely the title or the sector. It is the writing. A job description written with genuine clarity and specificity signals that the company knows what it needs and respects the candidate enough to communicate it clearly. A job description that reads like it was assembled from templates signals the opposite, that nobody thought carefully about this communication, which makes a candidate wonder what else nobody thinks carefully about.

What a good job description looks like instead

A job description that consistently attracts strong candidates does a few things differently. It leads with the problem the role exists to solve, not with the company's founding story or a list of perks. It describes the scope in specific terms: what this person owns, what they do not own, and what the boundary conditions of the role actually are. It is honest about the stage of the company and what that means for this hire in practical terms. It defines success concretely, at 90 days and at a year. And it gives a compensation range, even a broad one, because transparency at this stage costs nothing and earns significant trust.

The requirements list is short and limited to things that are genuinely non-negotiable, not things that would be nice to have. The language is specific to this company and this role, not borrowed from a generic template. And it ends with something that tells the candidate why this particular role, at this particular company, at this particular moment is worth their attention.

How ConsultBae approaches this

At ConsultBae, one of the first things we do when we take on a new role is read the job description the company has drafted and identify where it is likely to lose the candidates they actually want. In most cases, there is work to do before we start sourcing.

We have seen the same pattern enough times to know it with confidence: a well-written job description does not just attract more candidates. It attracts different candidates. The ones who apply because they understood clearly what was being asked and decided it was worth pursuing. Those are the candidates who show up to conversations ready, move through the process with genuine intent, and when they get an offer, take it.

The job description is the first thing a candidate sees. In most cases it is also where the best ones quietly decide to look elsewhere. Fixing it costs nothing except the time it takes to think clearly about what the role actually is and who it is actually for.

Anubhav Sahay is part of the hiring team at ConsultBae, focused on mid-to-senior recruitment for funded startups across India.