Why Your Job Posting Isn't Attracting Good Candidates

You post a job. Applications start coming in.

Then you look at them.

Half of the applicants do not have the experience you need. The strongest candidates seem to disappear. Maybe you get plenty of applications but very few people you actually want to interview.

It is easy to blame the talent market.

Sometimes the problem starts much earlier.

Your job posting may be turning away the right people before you ever get a chance to speak with them.

A job posting is not just a list of duties. It is often a candidate's first real look at the opportunity. They want to know what the job is, what it pays, where they will work, what you expect, and what they get in return.

If they cannot figure those things out quickly, they can move on to the next opening.

Here are some of the most common reasons a job posting fails to attract the candidates an employer actually wants.

Your Job Title Makes Sense to You, Not to Candidates

Start with the title.

Companies often use internal titles that mean something inside the organization but almost nothing to the outside world.

Maybe your internal title is "Client Success Specialist II." Candidates may be searching for "Account Manager."

Maybe you call someone a "Growth Ninja." Qualified candidates are probably searching for "Digital Marketing Manager."

Indeed recommends using clear, standard job titles because candidates search for familiar terms. It advises employers to avoid internal jargon, excessive detail, promotional wording, and unusual titles that make the role harder to find or understand.

A clever title is not useful if the right person never sees the job.

Use the title candidates actually type into a search bar.

You can explain your internal title later.

Your Requirements Are Really a Wish List

Some job postings read as if five different managers added everything they would like to see in the perfect candidate.

Five years of experience.

Three software platforms.

A specific degree.

Industry experience.

Management experience.

A certification.

Excellent communication skills.

Then another ten bullets follow.

Before publishing that list, ask one question:

Does someone truly need every one of these things to do the job well?

If the answer is no, do not call all of them requirements.

LinkedIn has recommended limiting job postings to no more than six requirements and aiming for even fewer when possible. Its research also found that U.S. job posts mentioning responsibilities but not "requirements" received more applications per view.

That does not mean lowering your hiring standards.

It means separating what is necessary from what would simply be nice to have.

If a CPA license is required, say so.

If someone needs three years of industrial maintenance experience to work safely on your equipment, say so.

But if you can teach a software program in two weeks, think carefully before using it to eliminate otherwise strong candidates.

Employers often say they want people who can learn, solve problems, communicate, and grow. A job posting should leave room for those people to apply.

You Left Out the Salary

Candidates notice when pay is missing.

LinkedIn research found that 91% of U.S. respondents said including a salary range would affect their decision to apply. Other LinkedIn research has also found that salary information is one of the most important details candidates want to see in a job description.

Indeed now lists pay range among the key pieces of information employers should include in a job post.

There is a practical reason for this.

Candidates do not want to spend hours applying, interviewing, and completing assessments only to discover that the position pays $20,000 less than they need.

Employers should not want that either.

A clear, realistic range lets both sides make that decision earlier.

It can also help reduce applications from people whose compensation expectations do not match the role.

Pay transparency laws now apply in a growing number of jurisdictions, so employers should also check the rules that apply where the job can be performed.

Your Description Could Belong to Any Company

Consider this opening:

"Join our fast-paced, dynamic organization where we work hard and play hard. The ideal candidate will be a motivated self-starter who thrives in a collaborative environment."

What job did I just describe?

It could be sales. Accounting. Operations. Marketing. Software. Construction.

That is the problem.

Generic writing takes up space without helping someone decide whether the job is right for them.

Candidates want specifics.

What will this person actually do?

Who will they work with?

What problems will they solve?

What does a normal week look like?

What would success after six months look like?

Indeed recommends structuring descriptions around three basic areas: requirements, responsibilities, and rewards. It also recommends clear language, short paragraphs, and information candidates can scan quickly.

That is much more useful than a paragraph about being a "world-class organization."

Tell people about the actual job.

You Are Hiding the Information Candidates Care About

Salary is not the only thing candidates want to know.

Where is the job?

Is it remote, hybrid, or fully on-site?

What hours will they work?

Is there travel?

Is there weekend work?

What does the benefits package include?

Does the company offer health insurance? A 401(k)? PTO? Bonuses? Parental leave? Flexible hours?

"Competitive benefits" does not answer those questions.

Indeed identifies pay, benefits, shift information, location, qualifications, and whether the position is full- or part-time as core information employers should consider including.

You do not need to turn your posting into an employee handbook.

Just give candidates enough information to decide whether the opportunity fits their life.

That matters because the candidate is making a decision too.

I have written before about why employers should be comfortable letting candidates interview the company. A strong hiring process gives both sides enough information to decide whether the fit makes sense.

Your Application Takes Forever

You finally convinced a great candidate to click "Apply."

Do not lose them now.

One of the fastest ways to create frustration is to ask someone to upload a resume and then manually enter every job, date, employer, responsibility, and degree that already appears on that resume.

LinkedIn candidate-experience research has found that shorter applications tend to receive better ratings from candidates. Applications that take too long create another place for strong applicants to drop out.

The lesson is simple.

Every unnecessary field creates another place for someone to stop.

Ask for what you actually need at this stage.

You probably need contact information, a resume, and a few useful screening questions.

You probably do not need someone's complete employment history entered twice before you have even decided whether to call them.

Candidates already spend time thinking about how their resume will perform in an applicant tracking system. I covered that side of the process in my guide on how to get your resume past the ATS.

Employers should look at the same technology from the other side.

Your ATS should help you find talent. It should not become an obstacle that drives talent away.

You Are Asking Candidates to Sell Themselves Before You Sell the Job

There is an old style of job posting that sounds almost like a challenge.

"Do you have what it takes?"

"Only top performers should apply."

"Must be willing to go above and beyond."

I understand what employers are trying to communicate. They want driven people.

But qualified candidates have choices too.

The best job posting should make it clear what you expect while also explaining why a strong candidate would want the job.

What can they learn?

What kind of work will they own?

Is there room to grow?

Will they have a good manager?

What problem will they help solve?

What makes this opportunity different from the ten similar positions they saw today?

You are evaluating the candidate.

The candidate is evaluating you.

That continues once interviews begin. My article on what hiring managers are thinking during an interview explains one side of that conversation. Employers should remember that candidates are making many of the same judgments about them.

Your Job Posting and Hiring Process Tell Two Different Stories

A great job posting cannot fix a poor hiring process.

You can describe your company as fast-moving and responsive, but that message falls apart if you take three weeks to schedule the first call.

You can say employees have autonomy, then require six interviews for a mid-level position.

You can talk about communication and then leave candidates without an update for two weeks.

The experience after someone applies needs to support what you promised in the posting.

That starts with the first conversation.

A phone screen may feel informal to an employer, but the candidate is already evaluating the company. That is why I consider the phone screen a real interview. It is one of the first chances both sides get to test the fit.

Good recruiting does not stop when someone clicks Apply.

That is where it starts.

Do Not Buy More Visibility for a Bad Job Posting

When a job does not produce strong applicants, the immediate response is often to spend more money promoting it.

Sometimes that helps.

But more traffic will not fix a weak message.

Before increasing your recruiting budget, read the posting as if you had never heard of the company.

Check whether it answers the questions a serious candidate will have:

• Is the title clear and searchable?
• Can I tell what I would actually do?
• Are the true must-have qualifications obvious?
• Is the salary range listed?
• Do I know where and when I would work?
• Are the benefits explained clearly?
• Can I understand why this opportunity might be worth pursuing?
• Is the application simple enough to complete without wasting time?

If several answers are no, fix the posting first.

The Goal Is Not More Applications

This may be the most important point.

A successful job posting does not necessarily produce the largest pile of resumes.

It produces the right resumes.

Clear pay may cause some people not to apply. Good.

Clear location requirements may cause someone who wants fully remote work to leave. Good.

A precise description of the job may show someone that the work is not what they expected. That is also good.

Every person who makes an informed decision not to apply saves time for the candidate, recruiter, and hiring manager.

At the same time, the person who reads the posting and thinks, "This sounds exactly like what I'm looking for," is much more valuable than another random application in your ATS.

That is what a good job posting should do.

It should not try to appeal to everyone.

It should make the right opportunity clear to the right person.

And sometimes, attracting better candidates starts with something as simple as rewriting the job post.