Should I include the salary range?

Yes. Listings with a salary range attract more and better-fit applicants, are now legally required in several US states and increasingly the EU, and signal transparency. Hiding pay wastes everyone's time when expectations mismatch at the offer stage. Post a real band, not a vague 'competitive'.

How long should a job listing be?

Long enough to inform, short enough to read. A strong overview paragraph, five to eight responsibilities, three to five real requirements, and a clear benefits list is plenty. Overlong lists of must-haves shrink your applicant pool, especially among candidates who would have been great but self-select out.

What is the difference between required and preferred qualifications?

Required qualifications are genuine dealbreakers; preferred are bonuses. Keep the required list ruthlessly short — every extra must-have disproportionately deters underrepresented candidates, who tend to apply only when they meet every line. Move anything you would still hire without into the nice-to-have list.

Why include a culture section?

Candidates choose where to apply partly on whether they will fit and thrive. A short, honest 'how we work' section about pace, communication style, and values helps the right people lean in and the wrong people opt out, improving the quality of your applicant pool before a single interview.

Should the listing have an equal-opportunity statement?

Yes — it is standard, often expected, and signals an inclusive process. The builder appends an equal-opportunity line and an offer of reasonable adjustments to the hiring process. Make sure your actual process lives up to it; a statement with no follow-through is worse than none.

What is the Careers Page Job Listing Builder?

Create a careers-page job post with an engaging role overview, responsibilities, required and preferred qualifications, benefits, and a culture section. Includes an equal-opportunity statement and exports clean Markdown ready to publish or paste into an ATS. It runs free in your browser on Gera Tools, with nothing uploaded.

Careers Page Job Listing Builder

Name: Careers Page Job Listing Builder
Creator: Gera Tools
License: https://creativecommons.org/licenses/by/4.0/

A job listing is your first interview — with the candidate

The candidates you most want are the ones with options, and they decide whether to apply in the first thirty seconds of reading your listing. A wall of generic must-haves and corporate filler loses them. This builder assembles a listing in the structure strong candidates expect — a real overview, scannable responsibilities, an honest split of required versus preferred, concrete benefits, and a culture section — so the right people lean in and the wrong ones opt out.

How it works

You provide the content and the tool arranges it into a standard, scannable job post:

Header          — title, company, location, type, salary range
Overview        — why the role exists and what you'll own
Responsibilities — what you'll actually do, day to day
Required        — genuine dealbreakers only
Preferred       — bonuses, never gatekeepers
Benefits        — concrete, not "competitive"
Culture         — how the team really works
+ equal-opportunity statement

The structure matters as much as the words: leading with the salary range and location lets candidates self-qualify immediately, and separating required from preferred qualifications keeps your applicant pool wide. The output is clean Markdown you can publish to a careers page or paste into most applicant-tracking systems.

Writing each section well

Overview (2–4 sentences)

Write why the role exists — what problem it solves, what you will own, and what a successful person in this role achieves in six months. Avoid describing the company’s history or funding. Candidates can find that elsewhere; what they cannot find without reading your listing is the honest scope and ambition of the role.

Weak: “We are a fast-growing startup looking for a passionate software engineer.”

Stronger: “We are rebuilding our checkout infrastructure to halve load times and cut fraud by 30%. You will own the backend API surface, partner with the payments team on integration, and define the observability layer for this system.”

Responsibilities (5–8 bullet points)

Use action verbs and be specific. Avoid “contribute to” and “assist with” — they are cover for uncertain scope. If the role owns a thing, say so. If it is supporting another function, be honest about that too.

Required vs preferred qualifications

The most common job-listing mistake is a required list that should be a preferred list. Research consistently shows that underrepresented candidates — particularly women — are more likely to apply only when they meet every stated requirement, while majority groups apply at 60%–70% match. Every line you move from “required” to “preferred” widens your pool without reducing quality. A useful test: would you still seriously consider a candidate who does not have this? If yes, it belongs in preferred.

Benefits

Replace vague phrases with specifics:

Weak: “competitive salary and benefits”
Better: “£70,000–£85,000 base salary; 30 days holiday + bank holidays; £2,000 annual learning budget; private health insurance (Bupa)”

Specifics let candidates self-qualify on benefits as easily as on salary. Vague benefits listings signal that the real package is not worth leading with.

Culture section

Be accurate rather than aspirational. “We move fast, ship weekly, and expect you to own your outcomes” is useful. “We are a family of passionate innovators who love what we do” is not. Candidates who want the former will lean in; those who want something slower will opt out — and finding that out at the interview stage is far more costly than finding it at the listing stage.

Equal-opportunity statement

The builder appends a standard equal-opportunity statement covering protected characteristics and offering reasonable adjustments to the hiring process. This is expected by candidates and legally relevant in the UK (Equality Act 2010), EU (Employment Equality Directive), and US (EEO). Make your actual process reflect the statement: diverse candidate shortlists, structured interviews, and consistent evaluation criteria are what back it up in practice.