Job Posting Examples: 4 Complete Samples You Can Copy
Four complete job posting examples for small businesses, each under 300 words, plus what to include and how to compete without a known brand.
Job Posting Examples
Four complete, copy-ready postings written for businesses nobody has heard of: a cafe, a dental practice, a twelve person software company making its first support hire, and a family HVAC shop. Plus the seven elements that belong in every posting, why every example here is deliberately under three hundred words, how to use a pay range as a competitive weapon, and the line-by-line rewrite that fixes a weak posting
Every list of job posting examples uses the same companies. A software giant with a famous careers page, an energy drink brand with a clever headline, a retailer with a marketing department. The postings are genuinely good and none of them are reproducible by a business with eleven employees and no brand recognition.
So the examples below are the other kind. A six-person cafe. A two-dentist practice. A twelve-person software company making its first support hire. A family HVAC shop. All four are complete and copy-ready rather than fill-in templates, and all four are deliberately under three hundred words, because a large analysis of job posts found that postings in the one to three hundred word range attracted applications at a rate meaningfully above average while longer ones fell below it.
That length constraint is the first thing most published examples get wrong. This guide covers the seven elements that belong in a posting, the four examples themselves, how to compete for people without a known name, why a pay range is the strongest lever a small employer has, a line-by-line rewrite that fixes a weak posting, and what the law actually requires. I build hiring and onboarding tooling at FirstHR, and everything here works with a text file and an email address.
What a Job Posting Is
A job posting is the public advertisement for an open role: the document a candidate reads when deciding whether to apply. Its job is persuasion and filtering, in that order.
Two jobs, and they pull in opposite directions. Persuasion argues for saying more about why the role is good. Filtering argues for stating requirements clearly so the wrong people do not apply. The resolution is not balance but sequence: be specific and honest about the role, and the filtering happens by itself because people who would not enjoy it will not apply.
Posting vs Description
A job description is an internal document. A job posting is an advertisement. Posting the description verbatim is the most common failure in this area and produces a document nobody finishes reading.
| Job description | Job posting | |
|---|---|---|
| Audience | Internal: HR, managers, compensation | External: the candidate deciding whether to apply |
| Purpose | Define the role and its boundaries | Persuade the right person to apply |
| Length | As long as needed, often 800 to 1,500 words | Under 300 words performs best |
| Duties | Comprehensive, including rare ones | The five to seven that fill the week |
| Tone | Neutral and precise | Direct and human |
| Compensation | Internal band and classification | The range you will publish |
| Lifespan | Reviewed annually | Rewritten every time you hire |
| Contains | Reporting lines, classification, physical requirements | What it is like, what it pays, what happens next |
The two also differ in what they contain about the role itself. A description enumerates roles and responsibilities in full, including the ones that come up twice a year, while a posting keeps only what fills the week.
Write the description first if you do not have one, because it forces the decisions that make the posting easy: what the role actually covers, what is genuinely required, and how it is classified.
What to Include
Seven elements, and the last one is the one almost nobody includes.
Note what is not on the list. A long company description does not belong at the top; it belongs after the person knows what the job is, if at all. Neither does a mission statement, a values list, or the phrase fast-paced environment, which candidates have correctly learned to read as understaffed.
Four Complete Examples
Each of these is a finished posting rather than a template with brackets in it. Names and details are invented; the structure, the length, and the specificity are the point. Every one is under three hundred words.
What makes this one work is the honesty about the actual requirement. The genuine must-have is showing up at 6:15 reliably, and saying so filters more usefully than any list of skills would. It also states the tip average from a real quarter rather than saying tips are great, which is the difference between a claim and information.
The line about the previous coordinator staying seven years does more work than any culture paragraph could. It is a verifiable fact that implies stability, and a candidate who has been through three bad front desk jobs will notice it immediately. Closed most Fridays, stated as genuinely closed rather than on call, is the same move.
This one admits that the current situation is not going well. That is a deliberate choice and it works, because the candidate for a first-in-function role is usually someone who wants to build something rather than inherit it. Naming the actual ticket volume also pre-qualifies: anyone who finds thirty a day alarming has just self-selected out, at no cost to either party.
The on-call line is the one that will get this posting read twice. One week in seven rather than one in three is a specific, checkable competitive claim in a trade where on-call frequency is a primary reason people leave. Paying for NATE certification is the same category: a concrete benefit stated as a number rather than as an intention.
Across all four, notice the section nobody else includes: what happens after you apply, with a response time attached. It is free, it is checkable, and in a stack of thirty postings it is frequently the only one that answers the question every applicant has.
Competing Without a Brand
The advice in most articles assumes brand recognition does some of the work. If nobody has heard of you, specificity has to do it instead, and specificity is something a small employer can produce more easily than a large one.
| What large employers write | What a small employer should write instead | Why it works |
|---|---|---|
| Join our dynamic team | You would be the ninth person here | Verifiable, and it tells them the scale immediately |
| Competitive compensation | $21 to $25 an hour depending on experience | A range removes the assumption that you pay badly |
| Great benefits package | 80% of the employee health premium, two weeks off in year one | Specific numbers can be compared; adjectives cannot |
| Opportunities for growth | The last person in this role now runs the department | A fact rather than a promise |
| Fast-paced environment | Busiest three hours are 7:00 to 10:00 | Says the same thing without the euphemism candidates distrust |
| Work-life balance | Schedule published two weeks ahead, no clopening | A policy rather than a value |
| Report to leadership | You would work directly with both founders | At twelve people this is true and it is genuinely attractive |
The scale point is worth stating too. Federal business size statistics place the overwhelming majority of US employer firms in the smallest bands, which means the typical person writing a job posting works somewhere nobody has heard of. The examples built around famous brands are the exception being presented as the rule.
The pattern is that every phrase a large company uses because it must apply across thousands of people can be replaced by a specific fact that only you can state. That is the actual advantage of being small, and most small business postings throw it away by imitating the language of the companies they are competing against.
Three things a small employer can offer that a large one structurally cannot: proximity to the person making decisions, visible consequence of the work, and flexibility that does not require a policy exception. Say all three concretely.
Pay as an Advantage
Publishing a pay range is the single highest-return change most small employers can make to a posting, and the strategic case is stronger than the compliance one.
The wider labor market context is worth a glance before deciding how aggressive to be. Federal job openings and labor turnover data tracks openings and hires monthly, and the gap between them tells you whether a slow-filling role reflects your posting or the market you are posting into.
Three findings converge here. Survey research has found that a substantial share of candidates, in the region of forty percent, declined to apply to roles that did not list a range. Analyses of application volume associate published pay with materially higher application counts. And candidates consistently report compensation as the first thing they look for when reading a posting, ahead of qualifications and job details.
The practical objections are real and each has an answer. If you worry about existing employees seeing the range, that is a signal worth acting on independently, and it is a conversation you will have eventually whether or not you post. If you worry about anchoring high, publish a genuine band rather than a single number and be prepared to explain what moves someone within it. If you do not know your band, that is a reason to work out your salary bands before hiring rather than a reason to omit the range.
The compliance layer is moving quickly and is covered separately in our guide to pay transparency laws. The short version is that a growing number of states require a range in the posting, some extend the obligation to listings placed by third parties, and penalties in a few states are assessed per violation.
How Long It Should Be
Shorter than you think, and shorter than nearly every published example. This is the finding that most contradicts standard practice.
| Posting length | What research associates with it | What it feels like to read |
|---|---|---|
| Under 300 words | Apply rates above average by several percentage points | Scannable in under a minute, which is how long people spend |
| 300 to 600 words | Apply rates below average | Complete, and roughly twice as long as anyone reads |
| Over 600 words | Weaker still | An internal document that escaped |
Eye tracking research puts the time a job seeker spends on a posting well under two minutes, with a fraction of that on the qualifications section, and survey work finds that a large share never read the description in full. Writing nine hundred words does not convey more; it moves the important parts below the point where people stop.
The compression is mostly subtraction of three things: the company paragraph at the top, duties that occupy under five percent of the week, and requirements you would waive for a strong candidate. Removing those three usually gets a nine hundred word posting under three hundred without losing anything a candidate needed.
Fixing a Weak Posting
Rather than a good-versus-bad pair of full documents, here is the line-by-line version, which is what you would actually do to a posting you already have.
| The weak line | The problem | The rewrite |
|---|---|---|
| Rockstar Sales Ninja wanted | Nobody searches this. The posting is invisible | Sales Representative, Inside Sales |
| Salary: DOE | Reads as unwilling to say, and is unlawful in several states | $52,000 to $64,000 base plus commission |
| Location: Flexible | Produces applications you will reject on geography | Hybrid, three days a week in our Tacoma office |
| Must be a self-starter with a can-do attitude | Describes nothing and filters nobody | You will run your own pipeline with no daily check-ins |
| 5+ years experience required | Filters out people who can do the job | Two years of B2B sales, or a strong case for why not |
| Bachelor's degree required | Often a proxy nobody has examined | Remove unless the role genuinely requires it |
| Other duties as assigned | Signals that the list is incomplete | Delete. It reassures nobody and worries some |
| Competitive benefits package | The most common empty phrase in hiring | Health at 80%, three weeks off, $1,000 learning budget |
| We are a fast-paced environment | Widely read as understaffed | Peak season runs March to June and we staff up for it |
| No response time mentioned | The most common omission of all | We reply to every applicant within five business days |
Two of these rows carry legal weight rather than just persuasive weight. Withholding pay in a state that requires it is a violation with a penalty attached, and requirements that function as proxies for age or other protected characteristics create exposure covered in the next section.
The Legal Requirements
Most examples pages skip this entirely. Three categories cover what a small employer needs to know before publishing.
| Requirement | Where it applies | What it means in practice |
|---|---|---|
| Pay range in the posting | Sixteen states plus Washington DC, with variation | State the range. Some states extend the duty to third-party listings |
| No preference by protected characteristic | Federal, and everywhere | Avoid wording that signals age, sex, national origin, disability, or religion |
| Indirect age-coded wording | Federal age discrimination law | Recent graduate, digital native, and young energetic team all create exposure |
| Equal opportunity statement | Required for federal contractors, standard practice otherwise | One sentence at the end of the posting |
| Accurate description of the role | General | A posting that misdescribes the job produces early turnover, not liability, but it is expensive either way |
| Accessibility of the application | Federal disability law | If the only way to apply is a system someone cannot use, that is a problem |
The third row is the one that catches well-intentioned employers. Phrases like recent graduate or digital native read as descriptive and function as age filters, and the same logic reaches wording that implies physical characteristics not required by the job. The safe test is whether the phrase describes the work or describes the person, and there is a fuller treatment of the same principle in our guide to questions you cannot ask in an interview.
On evidence for the wording debate more broadly, it is worth knowing the field is contested. One large industry analysis reported substantially more applications for gender-neutral wording, while research published in Management Science by researchers at MIT Sloan and Michigan State, covering roughly 296,000 postings and 487,000 job seekers, found the effects of altering gendered language too small to matter in practice. Plain, specific writing is defensible on its own merits without needing either finding to be true.
Where You Post It
The same posting does not work everywhere, and the adjustments are small.
| Channel | What to change | What matters most there |
|---|---|---|
| A general job board | Nothing structural. Keep the title plain and searchable | Title match and the pay range, since both are filterable |
| Your own careers page | Add the longer company context that does not belong on a board | Someone here has already decided to look at you specifically |
| A professional network post | Rewrite as a short personal note from the hiring manager, link out for the rest | The personal voice, since it is a social feed rather than a search result |
| A local or trade board | Emphasize location, schedule, and pay above everything | Practical fit. People browsing these are often already working |
| A referral message to your team | One paragraph plus the link, and say what a good referral looks like | Clarity about who you want, since your team is doing the filtering |
For a small employer the referral row usually outperforms the others and gets the least attention. A team of fifteen has a larger relevant network than the business does, and a specific ask outperforms a general one substantially.
Whichever channel, the posting needs somewhere for the application to land that you actually check. The most common failure in small business hiring is not the posting at all, it is a good applicant waiting eleven days for a reply, and it is the reason a response time promise in the posting is worth making only if you can keep it.
Common Mistakes
The failures are consistent and most of them are additions rather than omissions.
| Mistake | Why it happens | The fix |
|---|---|---|
| Posting the internal job description | It already exists and looks thorough | Compress to the seven elements. Under 300 words |
| A creative job title | It feels like personality | Use the title people search. Save the personality for the body |
| Omitting the pay range | It feels like losing negotiating room | Publish a band. Candidates assume worse than your actual number |
| Ten requirements | Each one seemed reasonable in isolation | Three or four must-haves, preferences labeled separately |
| Leading with four paragraphs about the company | It is the part you know best | The candidate wants to know what the job is first |
| Competitive pay and great benefits | Every posting says it | Numbers. A percentage, a dollar figure, a count of days |
| Copying a large company's posting | Their posting looks professional | Their advantage is brand. Yours is specificity. Different tools |
| No indication of what happens next | Nobody thinks to include it | One line with a response time you will honor |
| Leaving the posting up after you fill it | It stops being anyone's job | Take it down. Applications into a void damage more than they cost |
The last row is worth an explicit habit. Postings left up after a role is filled generate applications that nobody answers, and the person who applied has a specific and lasting impression of your company as a result. In a small local market that impression circulates, and it costs you candidates for the next role rather than this one.
None of this requires a recruiter or a tool. It requires seven elements, three hundred words, a real number for the pay, and a response time you can keep. The four examples above are there to be copied and adapted, and if you are hiring for the first time our guide to hiring your first employee covers everything that happens after the posting goes up.
Frequently Asked Questions
What is an example of a job posting?
A job posting is the public advertisement for an open role, and a good one contains a searchable job title, the location and work arrangement, a pay range, five to seven lines describing what the person will actually do, a short list of genuine requirements separated from preferences, concrete benefits, and an explanation of what happens after someone applies. This article contains four complete examples written for small employers rather than large brands, each one under three hundred words and ready to adapt.
What is the difference between a job posting and a job description?
A job description is an internal document defining a role: full duties, reporting lines, requirements, and often compensation banding and classification. A job posting is the external advertisement derived from it, written to persuade rather than to define. Posting the internal description verbatim is the most common mistake in this area, because a document written for HR filing purposes reads as long, generic, and cold to the person deciding whether to apply.
What should a job posting include?
Seven things: a job title people actually search for, the precise location and work arrangement, a pay range, a short list of what the person will do ordered by time spent, three or four genuine requirements with preferences separated out, concrete benefits rather than the word competitive, and a description of the hiring process including when you will respond. The last one is almost never included and is one of the cheapest ways to stand out.
How long should a job posting be?
Short. A large analysis of job posts found that those in the one to three hundred word range attracted applications at a rate several percentage points above average, while longer postings underperformed. Eye tracking research shows candidates spend well under two minutes reviewing a posting, and a substantial share never read the full description. Every example in this article is deliberately under three hundred words, which is roughly half the length of a typical published sample.
Should you include salary in a job posting?
Yes, and increasingly you must. Survey research has found a large share of candidates decline to apply to postings without a pay range, and analyses of application volume consistently associate published pay with materially more applicants. Sixteen states plus Washington DC now have pay transparency requirements, with penalties in some states running from hundreds to thousands of dollars per violation. For a small employer the strategic case is stronger than the legal one: a range removes the assumption that you pay badly.
How do you write a job posting for a small business nobody has heard of?
Lead with the things a large employer cannot offer and stop trying to sound like one. Say how many people work there, who the person will report to, and what the team actually does. Name the concrete advantages: direct access to the owner, a schedule published in advance, no layers of approval, work that visibly matters. A specific description of a twelve person company beats a generic description of a great culture, because the first is verifiable and the second is what everyone writes.
Does gender-neutral wording in job postings actually work?
The evidence is genuinely mixed and worth knowing both sides of. One large industry analysis of hundreds of thousands of postings reported substantially more applications per job for gender-neutral wording. However, research published in Management Science by scholars at MIT Sloan and Michigan State, analyzing roughly 296,000 postings and 487,000 job seekers, found the effects of altering gendered language were too small to matter in practice. Plain, specific writing is defensible on its own merits regardless of which finding holds.
What legally has to be in a job posting?
There is no federal requirement to post a salary, but a growing number of states and cities require a pay range in the posting, and some extend the requirement to third-party listings. Postings must not express preferences based on protected characteristics, which reaches indirect wording such as recent graduate or digital native. An equal opportunity statement is standard practice and required for federal contractors. Requirements vary by state, so confirm your own before publishing.
How many applications should a job posting get?
It varies enormously by role, location, and pay, and the number matters far less than the fit of who applies. A posting attracting two hundred unqualified applicants is worse than one attracting eight people who can do the job, because the first consumes screening time you do not have. If volume is low, the usual causes are a title nobody searches for, no pay range, or requirements that filter out people who could do the work.