Process and pipeline · 5 min read
How to write a job ad that gets applicants
A job ad is a short sales page for a role, written for someone scanning on a phone. This guide shows how to structure it, write requirements that filter fairly and make applying easy.
A job ad is not a job description
A job description is an internal document. It sets out the duties, reporting line and requirements of a role so that managers, HR and the person in the job agree on what it is. A job ad is a sales page for that role. It has one job: to get the right people to apply and help the wrong people decide not to.
Start from a good job description, then rewrite it for the reader. If you do not have one yet, our job description templates cover 40 common roles and give you a solid starting point for duties and requirements.
The person reading your ad is usually scanning a list on a phone. They are asking three questions. What is this job? Could I do it? Is it worth applying? Every part of the ad should answer one of those questions.
Use a title people search for
Use the plain title someone would type into a job board. Internal titles, grade codes and invented names hide your ad from the people you want.
- Use a standard title such as Data Analyst rather than an internal or playful name.
- Add seniority only where it matters, such as Senior, Lead, Junior or Graduate.
- Keep it short. Put team names, shift patterns and locations in the body or the location field.
- Do not stuff the title with keywords. One role, one title.
If you are unsure which title people use, look at how similar roles are titled on the job boards where you plan to post, and pick the most common plain version.
Structure the ad
A clear structure lets people find what they need in seconds. This order works for most roles.
- Opening, two or three sentences: what the role is, who it suits and why it is open now. Lead with the work, not the company history.
- What you will do: five to seven bullets on the main responsibilities, written as actions with outcomes. "Build weekly sales reports used by regional managers" tells the reader far more than "Responsible for reporting".
- What you need: the must-have requirements only. Keep this list short.
- Nice to have: a separate short list, clearly marked as optional.
- What we offer: pay or a pay range, working pattern, location or remote policy, and the benefits that are genuinely distinctive.
- About the team: a few sentences on what the team does and who the person will work with.
- How to apply: the steps, what happens next and roughly how long the process takes.
Write requirements that filter fairly
The requirements list does more filtering than any other part of the ad. A long list puts off capable people who do not tick every box, and lets through people who tick boxes without having the skill.
- Separate must-haves from nice-to-haves. A must-have is something without which the person cannot do the job in their first months.
- State skills and outcomes rather than years. "Can build a reporting model from raw sales data" is clearer than a number of years in a similar role.
- Ask for a degree only when the role truly needs one, and say whether equivalent experience counts.
- Remove requirements that are really personality labels, such as rockstar or self-starter. They tell readers little and can put off good applicants.
- Use the same must-haves when you screen CVs. If a requirement is not in the ad, do not reject people for lacking it.
That last point matters. The requirements you publish become the criteria for screening CVs against requirements, so write them as things you can actually check on a CV or in an interview. In Spark Careers Enterprise, skills are pulled from the job description and every CV is scored against them, so the requirements you write into the role are the same ones used to rank applicants.
Use language that widens the pool
Plain, specific language brings in more qualified applicants than clever copy.
- Write to the reader as you. "You will lead the weekly planning meeting" is clearer than "The successful candidate will lead".
- Use short sentences and common words. Many readers will be reading in a second or third language.
- Cut jargon and internal acronyms.
- Avoid words that suggest a particular age, gender or background, and describe the work instead. The guide on reducing bias in hiring covers this in more depth.
- Be honest about the hard parts, such as shifts, travel, targets or pressure. People who apply knowing this are more likely to stay.
- Check the employment and data protection rules where you hire before you state anything about age, health, nationality or right to work.
Pay, location and how to apply
Applicants want to know pay and location before they invest time in applying. Where you can, publish a pay range. Where you cannot, say how pay is set and at what stage you will discuss it. Be exact about location: the city, whether the role is on site, hybrid or remote, and how much travel it involves.
Then make applying easy. Every extra form field or account step loses applicants. Ask for a CV and the few details you truly need now. Leave long questionnaires for later stages. Tell people what will happen next and when they will hear from you, and then keep that promise. Each job in Spark Careers Enterprise has an apply link you can share on any channel and a careers page embed for your own website, so applications land in one pipeline wherever they come from.
Before you publish
- The title is a standard title people search for.
- The opening says what the job is in two or three sentences.
- Responsibilities are written as actions with outcomes.
- Must-haves are short, checkable and separate from nice-to-haves.
- Pay, location and working pattern are stated.
- The language is plain and describes the work, not an ideal person.
- Applying takes a few minutes and the next steps are clear.
- Someone outside the team has read the ad and could explain the job back to you.
Your next hire, start to finish, in one place.
Free workspace. No card. Full scoring free for 7 days.