How to Write a Job Post That Gets Responses

The most common reason a small business job post gets no good responses is not the role - it is the post. A vague, jargon-filled, copy-pasted description tells candidates almost nothing about what the job is actually like, and nothing about why they should choose your business over the fifty other listings they are looking at this week.

Writing a good job post takes about an hour and makes a real difference in the quality and volume of applications. This guide walks through what to include, what to cut, and a few mistakes that quietly kill response rates.

Think of it as a recruiting ad, not a legal document

A job description is internal. It defines the role for HR purposes, includes all the responsibilities, all the competencies, all the requirements. It is thorough and complete. It is also exhausting to read.

A job post is different. It is a public recruiting ad. Its job is to get the right people to apply and discourage everyone else. It should be short enough to read on a phone in two minutes. It should sound like a real person wrote it, not a committee. It should answer the question every candidate is silently asking: why would I want this job?

The simplest test: show your draft to someone who has never heard of this role. If they could tell you what the job actually involves after reading it, you are on the right track. If they shrug, keep cutting until it is clearer.

What to include in every job post

A specific, honest job title

Job titles affect search results on Indeed, LinkedIn, and Google for Jobs. Use the title candidates will actually search for, not an internal title that only makes sense inside your business. “Customer Service Representative” is better than “Guest Experience Lead Level II.”

Keep the title to five words or fewer. Avoid jargon. Avoid using words like “ninja,” “guru,” or “rockstar” - they filter out serious candidates.

The pay range

Including a pay range is now required by law in several US states. Beyond legal compliance, it is also just the right thing to do - it saves everyone time. Posts with pay ranges consistently get more applications from candidates who are actually a fit, because people who need more will move on early rather than wasting an interview slot.

If you are not sure what to pay, research comparable roles in your area on Indeed or Glassdoor before you post. Offering below market is fine if you are transparent about trade-offs (flexibility, training, growth). Hiding a below-market rate until the final interview is how you poison your hiring experience.

Location, hours, and work type

Be explicit: full-time or part-time, on-site or remote or hybrid, specific hours if they matter. If the role requires weekends, say so. If it is flexible, say that instead. Candidates are filtering for these things immediately, and ambiguity makes them skip your listing rather than ask.

What the person will actually do

This is the section most job posts get wrong. Bullet lists of generic responsibilities - “manage customer relationships,” “support team initiatives,” “drive results” - tell candidates nothing.

Instead, describe what a typical week looks like in concrete terms. Write in plain language. Be specific about what takes most of the person’s time.

A few examples of the difference:

• Vague: Provide excellent customer service in a fast-paced environment. Better: Help 20–30 customers per day at the front counter - answering questions, processing returns, and resolving issues calmly.
• Vague: Assist with general administrative tasks. Better: Manage our inbox, schedule service calls, and update customer records in our CRM - about half your time.
• Vague: Support the team in achieving sales goals. Better: Follow up on quotes, book appointments, and track where leads are in the pipeline.

What you actually require

Keep the requirements list short and honest. Every unnecessary requirement you add shrinks your candidate pool. The oft-cited research on gender gaps in applications - where women tend to apply only when they meet almost all listed requirements while men apply when they meet far fewer - is a real consideration. If something is a genuine hard requirement, say so. If it is nice-to-have, either leave it out or label it clearly.

Do not list years-of-experience requirements unless they are genuinely meaningful. “5+ years required” for an entry-level role is a red flag to experienced candidates that you do not know what you are hiring for.

One or two genuine selling points

Candidates are choosing you as much as you are choosing them. Give them a real reason to apply to your business rather than the one listed next to yours on Indeed.

This does not need to be extravagant. Honest is better than impressive. Some things that actually matter to candidates: flexible scheduling, a team that has worked together for a long time, a clear learning path, an owner who is present and accessible, genuine autonomy in the role. Whatever is genuinely true about working at your business - say it plainly.

What to cut

Most job posts are 30–40% longer than they need to be. Cut ruthlessly.

• Boilerplate about your company mission. A two-paragraph corporate mission statement in a job post for a part-time front desk role adds nothing. One sentence about what your business does is enough.
• Responsibilities that apply to every job. “Maintain a positive attitude” and “work well independently and on a team” are not distinguishing requirements. Delete them.
• Requirements you would actually waive for the right person. If you list “Bachelor’s degree required” but would hire a strong candidate without one, remove it. You are filtering out good people for no reason.
• Legal disclaimers in the body of the post. EEO statements and background-check notices belong at the bottom, not woven into the description where they add length and formality that signals bureaucracy.

Formatting: short, scannable, mobile-first

The majority of job seekers browse listings on their phone. Write accordingly. Short paragraphs. Bullet lists for responsibilities and requirements. A clear structure: role summary → what you’ll do → what we’re looking for → pay and hours → why us → how to apply.

Aim for under 500 words for most roles. Under 400 is better. A clean, readable post that covers the essentials will outperform a comprehensive one that nobody finishes.

Where to post it

For most small business roles, start with Indeed - it has the widest reach for hourly and local roles. Add LinkedIn if you are hiring for professional or skilled positions. Google for Jobs picks up your listing automatically when your job post is structured correctly, which a good applicant tracking system handles for you.

For niche roles, think about where candidates in that field actually look. Trades workers find jobs through local Facebook groups and industry-specific boards. Restaurants have dedicated platforms. Healthcare roles have specialty boards. Do not assume Indeed covers everything.

After the post goes live

Check the response rate in the first 48 hours. If you are getting applications but they are mostly unqualified, the post is attracting too broad an audience - tighten the requirements section. If you are getting almost no applications, the post may be too restrictive, or the pay range may be below market for your area.

Job posts are not permanent. Updating a post is normal. Rewrite the title or the opening paragraph and repost if things are slow - the algorithm on most job boards treats a repost as a new listing.