How to Write a Job Description: Complete Guide for Small Business

At a previous company, I wrote my first job description by googling "Office Manager job description," copying one from a Fortune 500 company, and changing the company name. The JD described a role that required managing a team of 8, coordinating with 4 departments, and overseeing a $200,000 annual budget. My company had 11 employees, one department, and an office supply budget of maybe $3,000.

I hired someone who expected the Fortune 500 role. She was overqualified, bored within weeks, and gone within three months. The problem was not the hire. The problem was the job description. It described a role that did not exist at my company, attracted a candidate who wanted that non-existent role, and set expectations that I could never meet.

A job description is not a formality. It is the document that determines who applies, what they expect, how you evaluate them, and what their first 90 days look like. Every onboarding problem, performance issue, and misaligned expectation traces back to what was or was not written in the JD. I built the onboarding workflow in FirstHR to start from the job description for exactly this reason: the JD is where hiring and onboarding connect, and most small businesses treat them as separate processes.

This guide covers everything a US small business owner needs to know about job descriptions: what they are, the 7 essential components, how to write one step by step, the compliance language that protects you from EEOC and ADA claims, 5 real examples for common small business roles, the FLSA exempt vs. non-exempt classification that most founders get wrong, salary transparency laws by state, how to adapt JDs for remote and hybrid roles, and the connection between the JD and your onboarding plan that no other guide makes. If you are writing a job description for the first time or fixing one that is not working, this is the complete reference.

What Is a Job Description?

A job description is a written document that defines the duties, responsibilities, qualifications, and working conditions of a specific position within an organization. It is both a hiring tool (attracting the right candidates) and a compliance document (establishing FLSA classification, ADA essential functions, and a defensible record of job requirements).

At a large company, job descriptions are written by HR professionals who specialize in job analysis and classification. They use standardized formats, are reviewed by legal counsel, and are maintained in an HRIS. At a small business, the founder writes the JD (usually in a hurry, usually by copying something from the internet) and it lives in a Google Doc that nobody updates. Both extremes produce problems. The enterprise JD is too rigid and generic. The small business JD (or lack thereof) is too vague and disconnected from reality.

The practical goal: a one-to-two-page document that accurately describes what someone will actually do at your company, written in language that is legally compliant and specific enough to serve as both a hiring tool and an onboarding blueprint. The EEOC provides specific guidance on writing job descriptions that comply with federal anti-discrimination laws.

Job Description vs. Job Posting vs. Job Specification

These three terms are frequently confused, but they serve different purposes and contain different information.

For small businesses, the practical approach: write the full job description first. Then create a shorter job posting by extracting the most compelling parts (title, summary, top 5 responsibilities, must-have requirements, compensation, and how to apply). The JD stays as your internal document. The posting goes on the major job boards.

A common mistake: treating the job posting as the job description. The posting is marketing. It is designed to attract clicks and applications. The JD is the operational document. It is designed to define the role, establish evaluation criteria, and serve as a compliance record. When the posting is your only document, you have marketing language where you need precision, and you lack the specificity needed for onboarding, performance reviews, and legal defense.

Another distinction worth understanding: a job specification is a subset of the JD that focuses exclusively on the minimum qualifications (education, experience, certifications, skills) required to perform the role. Some organizations maintain separate JDs and job specs. For small businesses, combining them into one document (the JD with a dedicated "Requirements" section) is simpler and equally effective.

You will also see the same document called a position description, a role description, or a job profile. In US small business practice they are the same thing, and the label matters far less than whether the document lists real duties, real requirements, and a classification. A fill-in job description template is the fastest way to start one.

The 7 Components Every Small Business Job Description Needs

Enterprise JD templates include 15 to 20 sections. Small businesses need 7. These cover legal requirements, candidate attraction, and operational clarity without the overhead of a formal job analysis process.

The most commonly missed component at small businesses is FLSA classification. Founders assume "salaried" means "exempt from overtime." It does not. Exemption depends on meeting specific duties tests and salary thresholds set by the Department of Labor. Misclassifying a non-exempt employee as exempt creates wage-and-hour liability that can include 2 to 3 years of back overtime pay plus liquidated damages. The exempt vs. non-exempt section below covers the tests in detail.

Job Analysis: Finding Out What the Role Actually Involves

A job analysis is the fact-gathering step that comes before the writing. You collect what the person does, how often, with which tools, and what each task produces. The job description then becomes a summary of those findings instead of a guess. Thirty minutes of it prevents most of the rewriting later.

The step also carries legal weight. The Uniform Guidelines on Employee Selection Procedures (29 CFR 1607.14) expect any validity study behind a selection procedure to rest on a review of job information that includes a job analysis. The notes you take here are the record behind every requirement you may later have to justify.

Five methods cover almost every small business situation. Pick the one that matches how much you already know about the role, not the one that sounds most thorough.

A Job Analysis Example for an Office Manager Role

Here is what one looks like end to end. You ask the person in the role to reconstruct five working days and you get roughly 40 tasks: invoice entry, chasing two late receivables, onboarding paperwork for one new hire, three vendor calls, ordering supplies, fixing the printer, booking travel, updating the PTO sheet.

Then you group them and total the hours. Finance ran about 14 hours a week, HR paperwork about 8, vendors and facilities about 9, scheduling about 5. Those four groups become four of the five responsibility bullets, in that order, because the hours decide the ranking. The printer and the travel booking fall under additional duties.

The value is in what the grouping exposes. In this example the JD had never mentioned the 8 hours a week of HR paperwork, which is why the last two hires believed they were taking a finance job. Analysis first, responsibilities second, title last.

How to Write a Job Description Step by Step

Writing a good job description takes 30 to 60 minutes. Fixing the problems created by a bad one (wrong hires, legal exposure, misaligned expectations) takes months and costs thousands. Here is the process that works for small businesses.

Writing Responsibilities That Are Actually Useful

The responsibilities section is the most important part of the JD and the one most founders get wrong. The two common failures: writing responsibilities so vague they describe any role ("manage projects and drive results") or so granular they describe a single task ("update cell B7 in the Q3 revenue spreadsheet every Tuesday"). The sweet spot is specific enough to evaluate but general enough to allow flexibility.

Each responsibility should follow one formula: action verb, then what, then measurable scope. Not "handle customer service" but "respond to 20-30 customer inquiries per day via email and phone within 4-hour SLA." Not "manage social media" but "create and publish 3-5 social media posts per week across Instagram and LinkedIn, managing a $1,500/month ad budget." The specificity is what makes the JD useful for onboarding: each responsibility with a number becomes a training milestone.

The "Would I Reject?" Test for Requirements

Every requirement you add to a JD reduces your applicant pool. Some reductions are necessary (you need a CPA license for your bookkeeper). Some are counterproductive (requiring a bachelor's degree for a role where experience matters more). The test: imagine a candidate who is excellent in every way except they lack this one requirement. Would you reject them? If the answer is no, it is not a requirement. It is a preference.

Research consistently shows that women apply to jobs when they meet 100% of listed requirements, while men apply when they meet about 60%. Every unnecessary requirement disproportionately reduces applications from qualified women. The practical fix: limit must-have requirements to 3 to 5 genuine necessities and move everything else to a "preferred" section.

Job qualifications come in four types, and separating them keeps the list honest: education, verifiable experience, licenses or certifications, and demonstrable skills. Only licenses are usually non-negotiable, because a law or an insurer requires them. The other three are where inflation creeps in, so write each one as the minimum that lets someone do the work.

Job Title Examples for Common Small Business Roles

Use the title candidates type into a search box, not the one that sounds best in a pitch deck. The table below covers the seven functions small businesses hire for first, with the titles that get searched next to the ones that quietly cost you applications.

Levels matter as much as the noun. Coordinator and Assistant read as entry level, Specialist and Representative as individual contributors, Lead and Supervisor as first-line management, Manager as owning a function, and Director as owning several. Pick the level that matches the real scope, because candidates price the role from the title before they reach the range.

Title inflation is the small business version of this mistake. Calling the head of a two-person team a Director creates a problem at the next hire, because the title already outranks the work and the next person up has nowhere to go. It also does nothing for classification, which turns on duties and salary.

Two checks before you commit to a title. Search it on a major job board and see whether real postings for comparable work come back, then compare it against the standard occupational titles on O*NET. If neither returns anything close to your role, candidates will not find the posting either.

Job Description Best Practices

Everything above adds up to a set of best practices worth keeping in one place. The checklist below is the short version of the whole guide: the ten habits that separate a job description that attracts the right people and holds up legally from one that produces mismatched applicants, legal exposure, and early turnover. If you do nothing else, do these ten.

The single highest-leverage practice on this list is the first one: write responsibilities before anything else. Nearly every weak job description traces back to a founder who started with the title and summary, got stuck trying to sound impressive, and ended up describing the role in generalities. Start with what the person actually does every week, in specific and measurable terms, and the rest of the document writes itself. The second highest-leverage practice is the last one: treat the JD as a living document that improves with every hiring cycle, not a form you fill out once and forget.

These practices are deliberately calibrated for small businesses, not enterprises. An enterprise JD process involves formal job analysis, compensation banding, and legal review. A small business needs the ten habits above and about thirty minutes per role.

Job Description Format: A Reusable Template

The format should be scannable, consistent, and reusable across all roles at your company. The template below works for any role at a small business with 5 to 50 employees.

Use this same format for every role. Consistency makes JDs easier to write (you are filling in a template, not starting from blank), easier to compare (same structure across all roles), and easier to defend (consistent formatting demonstrates a systematic approach to compliance).

One formatting decision that matters more than most guides acknowledge: whether to include physical requirements as a standalone section or embed them within responsibilities. The best practice is a standalone section that explicitly identifies which physical demands are essential functions (required to perform the job) versus marginal functions (occasionally needed but not central). This distinction matters legally under the ADA because employers must provide reasonable accommodations for essential functions but are not required to accommodate marginal functions. If the role has no physical demands beyond standard office work, omit this section entirely rather than listing generic physical requirements that do not apply.

Compliance Language: EEOC, ADA, and FLSA Without a Lawyer

This is the section that every other job description guide either skips entirely or covers in one paragraph. Compliance language in JDs is not optional. It is the difference between a defensible hiring process and one that creates liability. You do not need an employment lawyer to get it right, but you need to know the rules.

The Three Federal Laws That Apply to Every JD

The EEOC enforces Title VII (race, color, religion, sex, national origin), the ADA (disability), and the ADEA (age). Every word in your JD is potential evidence in a discrimination claim. The Job Accommodation Network provides specific guidance on writing ADA-compliant job descriptions with essential functions language.

The rule of thumb: every requirement in the JD must be a genuine, job-related necessity. If you cannot explain why a specific requirement is essential to performing the role, remove it. "Nice to have" requirements that disproportionately screen out a protected class become legal liabilities.

State-Specific Compliance Requirements

Beyond federal law, many states add requirements that affect job descriptions directly. California requires salary ranges in all postings, prohibits asking about criminal history on applications (Fair Chance Act), and restricts credit checks to certain roles. New York requires salary ranges and prohibits height/weight requirements unless they are bona fide occupational qualifications. Colorado requires listing benefits in postings. Illinois requires an EEO statement for employers with 15+ employees. These state requirements change frequently. SHRM maintains a comprehensive resource on job description best practices and state-specific requirements.

Documentation and Record Keeping

Retain every version of every JD you use in the hiring process. If a candidate files an EEOC charge claiming discriminatory requirements, the JD is your primary defense document. It shows what you required, why you required it, and that you applied the same requirements to every candidate.

Essential Job Functions: Examples From Common Small Business Roles

An essential function is a duty the position exists to perform. A marginal function is a task the person happens to do that could move to someone else without changing what the job is. The ADA regulations give three markers: the position exists primarily to perform the function, few employees are available to share it, or the function is highly specialized (29 CFR 1630.2(n)).

List the essential ones under their own heading and add "with or without reasonable accommodation" after any physical or cognitive demand. Those same regulations name a written job description prepared before you advertise or interview as evidence of what the essential functions are, which is one more reason to finish the JD before the posting goes up.

Why Small Businesses Need a Different Approach to Job Descriptions

Enterprise JDs are written by HR specialists for roles that exist within well-defined organizational structures. Small business JDs are written by founders for roles that often combine 2 to 3 enterprise functions into one position. Copying an enterprise JD for a small business role creates a fundamental mismatch.

The SMB Role Reality

At a 500-person company, "Marketing Manager" manages a team of 5, owns a $500K budget, and focuses exclusively on marketing strategy. At a 15-person company, "Marketing Manager" writes social media posts, designs email campaigns in Mailchimp, manages a $2,000/month ad budget, updates the website, and handles PR inquiries. These are not the same role. They should not have the same JD.

The practical implication: small business JDs should describe what the person will actually do, not what the role would look like at a larger company. Use specific tools (QuickBooks, not "ERP systems"), specific volumes (15-20 accounts, not "a portfolio of clients"), and specific reporting relationships ("reports to the founder", not "reports to the VP of Operations").

The First-Hire JD

The hardest JD to write is the first one: hiring employee number 3, 4, or 5 when the founder is doing everything and needs to offload responsibilities to someone else. The challenge is that the "role" is really "everything the founder does not have time for," which is not a job description. It is a cry for help.

The fix: list everything you are currently doing. Group the tasks into categories (admin, sales, operations, finance, HR). Identify the category that consumes the most time and is least dependent on your personal expertise. That category is the role. Write the JD for that category only, not for "general assistant who does everything." A focused role attracts better candidates and produces better outcomes than a catch-all role that overwhelms the new hire.

The Multi-Hat Problem

At a small business, every role is a multi-hat role. Your Office Manager also handles HR paperwork. Your Sales Rep also does customer support. Your Marketing person also manages the website. This is normal and expected. The mistake is not documenting the multi-hat nature of the role in the JD.

When you list only the primary function ("Marketing Manager") but the person also handles customer support, website management, and event coordination, you create a mismatch between what the candidate expects and what the job actually requires. Be explicit. If the role is 60% marketing, 20% customer support, and 20% admin, say so in the summary. Candidates who thrive at small businesses are the ones who want variety, not the ones who want a single specialty. The honest JD attracts them.

When the JD Does Not Match the Reality

One of the most common causes of early turnover at small businesses is the gap between the JD and the actual role. Research from Gallup shows that only 12% of employees strongly agree their organization does a great job of onboarding. A key contributor is misaligned expectations that start with the JD. When the role someone accepted does not match the role they are doing on Day 30, disengagement begins immediately.

The fix is simple but requires discipline: update the JD whenever the role changes, and share the current JD with the new hire during onboarding so they can see exactly what they signed up for. If the role has evolved since the JD was written, update it before you start interviewing.

From Job Description to Onboarding Plan in One Workflow

This is the connection that no other job description guide makes: the JD is not just a hiring document. It is the source material for your entire onboarding process. Every responsibility listed in the JD becomes a training task. Every requirement becomes a skill to verify or develop during the first 90 days. The JD is the blueprint for the 30-60-90 day plan.

This workflow means the JD is never a throwaway document. It is referenced during onboarding (what should we train?), during performance reviews (are they meeting expectations?), during compensation discussions (has the role expanded beyond what we originally described?), and during exit interviews (was the role what they expected?). I built the AI onboarding wizard in FirstHR to generate onboarding plans directly from job descriptions for exactly this reason: the JD already contains everything you need to onboard someone. You just need to transform responsibilities into tasks and requirements into training goals.

5 Real Small Business Job Description Examples

Every job description guide shows examples from Fortune 500 companies. Those are useless for a 20-person business. The examples below are written for real small business roles: the kind of positions a founder with 5 to 50 employees actually hires for. Each example follows the 7-component format from this guide.

Notice what all five examples have in common: specific responsibilities with measurable outcomes, realistic requirements (not inflated), clear compensation, and language that describes the actual role at a small company. None of them require "10+ years of experience" or an MBA. They describe the work as it actually is, which attracts candidates who want that specific work.

Customizing Examples for Your Business

These examples are starting points, not templates to copy verbatim. The responsibilities should reflect your specific context: your tools (QuickBooks vs. Xero vs. FreshBooks for the bookkeeper), your scale (15 accounts vs. 50 accounts for the sales rep), your structure (reports to founder vs. reports to operations manager for the warehouse lead), and your industry (healthcare has different compliance requirements than construction).

The most important customization is the compensation range. The ranges in these examples are illustrative. Your range should reflect your local market, your budget, and the seniority level you are targeting. Check national compensation surveys and the BLS Occupational Outlook Handbook for current market data in your area. Posting an accurate range attracts candidates who are genuinely interested at your price point and eliminates the frustration of reaching the offer stage only to discover a 30% gap in salary expectations.

For industry-specific roles, you may need additional components. Healthcare roles need license verification requirements and HIPAA training mentions. Construction roles need OSHA certification requirements. Financial roles need fiduciary responsibility language.

Salary Transparency Laws: What You Must Disclose

An increasing number of states and cities require employers to include salary ranges in job postings. As of 2026, these jurisdictions have pay transparency requirements.

Even in states without transparency laws, posting salary ranges is a competitive advantage for small businesses. It filters out candidates whose expectations exceed your budget (saving interview time), signals that you value transparency (attractive to high-quality candidates), and eliminates the awkward salary conversation that causes offers to fall through.

How to Set the Right Salary Range

The range should be narrow enough to be meaningful and wide enough to allow negotiation. A $20,000 spread ($40,000 to $60,000) is too wide: it tells the candidate nothing about what you actually intend to pay, and candidates will anchor to the top of the range. A $5,000 to $10,000 spread ($50,000 to $60,000) is ideal: it communicates your budget while allowing room for experience level and negotiation.

Where to find market data: the BLS Occupational Outlook Handbook (official government data by occupation and metro area), national compensation surveys published by industry and trade associations, and current postings for the same title in your metro area. Check at least two sources and use the overlap as your range. If one source says $55,000 to $65,000 and another says $52,000 to $62,000, your range of $55,000 to $62,000 is well-supported.

The Internal Equity Problem

When you post a salary range for a new role, it may be visible to current employees in the same or similar roles. If your existing bookkeeper makes $48,000 and you are posting a new bookkeeper role at $52,000 to $58,000, you have a pay equity issue to address before posting. Either adjust the existing employee's compensation, or have a proactive conversation about why the ranges differ (market rates may have shifted, the new role may have different scope). Discovering the discrepancy through a job posting is worse than discovering it through a planned compensation review.

Writing Inclusive Job Descriptions

Inclusive language in job descriptions is not about political correctness. It is about not accidentally discouraging qualified candidates from applying. Research consistently shows that certain words and phrases disproportionately discourage women, older workers, and candidates from underrepresented groups from applying, even when they are fully qualified.

Practical Changes That Expand Your Applicant Pool

The simplest test: read the JD as if you were a 45-year-old woman, a 55-year-old veteran, a person who uses a wheelchair, and a recent immigrant who is a US citizen. Does anything in the JD suggest they should not apply even if they are qualified? If yes, rewrite it.

The Gender Decoder Problem

Research from the Journal of Personality and Social Psychology found that certain words in job descriptions are coded as masculine (competitive, dominant, aggressive, ambitious, analytical) or feminine (collaborative, supportive, nurturing, interpersonal, community). JDs that use predominantly masculine-coded language receive significantly fewer applications from women, even when the women are fully qualified. The fix is not to avoid all gendered language but to balance it: use a mix of action-oriented and collaborative terms to attract a diverse applicant pool.

Practical changes: replace "competitive salary" with "market-rate compensation." Replace "aggressive growth targets" with "ambitious growth goals." Replace "dominate the market" with "lead in the market." These are small changes that measurably expand your applicant pool without weakening the JD. The goal is not to soften the language. It is to stop accidentally signaling that only one type of person should apply.

Accessibility in Job Postings

If your job posting is online (which it should be), basic accessibility matters. Use standard fonts and formatting. Do not embed text in images (screen readers cannot read image text). Provide an alternative to online-only application methods if requested as a reasonable accommodation. Include the phrase "Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions" in every JD that lists physical or cognitive requirements.

Exempt vs. Non-Exempt: Getting Classification Right

FLSA classification is the most consequential legal decision in any job description. Getting it wrong exposes you to years of back overtime pay, liquidated damages (equal to the back pay owed), and attorney fees. The DOL Wage and Hour Division provides the official tests.

The Two-Part Test

Part 1 is the salary test. The employee must be paid on a salary basis at or above the minimum threshold. The current federal minimum for exempt classification is $684/week ($35,568/year): the 2024 DOL rule that raised the threshold was vacated by a federal court in November 2024 and formally rescinded in May 2026, which restored the 2019 standard. If the role pays below this threshold, it is non-exempt regardless of duties.

Part 2 is the duties test. The employee's primary duties must fall into one of the exemption categories.

The most common misclassification at small businesses: calling someone a "Manager" (exempt) when they do not supervise anyone and primarily perform the same tasks as the people around them. Job title does not determine classification. Duties do. An "Operations Manager" who does not manage people, does not exercise independent judgment on significant matters, and primarily performs operational tasks is non-exempt, regardless of title.

The Practical Classification Checklist

Before classifying any role, walk through this checklist. If you answer "no" to either of the first two questions, the role is non-exempt, and you can stop there.

That last row is the one worth acting on today. The two salary questions are arithmetic, and the FLSA guide has a determination record that walks all three tests end to end. What the job description uniquely supplies is the evidence for the duties test: the responsibilities you wrote are the description of the work an auditor will read back to you. The sheet below pulls that evidence out of the JD and files it alongside, so the classification line in the JD has something standing behind it.

The Cost of Getting Classification Wrong

Misclassifying a non-exempt employee as exempt means you owe them overtime for every hour worked over 40 per week, going back up to 3 years (for willful violations). If the employee averaged 5 hours of overtime per week at $30/hour, the back pay is approximately $23,400 for one employee over 3 years, before liquidated damages (which can double the amount) and attorney fees. For a small business, one misclassification can cost more than the employee's annual salary.

When and How to Update Your Job Descriptions

A job description is not a one-time document. Roles evolve. Responsibilities shift. Compensation changes. Laws update. An outdated JD creates misaligned expectations, undermines performance reviews, and weakens your position in any legal dispute.

5 Triggers for Updating a JD

The minimum: review every JD once per year. The practical approach: update the JD whenever you fill the role, and review it with the person in the role during their annual review to confirm it still accurately describes what they do.

The JD as a Living Document

The best practice is to treat the JD as a living document that evolves with the role. When a team member takes on a significant new responsibility, update the JD. When a responsibility shifts to another person, update both JDs. When you promote someone, create a new JD for their new role and update the old one for their replacement.

This sounds like overhead, but it pays off in three ways. First, when the person in the role leaves, you have an accurate and current JD ready to post immediately instead of spending 2 hours reconstructing what the role had become. Second, during performance reviews, you and the employee are evaluating against an accurate baseline, not a document that describes the role from two years ago. Third, if the role has expanded significantly without a compensation adjustment, the updated JD makes the case for a raise visible rather than forcing the employee to argue for it.

Store the current version of every JD in a central location where both you and the employee can access it. The employee should know what their official JD says, and they should be able to flag when it no longer matches reality. This transparency builds trust and prevents the "that is not what I signed up for" frustration that leads to early departures.

AI-Assisted Job Description Writing

AI tools can generate a first draft of a job description from a job title and a few bullet points about the role. This is useful as a starting point, not a finished product. The quality of AI-generated JDs depends entirely on the quality of the input you provide.

What AI Does Well

AI generates comprehensive responsibility lists from a job title (often surfacing tasks you would forget to include), suggests appropriate requirements based on industry norms, writes professional-sounding summaries, and produces EEO statements. For a founder who has never written a JD, the AI draft provides structure and language that would take an hour to create from scratch.

What AI Gets Wrong

AI does not know your company. It generates generic responsibilities based on the job title at an average-sized company, not your specific context. It inflates requirements (defaulting to enterprise-level qualifications), uses buzzword-heavy language that sounds impressive but says nothing specific, and cannot determine the correct FLSA classification for your role. AI also has no visibility into your state's specific compliance requirements.

The Practical Workflow

Use AI to generate the first draft. Then customize every section: replace generic responsibilities with your specific weekly tasks, remove inflated requirements, add your actual compensation range, determine the correct FLSA classification manually, and review every sentence for compliance language. The final document should be 30 to 40% AI-generated structure and 60 to 70% your specific content.

Using the JD for Performance Reviews

A job description does not stop being useful after the hire is made. It is the baseline for every performance conversation you have with that employee. Without a JD, performance reviews become subjective: "I feel like you are doing a good job" or "I think you could do more." With a JD, they become objective: "You are performing 5 of 7 responsibilities at the expected level. Let us discuss the two that need improvement."

The JD-Based Review Framework

At the 30-day, 60-day, and 90-day check-ins (and at annual reviews thereafter), use the responsibilities section of the JD as your evaluation framework. For each responsibility, assess: is the employee performing this task independently? At what quality level? Is the scope what we described, or has it changed? This approach eliminates the vagueness that makes performance reviews uncomfortable for both parties.

This framework works because the JD already defines what the person should be doing. The check-in evaluates how well they are doing it. No new criteria needed. No ambiguity about expectations.

When the JD and Reality Diverge

If the performance review reveals that the employee is spending 30% of their time on tasks not listed in the JD, either the JD needs updating (the role has genuinely evolved) or the employee needs redirecting (they have drifted into work that is not their responsibility). Both are valuable discoveries. The first leads to a more accurate JD. The second leads to a conversation about priorities and focus. Either way, the JD is the anchor that makes the divergence visible.

Job Descriptions at Different Growth Stages

The JDs you write at 5 employees are different from the ones you write at 25 or 50. As your company grows, roles become more specialized, reporting structures add layers, and compliance requirements increase. Your JDs need to evolve accordingly.

5-10 Employees: Generalist Roles

At this stage, every role is a generalist role. Your "Marketing Manager" also handles sales support, customer communications, and probably the company holiday party. JDs should honestly reflect this breadth. List the primary function (60-70% of time) and the secondary functions (30-40%). Candidates who thrive at this stage want variety and ownership. The JD should signal that clearly.

Common roles at this stage: Office Manager/HR Coordinator (the person who handles everything administrative), Operations Generalist (the person who keeps things running), Sales/Business Development (the person who generates revenue), and Technical/Product (the person who builds or delivers what you sell). Each role probably touches 3-4 functional areas.

10-25 Employees: Beginning Specialization

At this stage, some roles start to specialize. You no longer need a Marketing + Sales + Customer Support generalist. You need a dedicated sales rep, a marketing person, and a customer support person. JDs should reflect this specialization: narrower responsibilities, deeper requirements within the specialty, and clearer boundaries between roles.

The transition challenge: the generalist who was hired to do "marketing and sales and support" may not want to specialize when the role narrows. This is a common source of tension at growing small businesses. Having clear, updated JDs makes the conversation productive: "The role has evolved from a generalist position to a dedicated marketing role. Here is the updated JD. Does this match what you want to do?"

25-50 Employees: Compliance Gets Serious

At this stage, federal compliance thresholds start triggering. At 15 employees, Title VII and the ADA apply. At 20, ADEA and COBRA apply. At 50, FMLA and the ACA employer mandate apply. Each threshold adds requirements to your JDs: ADA essential functions language becomes legally critical, FLSA classification must be defensible, and EEO statements become functionally necessary rather than optional.

JDs also need to support a more formal hiring process. When the founder is no longer the only interviewer, the JD becomes the shared evaluation framework that ensures consistency across multiple interviewers. Without it, different interviewers evaluate candidates against different unstated criteria, which produces inconsistent hiring decisions and potential discrimination liability.

Job Descriptions for Remote and Hybrid Roles

Remote and hybrid roles require specific additions to the standard JD format. Candidates need to know the work arrangement before they apply, and you need to document the arrangement for compliance (tax implications, workers' compensation, state employment law jurisdiction).

What to Add for Remote Roles

The most common mistake in remote JDs: saying "remote" without specifying location restrictions. If you can only employ someone in the 3 states where you are registered, say so. A candidate who applies from a state where you cannot operate wastes their time and yours.

The Multi-State Compliance Issue

When you hire a remote employee in a different state, you become subject to that state’s employment laws: minimum wage, overtime rules, paid sick leave, salary transparency requirements, anti-discrimination protections, and workers’ compensation. You may also need to register as an employer in that state, file state tax withholding, and carry workers’ compensation insurance covering that state. This is not a reason to avoid remote hiring. It is a reason to specify which states you can hire in and to do the registration work before posting the JD.

The JD should clearly state: "This is a remote position. Candidates must reside in [list of states]." This prevents applications from states where you are not set up to employ people, and it documents your intent for compliance purposes.

Hybrid Role Clarity

Hybrid roles create more ambiguity than fully remote or fully in-office roles. The JD must specify exactly what "hybrid" means at your company: how many days in office, which days (fixed or flexible), whether the schedule is negotiable, and what happens during busy periods or special projects. "Hybrid: 3 days in office, 2 days remote. In-office days are Tuesday through Thursday. Schedule is fixed for the first 90 days and may become flexible after that based on performance." That is a hybrid policy. "Hybrid: some days in office, some remote" is not a policy. It is a source of future conflict.

8 Common Mistakes in Job Descriptions

These mistakes appear in the majority of small business job descriptions. Every one of them either reduces application quality, creates legal risk, or produces misaligned expectations that lead to early turnover.

The mistake behind most of these mistakes: writing the JD in a rush because you need to post the job today. Twenty minutes of additional thought on responsibilities and requirements prevents months of problems with mismatched candidates, legal exposure, and onboarding failures.

The Feedback Loop That Improves Every JD

After every hire, ask two questions. First, ask the hiring manager: "Did the candidates who applied match what we described in the JD? If not, what was the gap?" The answer reveals whether your JD is attracting the right people. Second, ask the new hire at their 30-day check-in: "Is the role what you expected based on the job description? What is different?" The answer reveals whether your JD accurately describes the reality of the job.

Feed both answers back into the JD. After 3 to 5 hires for the same or similar roles, your JDs become significantly more accurate because they incorporate real-world feedback from both sides of the hiring process. This is the cheapest quality improvement you can make: it costs nothing except asking two questions and spending 10 minutes updating the document.

The best job descriptions are not written by HR professionals with perfect compliance language. They are written by founders who know the role intimately, refined through multiple hiring cycles with feedback from real candidates and real employees. Start with a good-enough draft, use it, learn from it, and improve it. The fifth version of any JD is dramatically better than the first.

Frequently Asked Questions