Job Description Examples for Small Business Roles (Five Full Examples)
A good small business job description names the outcome of the role, lists the daily work in plain words, separates must-haves from nice-to-haves, states pay and hours, and describes the company honestly. This guide gives five full examples for a receptionist, bookkeeper, sales representative, operations coordinator and junior developer, each annotated, plus a weak one rewritten.
Why small businesses need a better job description
A small business cannot afford a bad hire or a long search. The job description is the first thing a candidate reads and the document the whole hiring process is measured against. If it is vague, you attract the wrong people and waste time reading their CVs. If it is bloated with a wish list, good people talk themselves out of applying. If it hides the pay, many will not bother. A strong description does four things. It tells the right person what success looks like. It tells the wrong person early that this is not for them. It gives you the criteria to screen and interview consistently. And it gives you something to point to when a manager and a candidate disagree about what the job was. The five examples here are written for roles small businesses hire most. Each is followed by notes on what makes it work. Replace the details in [brackets] with your own, and cut anything that is not true for your company. For a blank structure to copy, see /job-description-template. Rules on pay disclosure, protected characteristics and wording differ by country, so check local law.
Example 1: receptionist
Title: Receptionist, [Company name], [Location]. About us: [Two sentences on what the company does and the size of the team]. The role: You are the first person clients and visitors meet, and you keep the front of the business running smoothly. Hours: [Days and times], [Part-time or full-time]. Pay: [Amount and period]. What you will do: Greet visitors and answer phone calls, directing them to the right person. Manage the shared inbox and sort messages the same day. Book appointments and meeting rooms in [Calendar tool]. Receive deliveries and handle post. Keep reception tidy and stock basic supplies. Support the team with simple admin such as filing and data entry. Must have: Clear spoken and written English [or relevant language]. Comfortable using email and calendar tools. A calm, friendly manner with people. Reliable attendance. Nice to have: Experience on a switchboard or booking system. A second language. What a good first six months looks like: Every call answered within [Number] rings, the appointment diary has no double bookings, and the team trusts you to handle visitors without help. How to apply: [Method and deadline]. Annotation: it opens with the purpose, it names tools and hours, and it describes success in a way you can test later.
Example 2: bookkeeper
Title: Bookkeeper (part-time), [Company name], [Location or remote]. About us: [Two sentences]. The role: You keep our financial records accurate and up to date so the owner and our accountant can make decisions and file on time. Hours: [Hours per week]. Pay: [Amount and period]. What you will do: Record sales, purchases and expenses in [Accounting software] weekly. Reconcile bank and card accounts monthly. Raise customer invoices and chase overdue payments. Process supplier bills and prepare payment runs for approval. Prepare a simple monthly report of cash, income and costs. Prepare information for the accountant for tax and year-end. Keep records organised and secure. Must have: Practical bookkeeping experience in a small business. Skill with [Accounting software]. Accuracy and attention to detail. Discretion with confidential information. Nice to have: A bookkeeping qualification. Experience with payroll or sales tax returns in [Country]. Success in six months: Monthly accounts closed within [Number] working days of month end, bank accounts reconciled with no unexplained items, and overdue invoices below an agreed level. Annotation: it measures success in tasks and timing, not just in personality, and it names the software, which filters applicants honestly. Check local rules on qualifications and tax roles before listing them.
Example 3: sales representative
Title: Sales Representative, [Company name], [Location or remote]. About us: [Two sentences on the product and who buys it]. The role: You find and win new customers for [Product or service] and grow the accounts you win. Hours: [Full-time]. Pay: Base [Amount] plus commission [Explain how it is calculated, with an example], total expected earnings for a typical performer: [Honest range or note that it is an example]. What you will do: Contact new prospects by phone, email and [Channel]. Run discovery calls and demos. Prepare proposals and follow up until a decision. Record all activity in [CRM]. Hit a monthly target of [Number or value]. Share what you learn from customers with the team. Must have: Experience selling to [Type of buyer], or a clear record of results in a similar role. Clear, persuasive communication. Discipline to follow up and keep records. Nice to have: Knowledge of our industry. Experience with [Tool]. Success in six months: A full pipeline, [Number] qualified meetings a month, and hitting at least [Percent] of target by month [Number]. Annotation: it explains the pay structure openly, because hidden commission is the biggest reason good sales candidates drop out. Do not promise earnings you cannot support. Label any expected earnings clearly as examples and check local rules on commission disclosure.
Example 4: operations coordinator
Title: Operations Coordinator, [Company name], [Location]. About us: [Two sentences]. The role: You keep day-to-day work moving between teams, suppliers and customers so promises are kept and problems are caught early. Hours: [Full-time]. Pay: [Amount and period]. What you will do: Track orders, jobs or projects from start to finish in [Tool]. Schedule work and resources and update the team daily. Liaise with suppliers and customers about deadlines and changes. Prepare weekly reports on progress, delays and costs. Improve small processes, writing simple checklists others can follow. Order supplies within an agreed budget. Support the owner with ad hoc tasks. Must have: Experience coordinating tasks or people in a busy setting. Organised, with a good eye for detail. Clear written updates. Comfortable with spreadsheets. Nice to have: Experience with [Industry]. Knowledge of project tools. Success in six months: Fewer missed deadlines than the previous six months, a weekly report the owner reads and acts on, and two processes documented and in use. Annotation: it names outcomes rather than virtues like proactive, and the nice-to-haves are honestly optional. Operations roles are easy to write as a pile of random tasks, so group the work under a clear purpose.
Example 5: junior developer
Title: Junior Developer, [Company name], [Location or remote]. About us: [Two sentences on the product and the engineering team size]. The role: You will join [Number] developers building and maintaining [Product], learning from experienced colleagues and taking on real tasks from week one. Hours: [Full-time]. Pay: [Amount and period]. What you will do: Build and fix features using [Languages and frameworks]. Write tests and take part in code review. Investigate bugs reported by users. Work with designers and product owners to clarify tasks. Document what you build. Learn our tools and practices, with [Mentoring arrangement]. Must have: Working knowledge of [Language], shown through a portfolio, project, course or job. Ability to explain your work and ask good questions. Willingness to learn and take feedback. Nice to have: Experience with [Framework or database]. Contributions to open-source or team projects. Our process: A short call, a practical task of about [Number] hours that we will pay for or keep to a fair limit, and a conversation with the team. Success in six months: Shipping small features independently, reviewed code with few repeated comments, and growing independence on bugs. Annotation: it states the interview process and task length, which builds trust, and it accepts any proof of skill. Do not ask for years of experience that exceed what a junior can have.
The weak job description, and its rewrite
Weak version and rewrite compared.
| Weak version | Problem | Rewrite |
|---|---|---|
| Rockstar office ninja | Not a title people search for | Office Administrator |
| Dynamic, fast-paced, join our family | Buzzwords that say nothing | [Company name] is a [Number]-person [type] business that [what you do] |
| Various admin tasks as required | No real tasks | Answer the main phone line and inbox; book travel; process supplier invoices; manage the office budget |
| 5+ years experience | Unjustified requirement | Experience in an admin or office role |
| Competitive salary | Hidden pay | [Amount and period], hours [Days and times] |
| Apply now! | No method or date | Send your CV and two lines on why you want the role to [Email] by [Date] |
Full rewritten version: Title: Office Administrator, [Company name], [Location]. The role: You keep our office running so the team can focus on clients. Must have: experience in an admin or office role, good written English, confident with spreadsheets and email. Nice to have: experience with [Accounting software]. What changed: a real title, real tasks, pay and hours, a must-have list short enough to read, and no slogans.
A checklist to score your own description
Score one point for each yes.
| Check | Yes or no |
|---|---|
| Title is one a candidate would search for | |
| First paragraph says what the person will achieve | |
| Duties are plain action verbs | |
| Must-haves separated from nice-to-haves and limited | |
| Pay, hours and location stated | |
| Six-month success described | |
| How to apply and the process explained | |
| No slogans, age or gender hints, or needless requirements | |
| Company description is short and true | |
| Local pay and wording rules checked |
Eight or more means ready to post. Five to seven means improve before posting. Under five means start again with the structure in /job-description-template. After posting, count how many applicants meet the must-haves. If most do not, the description or the channel needs work. Ask the first person you hire which parts of the description matched reality, and use the answer to improve the next one.
| Example role | What makes it work |
|---|---|
| Receptionist | Opens with purpose, names tools and hours, success can be tested later |
| Bookkeeper | Success measured in tasks and timing; names the software, which filters honestly |
| Sales representative | Explains pay structure and commission openly; earnings labelled as examples |
| Operations coordinator | Outcomes instead of virtues; tasks grouped under a clear purpose |
| Junior developer | States the process and task length; accepts any proof of skill |
Worked example with example numbers
These numbers are examples only. A ten-person design studio posts the weak office ninja advert and gets 85 applicants in two weeks. After screening against a must-have list written afterwards, only 9 meet the basics, and the owner spends about 14 hours reading and replying. The studio rewrites the description using the structure above, adding pay, hours, a short must-have list and a six-month success statement, and posts again. This time 52 people apply, 21 meet the basics, and the owner spends about 8 hours on screening. The numbers are invented for illustration, but they show the pattern to look for: a clearer description should raise the share of applicants who fit and reduce the time spent. Track your own two figures for each role, applicants who meet the must-haves, and hours spent screening, so you can see whether a rewrite helped. Keep the old and new versions so you can compare them later, and note any change in where applicants came from.
Where Rezumz fits, and who this is not for
Rezumz is a hiring workspace for small and mid-size hiring teams. You can write the job there, set its must-haves, open it to applications on a link, and score every CV against the must-haves with the lines it relied on shown. People make every decision. It suits small and mid-size teams, with the Team plan for four or more recruiters. It does not suit large enterprises that need deep HRIS or payroll links, and it does not post to job boards in one click, so you will share the apply link yourself. Prices: a free plan with 2 free candidate analyses, $29 a month, $199 a year, or a limited $499 lifetime option. Team is $79 a month or $699 a year for up to 10 teammates. See /pricing, /applicant-tracking-system and the live demo at /demo. These examples are not for senior executive roles, regulated professions, or roles with legal duties that must be stated in a set form, and a description does not replace an employment contract. Rules differ by country.
Frequently asked questions
What should a small business job description include?
Include a searchable title, a short company description, the purpose of the role, daily duties in plain verbs, short must-have and nice-to-have lists, pay, hours, location, what success looks like at six months, and how to apply. Check local pay-disclosure rules.
How long should a job description be?
Long enough to be specific and short enough to read in a couple of minutes, often 300 to 500 words for small business roles. Cut slogans and wish lists. Put the most important information first: the role, the pay and the hours.
Should I include the salary in a job description?
Stating pay usually attracts better-matched applicants and saves time, and some places require it. Rules differ by country and region, so check local law. If you give a range, make it honest and apply it consistently.
What is the difference between must-have and nice-to-have?
A must-have is something the person needs to do the job well in the first months. A nice-to-have is helpful but can be learned or is not essential. Keep must-haves short, because each one removes candidates, and screen against them consistently.
How do I fix a vague job description?
Replace buzzwords with specific tasks, state pay, hours and location, cut the experience requirement to what the work needs, add what success looks like at six months, and describe the company in plain words. Then compare results with the old version.