Job Description Generator
Turn a set of bullet points into a structured, consistently formatted job description. Enter the role details and the lists you already have, and the page assembles them into a document with proper headings that you can publish or hand to a hiring manager.
It Structures Your Content Rather Than Inventing It
This is a formatting tool, not a writing tool. It does not produce responsibilities you did not supply or embellish a list of requirements. What it does is take the material you already have and put it into a consistent structure — the right headings, in the right order, with the boilerplate that every job posting needs and that people routinely forget. That distinction matters because a generated description that invents duties is worse than useless to a hiring manager.
- Seven single-line fields cover the role: title, department, employment type, seniority level, location, salary range and company name.
- Four multi-line fields take your lists — responsibilities, requirements, nice-to-have skills and benefits. One item per line, with blank lines ignored.
- The output is produced both as a rendered preview and as Markdown, so you can take the formatted version to a job board or the plain-text version into a document or a tracking system.
- Sections with no content are omitted entirely rather than shown empty, so a role without a benefits list does not carry an awkward heading with nothing under it.
Assembling a Description
- Enter the job title first. It is the only required field, and without it the page stops and says so rather than producing an untitled document.
- Fill in department, employment type and level. These appear on a single line beneath the title and are the fields most often left inconsistent across a set of postings.
- Add the location and salary range. The salary range is optional but it is omitted from the line cleanly if you leave it blank, so there is no trailing separator.
- Paste your responsibilities, one per line. Do not add bullet characters — they are added for you, and pasting them from another document produces doubled markers that look sloppy.
- Do the same for requirements, nice-to-have skills and benefits. Leave any of these blank if they do not apply.
- Read the preview and check the application section, which contains a generated email address that you should verify before using.
- Copy the Markdown if you need it in a plain-text system, or copy the rendered version into your applicant tracking system.
The Document Structure You Get
The assembled description always follows the same order. That consistency is the point — a set of postings from one organisation should look like a set, and that is hard to achieve when each one is written from scratch.
- The title is the top-level heading, followed immediately by a metadata line carrying department, employment type and seniority level.
- A second metadata line carries location, with the salary range appended only if you supplied one.
- An About Us section follows, containing whatever you wrote about the company.
- Responsibilities and Requirements come next, as bulleted lists in the order you typed them, with empty lines skipped.
- Nice to Have and Benefits appear only when their fields are non-empty, each as its own bulleted section.
- A How to Apply section closes the body with a generated careers email address.
- A closing equal opportunity statement is appended automatically, which is a standard requirement on most postings and one that is frequently forgotten when a description is written in a hurry.
Check the Generated Email Address Before You Publish
The application section builds an email address from the company name you entered, by lowercasing it and removing every character that is not a letter or a digit. This is a convenience with a real chance of being wrong, and it is worth being explicit about it.
- A company entered as Acme Corp produces an address on the acmecorp domain. That is a reasonable guess and nothing more.
- Names with spaces, ampersands, punctuation or non-Latin characters are all reduced to a compact string, so a trading name that differs from the registered domain will produce the wrong address.
- Every application that goes to a dead address is a candidate lost silently, since the applicant has no way to know their email bounced. Check the domain and the local part before publishing.
- If you would rather route applications through an applicant tracking system, replace the whole How to Apply section — the rest of the document is unaffected.
- The same caution applies to the salary range, which is passed through as text. It is not parsed or validated, so a range with a typo will appear exactly as typed.
Writing the Lists Themselves
| Alternative | Notes |
|---|
| Responsibilities | Describe the work rather than the person. Six to eight items is usually enough; longer lists read as a warning that the role is several jobs. Start each with a verb and keep them parallel in form. |
| Requirements | The items you would genuinely screen on. Long lists of wish-list requirements are the single most common reason strong candidates do not apply, and the effect is worse for anyone who takes stated requirements literally. |
| Nice to Have | Everything you would like but would not reject someone for. Having this section separately is what allows the requirements list to stay short, which is the point of splitting them. |
| Benefits | Specific and true. Vague statements about a great culture convey nothing, and listing something the role does not actually offer is a problem that surfaces at offer stage. |
Job Description Questions
Does the tool write the content for me?
No, and that is a deliberate limitation. Every responsibility, requirement and benefit comes from what you type. The tool supplies structure, ordering, consistent formatting and the standard closing statement. A description with plausible-sounding duties that nobody actually performs is a liability when the person starts.
What format is the output?
Both a rendered preview and Markdown. The preview is what you would paste into a system that accepts formatted text, and the Markdown is what you would take into a document, a repository or a tracking system that stores plain text. Markdown headings map cleanly onto the structure if you convert to a document format later.
Why is the equal opportunity statement included automatically?
Because it is expected on most public job postings and its absence is a compliance issue in many jurisdictions. Including it by default means the common case is correct without anyone having to remember. If your organisation uses different wording mandated by legal or policy, replace that closing paragraph after pasting.
Is the content I enter stored anywhere?
No. The document is assembled in the browser from the fields you fill in, and there is no submit action. Nothing is transmitted and nothing persists after the page is closed, which also means an unfinished description will not be waiting for you when you return.
Last verified: October 3, 2026
Launch Job Description Generator
All Tools · All Tools · About · How We Test · Contact · Privacy
Maintained by Huang Bin · Last updated October 3, 2026