# How to Create a Job Description for Your First Hire

> Source: [https://botensten.com/articles/job-description-for-first-hire](https://botensten.com/articles/job-description-for-first-hire) (canonical)
> Author: Botensten — Botensten, https://botensten.com
> Published: 2026-08-18

## TL;DR

To create a job description for your first hire, define the single outcome the role must own, then list 3-5 responsibilities tied to that result, the must-have skills, the pay range, and the work model. Keep it under 500 words. SHRM reports 71% of employers treat the job description as a critical hiring step, and the U.S. Bureau of Labor Statistics puts the average cost of a new hire near $4,000 — so getting the description right before you post saves real money.

Create a job description for your first hire by defining one outcome you need owned, not a task list — 71% of employers call the job description a critical hiring step, according to [SHRM's research on job descriptions](https://www.shrm.org/hr-today/trends-and-forecasting/research-and-surveys/Pages/job-descriptions.aspx). Name the role, list 3-5 responsibilities tied to results, and state the pay and work model. Keep it under 500 words. Write it before you post, because a fuzzy description pulls in fuzzy candidates.

## How do I create a job description for my first hire?

Start with the outcome, then work backward to the daily work. Your first hire should own a result you can measure — "keep our support inbox under a four-hour first-response time," not "answer emails."

The cost of getting this wrong is concrete. The [U.S. Bureau of Labor Statistics estimates the average cost of a new hire near $4,000](https://www.bls.gov/opub/mlr/2019/article/costs-of-recruiting-and-hiring-employees.htm), and a mis-hire usually costs several times that once you count lost time and re-hiring. A tight description is your cheapest filter.

Use these six steps in order:

1. Name the one outcome the role owns.
2. List 3-5 responsibilities that drive that outcome.
3. Separate must-have skills from nice-to-haves.
4. State the work model, hours, and a real pay range.
5. Describe what success looks like at 90 days.
6. Cut every line that does not help a candidate self-select in or out.

If a sentence does not help someone decide whether to apply, delete it.

## What are the essential components of a job description?

Every useful job description has six parts: title, outcome, responsibilities, required skills, pay and work model, and a 90-day success measure. Skip any of these and applicants fill the gap with guesses.

The difference between a description that works and one that wastes your time is specificity. Compare the two versions of each element below.

| Element | Vague (attracts noise) | Specific (attracts fit) |
|---|---|---|
| Title | "Marketing Ninja" | "Content Marketer (B2B SaaS)" |
| Outcome | "Help us grow" | "Publish 8 SEO articles/month that rank" |
| Responsibility | "Manage social media" | "Own LinkedIn: 3 posts/week, reply within 24h" |
| Skills | "Detail-oriented" | "Can write and edit in our house style, 2+ yrs" |
| Pay | "Competitive" | "$60k-$75k + equity, remote" |
| Success | "Do a great job" | "By day 90: content calendar live, 4 posts shipped" |

Naming a real pay range is not optional. It filters out mismatched candidates before you spend an hour interviewing them.

## How we write job descriptions as an AI-first studio

At Botensten we ship production software with AI every day, and our first outside hire was a part-time technical writer to document our build-in-public playbooks. Our first draft failed. We wrote "help create content" and got 40 applicants, most of them generalists who had never touched developer docs.

So we rewrote it around one outcome: "Turn our shipped features into tutorials a solo founder can follow in under 30 minutes." We added a real constraint — must have written for a technical audience — and a 90-day measure: six tutorials live, each tested by a non-engineer. The applicant pool dropped to nine people, and every one of them could actually do the job.

The lesson we now apply to every hire: the description is a product spec. We draft it, run it past the AI models we build with to catch vague verbs, then cut it to a single screen. If the role's real work changes — and for a small studio it changes often — we update the description that week, not at some annual review.

## What are the best practices for writing and updating job descriptions?

The core best practice is clarity: state exactly what the person will do and how you will judge it. A [Glassdoor survey found 60% of job seekers say a clear, concise job description was a key factor in deciding to apply](https://www.glassdoor.com/blog/job-descriptions-why-they-matter/), so vagueness costs you good candidates directly.

Follow these rules when you write and maintain them:

- Lead with the outcome and the 90-day measure of success.
- Cap it at one screen — roughly 400-500 words.
- Write responsibilities as verbs the person owns, not passive duties.
- List only skills the role truly needs; over-listing narrows your pool and hurts diversity.
- Include the pay range and work model up front.
- Review the description each time the role's real work shifts, and at minimum every 6-12 months.

Avoid inflated titles and buzzwords. "Rockstar" and "ninja" signal a company that has not defined the job.

## How can job descriptions attract and retain top talent?

A precise job description attracts people who want that exact role and repels the rest, which raises retention from day one. When the described job matches the real job, new hires do not quit in month three over a mismatch.

Management, not the posting, drives most departures — [Gallup's State of the American Workplace report found employees frequently cite poor management as a reason to leave](https://www.gallup.com/services/176708/state-american-workplace.aspx), and a description that overpromises then underdelivers reads as bad management on arrival. Employer brand compounds this: [HubSpot's 2022 Recruitment Marketing Benchmark Report found companies with a strong employer brand see a 28% reduction in turnover](https://blog.hubspot.com/blog/tabid/6307/bid/33323/The-2022-Recruitment-Marketing-Benchmark-Report.aspx). An honest, specific description is the first proof of that brand.

## Job description vs. job posting — what's the difference?

A job description is the internal definition of the role — outcomes, responsibilities, and success measures. A job posting is the public, marketing version you publish to attract applicants, built from the description but adding your company story and a call to apply.

Write the description first. The posting inherits its clarity; if the underlying description is fuzzy, no clever posting copy will fix the mismatch later.

## Frequently asked questions

**How do I create a job description for my first hire?**

Define one measurable outcome the role owns, then list 3-5 responsibilities, must-have skills, a real pay range, and a 90-day success measure. Keep it to one screen and write it before you post the job.

**What are the key components of a job description?**

Title, the core outcome, 3-5 responsibilities, required skills, pay and work model, and a 90-day measure of success. Missing any of these forces applicants to guess.

**How do I determine the essential duties of a job?**

Start from the outcome you need owned and list only the tasks that directly drive it. If a duty does not affect the measurable result, it probably belongs to a different role.

**How can job descriptions attract diverse candidates?**

List only the skills the role genuinely requires and drop inflated "nice-to-have" credentials. Over-listing requirements narrows your pool and screens out capable people from non-traditional backgrounds.

**What is the difference between a job description and a job posting?**

The description is the internal definition of the role; the posting is the public marketing version you publish to attract applicants. Write the description first, then build the posting from it.

**How often should I update my job descriptions?**

Update a description whenever the role's real work changes, and review it at least every 6-12 months. For small teams where roles shift fast, revise it the same week the work changes.

**What are the legal considerations when creating a job description?**

Focus on job-related requirements and measurable duties, avoid language that could screen out protected groups, and state that essential functions can be performed with reasonable accommodation. Consult local employment law before posting.