# How to Write a Job Description: An Owner&#8217;s Guide With Examples for Sales, Ops and Admin Roles

https://salesbond.app/blog/how-to-write-a-job-description/
Published: 2026-11-07 · Updated: 2026-11-14

A job description is a written account of a role: the title, why the position exists, who it reports to, what the person is responsible for, what they need to bring, and how you will know the work is being done well. The description of responsibilities sits at its center, so start with the outcome you need from the seat, then list five to eight responsibilities as verbs, and attach to each one the way you will measure it. Most templates skip the measure, and it is what keeps the document useful after the hire.

This guide is for an owner writing the description for a role they have been covering badly on the side, with worked examples for a sales rep, an office manager and a support agent in one format.

## What is a job description (and what it is not)

Three documents get confused here.

A job description is internal. It describes the role as it exists in your company, and you use it to hire, onboard, run 1:1s and judge whether the job is being done. It outlives the vacancy.

A job posting is marketing. It is the public text on the job board: shorter, it sells the company, and it says what the pay is. Write the description first, then cut the posting from it. In the other order you get an ad with no measures behind it, and the first 1:1 turns into a negotiation about what the job was.

An employment contract is a legal agreement about terms: pay, hours, notice, confidentiality. A job description should leave the binding terms, such as exact salary, notice and confidentiality, to the contract; a pay band and typical hours still belong in it. FindLaw’s small-business guide puts it plainly: “there are no legal requirements to have a job description” ( [FindLaw, Writing Legal and Effective Job Descriptions](https://www.findlaw.com/smallbusiness/employment-law-and-human-resources/writing-effective-job-descriptions.html)). You write one because it makes hiring and managing easier, and its yours to change whenever the role changes.

If the person will work as an [independent contractor](https://salesbond.app/blog/independent-contractor-vs-employee-sales-reps-owner-check-1099-crm-access/) instead, the 1099 check and the CRM access decisions come before any description.

## Before you write: decide what the seat has to produce

Most descriptions are written by listing what the last person did. That bakes in thier habits, including the bad ones. Start from the outcome instead.

One question: twelve months from now, what will be true in the business because this person was here? For a sales rep it might be “we have a steady flow of new customers from outbound, and the pipeline in the CRM can be trusted”. For an office manager: “the owner stops being the person who orders toner and chases invoices”. For support: “customers get an answer the same day, and the same complaint does not come in twice”.

Entrepreneur’s guide calls this step a job analysis and lists what to look at: the tasks involved, how the work will be done, the reason the job exists and how it relates to other positions, and the qualifications needed ( [Entrepreneur, How to Write a Job Analysis and Description](https://entrepreneur.com/growing-a-business/how-to-write-a-job-analysis-and-description-entrepreneur/56490)). The part owners skip is the reason. If you cannot say it in a sentence, you are not ready to hire. You are ready to hand off a pile of tasks.

Is this one job or two? A “sales and marketing coordinator” who also runs the CRM, writes the newsletter and closes deals is three jobs at half pay each. If the outcome sentence needs an “and” joining unrelated things, split the role. If the real question is how many sellers the plan needs, see [capacity planning for a small sales team](https://salesbond.app/blog/sales-capacity-planning-small-team/).

And who will manage this person? “Reports to the owner” is honest in a five-person company. In a fifteen-person company it usually means nobody will run the 1:1s. For a sales hire, if you are not sure who owns the number, read [what a sales leader owns versus what a manager owns](https://salesbond.app/blog/sales-leader-vs-sales-manager-what-the-role-owns-numbers-in-crm/) first.

## The parts of a job description

Eight parts, each with the mistake owners tend to make in it.

1. **Title.** The name the role has inside the company, and one candidates actually search for. Watch for vague titles: MileIQ’s example is advertising for a “Marketing Specialist” when you need a “Search Engine Optimization Associate”.
2. **Purpose.** One or two sentences on why the seat exists and what it produces. Not the company mission pasted in.
3. **Reports to.** One name or role. “The leadership team” is nobody.
4. **Responsibilities.** Five to eight, each a verb, an object and a result. Twenty bullets describing a week is too many.
5. **Measures.** How you and the person will know each responsibility is being met. Most templates leave this out.
6. **Requirements.** Must-have and nice-to-have, as two separate lists, so not everything looks mandatory.
7. **Working conditions.** Location, hours, travel, physical demands, tools. The weekend rota belongs here, so nobody hears about it first at the interview.
8. **Pay band.** A range, even a wide one; silence loses good candidates at the first screen.

Entrepreneur splits this in two: the job description (title, reporting line, summary, how the job relates to other positions) and a job specification, the companion document that lists the personal requirements, experience, salary range and physical demands ( [Entrepreneur](https://entrepreneur.com/growing-a-business/how-to-write-a-job-analysis-and-description-entrepreneur/56490)). With no HR department, one document is enough. Keep requirements and responsibilities in separate sections so you can edit one without rewriting the other.

How long? hibob’s HR glossary suggests “around 300 words” ( [hibob, Job description](https://www.hibob.com/hr-glossary/job-description/)). We think that is right for the posting and too short for the description, which comes out at roughly a page. Past a page and a half, you are listing tasks and the role gets lost.

## Write each responsibility as verb + result + how you’ll measure it

The line that appears in most sales rep descriptions reads like this.

> Responsible for managing the sales pipeline and building relationships with clients.

Nobody can fail at that sentence. Nobody can succeed at it either. It names no result and no way of telling.

Rewritten, the same responsibility looks like this.

> Keep every open deal in the CRM with a next step dated within 14 days, so the Monday pipeline report is true. Measured by: open deals with no scheduled activity, checked weekly in the pipeline view.

That is the format for every line: verb, object, result, and where you will look.

![A vague job line struck through, then rewritten as verb, object, result and measure.](https://salesbond.app/wp-content/uploads/2026/11/how-to-write-a-job-description-2.png)

Start with a doing verb. “Own”, “support”, “ensure” and “be responsible for” are ways of avoiding an action. “Call”, “book”, “update”, “reconcile”, “close”, “answer”, “order” are actions.

The measure must already exist or be cheap to create. “Customer delight” gives nobody anything to check, while “Measured by the rating question in the ticket-closed email” does. If the measure needs a new spreadsheet nobody will fill in, pick a different one, or admit the line is not measurable.

Not every line needs a number. “Reconcile supplier statements by the fifth working day of the month” has no quantity in it and is fully checkable.

Keep it to five to eight lines. MileIQ suggests marking the share of time each responsibility takes ( [MileIQ, How to write a job description](https://mileiq.com/blog/how-to-write-a-job-description)), which is a good sanity check. If the percentages add up to 140, cut.

A measure and a quota are different things. The target lives in the sales plan and moves with the season. The description says what you will look at; the plan says what number is good this quarter. Mix them and you will reissue the description every time the target changes.

## Requirements: must-have versus nice-to-have

Two lists and be stingy with the first one.

The must-have list is what you would not interview without: the right to work, one or two hard skills, one piece of experience that cannot be taught in a month. MileIQ makes the same split and warns that asking for too many years of experience or excessive academic credentials can turn away the very candidate you wanted ( [MileIQ](https://mileiq.com/blog/how-to-write-a-job-description)). Every must-have shrinks the applicant pool, so each has to earn its place.

The nice-to-have list is where “has used HubSpot” or “has worked in a company our size” goes. It tells you what to probe in the interview rather than screen on.

A test we use: for every must-have, name what goes wrong in the first 90 days if the person lacks it. If you cannot name it, move the item to the second list. “Bachelor’s degree” rarely survives this test for any of the three roles below.

If the must-have is “has kept a CRM clean under pressure”, ask for a real example and skip “tell me about your strengths”. Our [sales interview questions that test CRM habits](https://salesbond.app/blog/sales-interview-questions-hiring-manager-crm-habits/) are written for that line.

## Sales rep job description example, with measures from the CRM

Here the measure column is easiest to fill, because the CRM already records most of it. Name the CRM view or field in the description, so there is no argument later about where the number comes from.

A sales rep is not the person who runs the team. If you are hiring the one who owns the number and manages the sellers, use our [sales manager job description template for a small company](https://salesbond.app/blog/sales-manager-job-description-small-company-crm-duties/) instead. This example is for the seller.

**Title:** Sales Representative, outbound (B2B)
 **Purpose:** Bring in new customers from outbound prospecting and keep every open deal in the CRM honest enough that the pipeline report can be trusted.
 **Reports to:** Owner, until a sales lead is hired

Responsibilities and measures:

1. Create new opportunities from outbound outreach every week. Measured by: deals created per week in the CRM, against the weekly number in the sales plan.
2. Move deals through the stages with a dated next step on every open deal. Measured by: open deals with no scheduled activity, in the pipeline view, every Monday. The target is zero.
3. Qualify before proposal, using the fields the team agreed on (budget, decision maker, timeline). Measured by: proposals sent with those fields empty, reviewed in the weekly 1:1.
4. Close at the margin and terms in the price list. Measured by: won revenue and discount per won deal, from the CRM.
5. Record every customer conversation as an activity or note the same day. Measured by: deals whose last activity is older than 14 days.
6. Hand won customers to delivery with the agreed fields filled. Measured by: handover checklist complete before the deal is marked won.

**Must-have:** a year of selling to businesses by phone and email; has worked in a CRM daily; writes clearly.
 **Nice-to-have:** has sold in our industry; has used the CRM we use; has worked to a weekly target.

Every measure here comes from a report the owner can open, which keeps it independent of the rep’s memory and lets the 1:1 start from the pipeline view before anyone asks “how is it going”.

A disclosure, since this is where the measures meet software: we build SalesBond, a sales management layer on top of the CRM a team already uses. Measures like these are per-rep execution, which is what the Team Performance tab of its Sales Dashboard shows, so the owner does not build the filters by hand. If you want to know what your CRM says before the new rep inherits it, the free CRM audit looks at the last 30 days of the connected CRM and sends a PDF report, then a second PDF a week later with what changed. [Check your CRM with SalesBond](https://salesbond.app/).

![Hub-and-spoke map of six sales rep responsibilities, each with its result and where to measure it in the CRM.](https://salesbond.app/wp-content/uploads/2026/11/how-to-write-a-job-description-3.png)

## Two more job description examples: office manager and support agent

Same format, to show the measure column works outside the CRM.

### Office manager

**Purpose:** Run the office and the admin so the owner and the team do not have to.
 **Reports to:** Owner

1. Order supplies and manage vendors within the monthly budget. Measured by: spend against budget, monthly; out-of-stock items reported by staff.
2. Reconcile supplier invoices and pass them to the bookkeeper by the fifth working day of each month. Measured by: done or not, monthly; late-payment fees.
3. Keep the shared calendar, meeting rooms and visitor process working. Measured by: double bookings and complaints from the team, reviewed in the monthly 1:1.
4. Onboard new hires on day one: equipment, accounts, desk, first-week schedule. Measured by: onboarding checklist complete on day one for every hire.
5. Keep the office within the safety and insurance requirements that apply to us. Measured by: inspections passed; renewals done before expiry.

**Must-have:** two years in an admin or office role; comfortable with spreadsheets and a shared calendar. **Nice-to-have:** has handled vendor contracts; has worked in a company that grew while they were there.

### Customer support agent

**Purpose:** Give customers an answer they can act on, fast, and make sure the same problem does not come back.
 **Reports to:** Operations lead

1. Answer every incoming ticket within the response time the team sets. Measured by: first response time, from the helpdesk report.
2. Resolve at first contact where the answer exists in the help docs. Measured by: first-contact resolution rate; reopened tickets.
3. Tag every ticket with the right category so recurring problems can be seen. Measured by: untagged tickets, weekly.
4. Flag any problem that shows up repeatedly in a week to the operations lead. Measured by: flags raised versus repeat tickets, in the weekly review.
5. Update the help docs when an answer had to be written from scratch. Measured by: new or edited help articles per month.

**Must-have:** clear, kind written English under pressure; has used a helpdesk tool. **Nice-to-have:** has supported a product like ours; has written help documentation.

These two carry fewer numbers than the sales one, and that is honest. The sales role sits on top of a CRM that counts everything; an office manager’s work is mostly checked by whether things were done on time, which the monthly 1:1 covers.

## Legal and wording checks

The legal side is lighter than most owners fear, with one place that needs more care.

Nothing requires you to have a job description. But if you employ people in the US and the ADA applies to you, FindLaw’s reading is that a description you do write should list the essential functions of the role, as they really are. Its example is a warehouse role where workers are supposed to lift 50 pounds but routinely lift 75; the description should say 75 ( [FindLaw](https://www.findlaw.com/smallbusiness/employment-law-and-human-resources/writing-effective-job-descriptions.html)). For an office or sales role the equivalent is being straight about evening calls, travel, or eight hours on your feet at a trade show.

Wording is where owners get into trouble without meaning to. FindLaw’s examples are specific: “bilingual applicants preferred” is fine, “English-speaking only” is not; “young vigor” or “Millennial ideas” reads as age screening; “must work well under pressure” tells a candidate that one person is doing three jobs; “often” and “occasional” should become how much, per shift or per week. Read every requirement and ask whether it describes the job or a type of person. Cut the second kind.

Then check accuracy line by line against the day the person starts. A description of the company you hope to be next year is a promise you will be held to in the first 1:1.

## One description, four uses: posting, onboarding, 1:1s, review

A description written this way stays in use after the vacancy closes.

The posting is cut from it. Keep the title, the purpose sentence, three or four responsibilities in plain words, the must-have list, location and hours, and the pay band. Add a few true sentences about the company and drop the measure column; it reads cold in an ad. On pay, MileIQ’s advice holds: give a range if you can, and at minimum say something like “commensurate with experience” rather than nothing.

On the first day hand the person the full description with the measures and show them where each one lives: this pipeline view, this helpdesk report, this budget sheet. For a sales rep that is a twenty-minute tour of the CRM, and it becomes the first item in a [30-60-90 onboarding plan](https://salesbond.app/blog/sales-rep-onboarding-30-60-90/). It replaces the “what do you actually expect from me” conversation that otherwise happens in month three.

Run the 1:1 down the the list of measures. Not every line every time, just the two or three that moved. The agenda already exists, and the conversation stays on the work.

When someone is not doing the job, the description is the first document you both open. If the measures were there from day one, a [performance improvement plan](https://salesbond.app/blog/sales-performance-improvement-plan-small-team/) is a continuation of the 1:1s, and nobody is caught off guard. If they were not, the improvement plan is where you discover you never agreed what the job was.

hibob’s glossary says to update job descriptions regularly. Our concrete version: at every annual review, and whenever a responsibility that takes a real share of the week is added or removed. Then have the person in the seat read the new version and tell you whether it is true.

Pick the role you are about to hire for, write the outcome sentence tonight, and see whether it needs an “and”. The first description in this format takes an evening. The second takes an hour, because half the measures already exist in your CRM, your helpdesk or your bookkeeping.
