# Writing a job description people can answer How to write a job description that a candidate can answer: outcomes before tasks, plain words, essential duties and advertising wording to check. Canonical URL: https://worldenterprise.org/insights/writing-a-job-description-people-can-answer/ Last updated: 2026-10-10 Publisher: World Enterprise, run by World Enterprise Group Incorporated *General information, not legal advice. Written October 10, 2026. The rules on job advertisements and job duties differ by country and state, so have your own counsel check anything you publish.* A job description does two jobs at once. It tells candidates what the work is, and it tells you, later, what you asked for. Most are written to do neither. They list a dozen tools, a vague mission and a set of adjectives, and a candidate cannot tell from them what a normal Tuesday looks like. If you are not an engineer, a designer or a salesperson yourself, the problem is sharper: you may not know which skills the work needs, so you copy a posting from another company and hope. A better posting is a short document a candidate can answer. They should be able to read it and say, in a sentence, whether they could do that work and whether they want to. This article describes a structure for writing one, and it flags the points where the wording of a posting meets the law. It is a writing guide, not a legal review. ## Write the outcome before the tasks Start with a paragraph that says why the role exists. Not "we are looking for a rockstar", but something a candidate can picture: "Customers ask us the same five questions every day, and no one owns the answers. This role owns them." A reader who finishes that paragraph knows the problem, and a good candidate starts thinking about how they would solve it. Then list what the person will do, in order of importance, in plain verbs. Five to seven items is plenty. Each should be something you could watch happen: "answer customer email and write the help-center article when a question repeats", not "support customer success initiatives". If you cannot say how you would tell whether an item had been done, it is not yet clear enough to hand to someone. ## Use the words your reader uses Federal guidance on plain language starts from the audience. Digital.gov, a US federal government site, says the Plain Writing Act of 2010 established the requirement that content for the public is written for its specific audience. The principle transfers well to a posting: write for the people who will read it, in the words they would use. In practice, this means cutting internal vocabulary and stacked nouns, preferring a short sentence to a long one, and explaining any abbreviation the first time it appears. Read the draft aloud to someone outside the company. Where they stumble, rewrite. ## Separate what the job requires from what you would like A common failure is a requirements list that mixes what the person must be able to do on the first day with what would be pleasant to have. Candidates read the whole list as demands, and some who could do the work rule themselves out. Use two short lists. The first holds the few abilities without which the work cannot be done. The second holds things that would help and that the person could learn. Keep the first list honest: ask of each item, "if a candidate lacked this but was strong at the rest, would I really turn them away?" If the answer is no, move it. The same discipline protects you later. In the United States, regulations under the Americans with Disabilities Act say that evidence of whether a particular function is essential includes, but is not limited to, a set of items that begins with the employer's judgment as to which functions are essential. Another item on that list is written job descriptions prepared before advertising or interviewing applicants for the job. In other words, the document you write now can become part of the record of what the job required. EEOC guidance describes an essential function as a fundamental duty of the position. Whether any specific duty of yours is essential is a legal question for your counsel, but writing the description carefully, and before you advertise, is the part within your control. Table: Two lists, two purposes | List | What goes in it | Test for each item | | --- | --- | --- | | Required | The duties and abilities the work cannot proceed without | Would I decline a strong candidate who lacked this? | | Helpful | Skills or experience that would speed things up and can be learned | Could the right person pick this up on the job? | | Left out | Tools you have not chosen, habits you like, wishes about personality | Does it describe the work, or my preferences? | ## Check the advertising wording Wording is where a posting can create legal exposure without anyone intending it. The US Equal Employment Opportunity Commission's page on prohibited employment practices says it is illegal for an employer to publish a job advertisement that shows a preference for, or discourages someone from applying for a job because of, race, color, religion, sex, national origin, age or disability, or genetic information. The page gives age as 40 or older and includes transgender status, sexual orientation and pregnancy within sex. That sentence is a good reason to read a draft for phrases that describe a person rather than the work. "Recent graduate", "young and energetic" and "digital native" describe people. "Comfortable learning new tools quickly" describes a skill. The test is the same one you applied to the requirements list: does this phrase say what the work needs, or who you imagine doing it? Rules elsewhere differ. Many countries and some US states regulate what a posting must or may say, including how pay is described, and this article cannot tell you what applies where you hire. That is a question to put to your lawyer before you publish, along with the question of whether the posting is going to candidates in more than one place. ## Say what happens next Candidates deserve to know how hiring will work, and saying so is also a courtesy to yourself, because it forces you to design the process. Add a short section: how to apply, what the stages are, who will read applications and whether you will tell candidates who are not selected. Avoid promising a reply time or a date you cannot control. If you plan to give every candidate the same questions, as described in [structured interviews for a small team](https://worldenterprise.org/insights/structured-interviews-for-a-small-team/), you can say so. Add a line on how a candidate can ask for an adjustment to the process. It tells them you have thought about it, and it gives them a way to ask without having to guess. **From outcome to posting.** A description that people can answer starts with the work and ends with the process, in this order. 1. **Outcome.** Describe what will be different in a year if the hire goes well. 2. **Requirements.** Separate what the job requires from what you would like. 3. **Wording check.** Read the text for wording that excludes people for reasons unrelated to the work. 4. **Next steps.** Tell applicants what happens after they apply and roughly when. ## A template of headings, not of words You do not need a template of sentences. A set of headings is enough to organize your thinking: > **Headings for a posting** > > Why this role exists. What you will do. What the work requires. What would help. How we work together. How to apply and what happens next. Each section should be written for a person who has never heard of your company. Fill each heading from the one-page record described in [your first hire](https://worldenterprise.org/insights/your-first-hire-what-to-settle-before-you-write-the-job/). If you cannot fill a heading, the decision behind it has not been made yet, and finishing the posting will not make it for you. The [glossary](https://worldenterprise.org/glossary/) may help with terms a candidate from outside the startup world has not met. ## Where this fits in a long effort A job description is the first document a new team member reads about the company, so it sets the tone for a relationship that, ideally, lasts years. The [first hire article](https://worldenterprise.org/insights/your-first-hire-what-to-settle-before-you-write-the-job/) covers what to settle before writing, and the [team handbook article](https://worldenterprise.org/insights/writing-down-how-a-remote-team-works-a-team-handbook/) covers what the hire will read next. The [longevity paradox](https://worldenterprise.org/insights/the-longevity-paradox-sprint-weekly-endure-for-a-decade/) article explains why a team that stays together is worth the care taken in hiring it. SBA resource partners, listed in the [ecosystem directory](https://worldenterprise.org/ecosystem/), offer counseling on first hires, and founder communities are a good place to ask how others wrote theirs. ## What this article cannot tell you This article cannot tell you whether any wording in your posting is lawful where you hire, what counts as an essential function of your job, or how to describe pay. It draws on three US federal sources and a federal plain-language guide, read on October 10, 2026, and the US rules it describes are not the rules of other countries. It does not cover the laws on advertising in a particular state, the rules on pay disclosure, rules for roles that require licenses, or the use of software to screen applications. The Plain Writing Act is cited for its principle only, and the article does not say who it binds. For any posting that carries legal risk, ask counsel before you publish. ## Sources - Prohibited employment policies and practices. U.S. Equal Employment Opportunity Commission. - 29 CFR 1630.2, Definitions (Americans with Disabilities Act regulations). Legal Information Institute, Cornell Law School. - Enforcement guidance on reasonable accommodation and undue hardship under the ADA. U.S. Equal Employment Opportunity Commission. - Plain language. Digital.gov, U.S. General Services Administration.