Key Takeaways
- Use clear, search-friendly job titles and concise summaries to make your job descriptions easier for qualified candidates to find and understand.
- Define responsibilities, expectations, and essential qualifications clearly to attract relevant candidates and reduce mismatched applications.
- Create transparent, inclusive, and candidate-focused job descriptions by clearly communicating salary, benefits, work arrangements, and career opportunities.
A clear and compelling job description helps employers attract qualified candidates by explaining the role, responsibilities, requirements, salary, benefits, and working conditions in simple language. A strong job description uses a searchable job title, concise summary, realistic qualifications, specific expectations, and transparent employment information so candidates can quickly decide whether to apply.
Writing a clear and compelling job description is one of the most important steps in attracting qualified candidates. Before a job seeker submits an application, the job description is often their first detailed introduction to the role, its responsibilities, the employer’s expectations, and the overall employment opportunity. If that description is vague, confusing, unrealistic, or overloaded with corporate jargon, strong candidates may simply move on.

A well-written job description does much more than list duties and qualifications. It helps candidates quickly understand what the position involves, what skills are required, what they will be responsible for, and whether the opportunity aligns with their experience and career goals. At the same time, it allows employers and recruiters to communicate expectations more accurately and reduce applications from candidates who are poorly matched to the position.
Clarity is particularly important in an increasingly competitive recruitment market. Candidates frequently compare several opportunities at the same time, which means employers need to communicate the value of a role quickly. Clear job titles, concise summaries, realistic requirements, transparent employment information, and well-structured responsibilities can make a vacancy significantly easier to understand and evaluate.
Compelling does not mean exaggerated. Employers do not need to fill job descriptions with phrases such as “rockstar,” “ninja,” “world-class,” or “once-in-a-lifetime opportunity.” Instead, an effective job description should give candidates useful information: what they will do, who they will work with, what skills they need, how the position contributes to the organization, and what they can expect in return.
Job descriptions also influence the quality and efficiency of the wider recruitment process. When responsibilities and requirements are clearly defined, recruiters can assess candidates against more consistent criteria. Candidates can make better-informed decisions before applying, while hiring managers can establish clearer expectations for interviews, onboarding, and eventual job performance.
Search visibility matters as well. Candidates commonly discover vacancies through job portals, search engines, recruitment platforms, and increasingly AI-powered search and recommendation tools. Using recognizable job titles, relevant skills, location information, employment type, and natural job-related keywords can help employers make their vacancies easier for the right candidates to discover without resorting to keyword stuffing.
Artificial intelligence is also changing how job descriptions are created. Modern AI job description generators can help recruiters transform basic information about a position into a structured first draft, suggest responsibilities and qualifications, identify missing information, and improve readability. However, AI works best as an assistant rather than a replacement for human judgment. Employers still need to verify that every requirement, responsibility, salary detail, and employment condition accurately reflects the real position.
Ultimately, the best job descriptions balance the needs of both employers and candidates. They provide enough information to establish clear expectations while remaining concise and easy to scan. They distinguish genuine requirements from optional qualifications, communicate important employment details transparently, and give candidates a realistic picture of what working in the role would actually involve.
In this guide, we will explore the top 5 tips to write a clear and compelling job description, from choosing an accurate and search-friendly job title to defining responsibilities, setting realistic requirements, improving transparency, and writing with the candidate in mind. Whether you are a recruiter, HR professional, hiring manager, startup founder, or business owner, these practical job description writing tips can help you create stronger vacancies and attract candidates who are better suited to your roles.
Before we venture further into this article, we would like to share who we are and what we do.
About 9cv9
9cv9 is a business tech startup based in Singapore and Asia, with a strong presence all over the world.
With over ten years of startup and business experience, and being highly involved in connecting with thousands of companies and startups, the 9cv9 team has listed some of the top and best companies/tools in this review.
If you like to get your company listed in our top B2B software reviews, check out our world-class 9cv9 Media and PR service and pricing plans here.
Top 5 Tips to Write a Clear and Compelling Job Description
- Start With a Clear and Search-Friendly Job Title
- Write a Concise and Engaging Job Summary
- Clearly Define Responsibilities and Expectations
- Separate Essential Requirements From Preferred Qualifications
- Make the Job Description Transparent, Inclusive, and Candidate-Focused
1. Start With a Clear and Search-Friendly Job Title
The job title is one of the most important elements of a job description. It tells candidates what the position is, helps job boards categorize the vacancy, and influences whether the role appears when job seekers search for relevant opportunities.
A creative title might sound interesting internally, but candidates cannot apply for a vacancy they cannot find or understand. Someone looking for a software engineering position is much more likely to search for “Software Engineer” than “Code Ninja.” LinkedIn specifically recommends standardized, commonly used titles and gives this exact type of comparison: “Software Engineer” is preferable to “Code Ninja.”
The basic principle is straightforward: write the job title using the terminology your ideal candidates are likely to search for, rather than the terminology your organization happens to use internally.
Use a Recognizable, Industry-Standard Job Title
Start by identifying the primary function of the position. The title should allow a candidate to understand the general nature of the job without needing to read the description.
LinkedIn recommends using standardized titles commonly recognized within an industry because they are easier for candidates to understand and discover through search.
For example:
| Less Effective Job Title | Clearer Job Title | Why It Is Better |
|---|---|---|
| Code Ninja | Software Engineer | Matches commonly searched terminology |
| Marketing Rockstar | Marketing Specialist | Immediately communicates the function |
| Sales Superstar | Sales Executive | Uses recognizable industry language |
| Customer Happiness Hero | Customer Success Manager | Clearly defines the professional function |
| People Wizard | Human Resources Manager | Easier to understand and search |
| Data Guru | Data Analyst | Accurately identifies the occupation |
| Growth Hacker Extraordinaire | Growth Marketing Manager | Defines both function and specialization |
| Office Ninja | Administrative Assistant | Uses an established occupational title |
This principle is supported across major recruitment platforms. Indeed’s current job-posting standards tell employers to keep titles simple, short and accurate and to use the actual job title rather than clickbait or unclear wording.
Think About What Candidates Actually Search For
A search-friendly job title should closely reflect the terminology a qualified candidate would enter into a job portal or search engine.
For example, imagine that a company internally calls its salespeople “Business Growth Partners.”
The internal title may make sense within the organization, but candidates might instead be searching for:
- Business Development Executive
- Sales Executive
- Account Executive
- Business Development Manager
Using the appropriate conventional title gives the vacancy a better chance of matching those searches.
LinkedIn explicitly recommends searchable titles over flashy alternatives, noting that candidates are more likely to search for a conventional title such as “Sales Manager” than an unconventional equivalent such as “Head of Relationship Builders.”
Add Specificity When It Helps Candidates Identify the Role
Being searchable does not necessarily mean being generic.
Sometimes a broad title can attract candidates from too many unrelated backgrounds. Adding a relevant specialization can make the position considerably clearer.
Consider these examples:
| Too Broad | More Specific | Candidate Intent |
|---|---|---|
| Developer | Front-End Developer | Front-end engineering |
| Engineer | DevOps Engineer | Infrastructure and DevOps |
| Marketing Manager | Digital Marketing Manager | Digital marketing |
| Designer | UX/UI Designer | Product and interface design |
| Sales Representative | Pharmaceutical Sales Representative | Pharmaceutical sales |
| Accountant | Management Accountant | Management accounting |
| Recruiter | Technical Recruiter | Technology recruitment |
| Analyst | Financial Analyst | Finance |
| Content Manager | SEO Content Manager | Search-focused content |
Indeed specifically uses “Pharmaceutical Sales Representative” as an example of how adding a relevant field can make “Sales Representative” more precise.
LinkedIn similarly recommends including relevant keywords and specialties. For example, if the vacancy specifically requires Java expertise, a title such as “Java Software Developer” can communicate that specialization more effectively than a generic “Developer.”
Include Seniority When It Meaningfully Changes the Role
Seniority is another useful search qualifier.
Terms such as Junior, Senior, Lead, Head, Manager and Director can help candidates immediately understand the expected experience and responsibility level.
| Generic Title | Better Title | Information Added |
|---|---|---|
| Accountant | Junior Accountant | Entry/junior level |
| Software Engineer | Senior Software Engineer | Advanced experience |
| Designer | Lead Product Designer | Leadership responsibility |
| Marketing | Marketing Manager | Management responsibility |
| Sales | Sales Director | Senior leadership |
| Data Analyst | Senior Data Analyst | Higher experience level |
Both LinkedIn and Indeed recommend specifying seniority when it is genuinely relevant to the position.
However, employers should not inflate titles merely to make positions sound more prestigious. Calling an individual contributor a “Director” when the role has no director-level responsibilities can create inaccurate candidate expectations.
Keep the Job Title Concise
Search-friendly titles should generally be short enough to scan quickly while containing enough information to distinguish the position.
Indeed recommends keeping job titles short and clear. In separate guidance on choosing job titles, Indeed suggests aiming for approximately 50–60 characters and avoiding titles longer than 80 characters where possible.
That does not mean every title needs to reach 50 characters. In many cases, shorter is better:
| Job Title | Approximate Quality |
|---|---|
| Accountant | Clear but broad |
| Senior Accountant | Clear and specific |
| Senior Management Accountant | Highly descriptive when accurate |
| AMAZING Senior Accountant – Great Salary – Apply Today!!! | Cluttered and promotional |
The title is an identifier, not an advertisement. Compensation, benefits, schedules, bonuses and promotional messaging belong elsewhere in the job description.
Do Not Stuff Extra Information Into the Job Title
A common mistake is trying to turn the job title into a miniature advertisement.
For example:
Poor: Senior Software Engineer – Remote – $120K – Great Benefits – Apply Now!
Better: Senior Software Engineer
The salary, remote-work policy and benefits can still be important selling points, but they should appear in the appropriate fields or sections.
Google’s JobPosting structured-data documentation makes this distinction particularly clear. Google says the title property should contain the job title itself, rather than information such as addresses, dates, salaries, company names or job codes. Google also recommends concise and readable titles.
Indeed follows a similar policy, advising employers not to place details such as pay, location or shifts inside the job title.
Avoid Internal Acronyms and Company-Specific Terminology
Internal titles can become particularly problematic when organizations use abbreviations that outsiders do not recognize.
For example:
| Internal Title | Candidate-Friendly Alternative |
|---|---|
| SSE II | Senior Software Engineer |
| AE-L2 | Account Executive |
| TA Spec III | Talent Acquisition Specialist |
| CS Ops L2 | Customer Success Operations Specialist |
| MKTG Exec B | Marketing Executive |
An employee already working at the company may understand “SSE II.” A candidate encountering the organization for the first time may not.
Indeed specifically recommends avoiding abbreviations and internal jargon that job seekers are unlikely to recognize or search for.
Where an internal title is required for HR or organizational purposes, employers can retain it internally while using a more recognizable external title for recruitment, provided the external title accurately represents the position.
Avoid Combining Multiple Jobs Into One Title
Another search problem occurs when employers attempt to advertise several functions simultaneously.
For example:
Poor: Sales / Marketing / Customer Service / Admin Executive
What is the actual job?
Candidates cannot easily determine whether the company needs a salesperson, marketer, customer service representative or administrator.
Indeed’s 2026 guidance specifically recommends avoiding multiple roles in a single title and creating separate postings where appropriate.
A better approach is to identify the primary responsibility:
Better: Sales Executive
Then explain secondary responsibilities within the job description.
If the position genuinely combines two closely related disciplines, a combined title can sometimes be appropriate:
Acceptable: Content Marketing and SEO Specialist
The difference is that these functions naturally overlap and accurately describe a coherent position.
Avoid Keyword Stuffing
SEO optimization does not mean inserting every potentially relevant keyword into the title.
For example:
Poor: Digital Marketing Manager SEO SEM PPC Google Ads Social Media Marketing Manager
Better: Digital Marketing Manager
Relevant skills such as SEO, paid search, Google Ads and social media marketing can appear naturally throughout the job description.
Indeed explicitly prohibits keyword stuffing intended to manipulate search visibility, including repeating keywords and inserting long lists of job titles.
Search optimization should therefore focus on relevance rather than repetition.
Use Gender-Neutral and Inclusive Job Titles
Employers should also review whether their titles contain outdated or unnecessarily gendered terminology.
For example:
| Avoid | Consider Instead |
|---|---|
| Salesman | Sales Representative |
| Saleswoman | Sales Representative |
| Waitress | Server |
| Doorman | Door Attendant |
| Cameraman | Camera Operator |
| Chairman | Chair or Chairperson |
Indeed’s current guidance specifically recommends gender-neutral titles and provides examples such as replacing “waitress” with “server.”
Inclusive titles are not merely a matter of wording. They make the vacancy understandable and relevant to the widest appropriate candidate audience.
Understand the Connection Between Job Titles and Google Search
Job-title optimization can extend beyond recruitment platforms.
Employers publishing vacancies on their own career websites can use Google’s JobPosting structured data. When properly implemented, this markup can make job pages eligible for Google’s dedicated job-search experience. Google says job seekers can filter opportunities by criteria including job title and location, helping employers reach applicants looking for that type of role.
For the title itself, Google recommends a concise representation of the actual job, such as:
Software Engineer
rather than promotional wording or unrelated information.
This creates an important alignment between candidate experience, job-board optimization and technical SEO: the clearest title is frequently also the most search-friendly title.
Job Title Optimization Matrix
Before publishing a vacancy, employers can evaluate the proposed title against several criteria.
| Criterion | Weak | Acceptable | Strong |
|---|---|---|---|
| Clarity | Candidate cannot identify role | General function is apparent | Role immediately understood |
| Searchability | Internal or invented terminology | Partially recognizable | Common industry terminology |
| Specificity | Extremely broad | Function identified | Function + useful specialization |
| Seniority | Misleading or absent when essential | Implied | Clearly stated where relevant |
| Length | Long promotional sentence | Moderately concise | Short and focused |
| Keywords | Stuffed with keywords | Main keyword included | Natural primary job title |
| Jargon | Heavy internal terminology | Some specialist terminology | Candidate-friendly terminology |
| Accuracy | Exaggerates responsibilities | Mostly accurate | Directly reflects actual role |
| Inclusivity | Gendered/exclusionary | Neutral overall | Clearly neutral and professional |
A strong title should score well across most or all of these dimensions.
Practical Job Title Formula
For many vacancies, employers can use a simple structure:
Seniority + Core Role + Relevant Specialization
Examples include:
Senior Software Engineer
Junior Financial Analyst
Senior Backend Engineer – Python
Digital Marketing Manager
Technical Recruitment Consultant
Enterprise Account Executive
Senior Product Designer
Not every title requires all three elements. A straightforward title such as Accountant, Barista, UX Designer or Warehouse Associate may already communicate everything candidates need.
The objective is not to build the longest possible title. It is to include only the information that materially helps candidates identify the opportunity.
Quick Test Before Publishing the Job Title
Ask one simple question:
If a qualified candidate saw only this title in a search result, would they immediately understand what job we are hiring for?
If the answer is no, simplify or clarify it.
A title such as “Growth Rockstar” requires interpretation. “Growth Marketing Manager” does not.
A title such as “SWE III” assumes internal knowledge. “Senior Software Engineer” communicates the position immediately.
A title such as “Amazing Opportunity – Apply Now!” communicates almost nothing about the occupation.
The strongest job titles are therefore rarely the most creative. They are the titles that accurately describe the position, align with the terminology candidates use, communicate relevant seniority or specialization, and remain concise enough to work effectively across search engines and job platforms. This approach improves discoverability while giving candidates a clearer understanding of the opportunity from the very beginning.
2. Write a Concise and Engaging Job Summary
After the job title captures a candidate’s attention, the job summary needs to convince them that the opportunity is worth exploring. This opening section should quickly explain what the role is, why it exists, where it fits within the organization, and what makes the opportunity attractive.
Indeed recommends opening with a strong summary that gives candidates an overview of the company and expectations for the position while highlighting what makes the employer distinctive. LinkedIn similarly recommends explaining why the role matters, the team or mission it supports, and the impact the successful candidate can make.
The goal is not to summarize every responsibility and qualification. Those details belong later in the job description. Instead, think of the job summary as a high-value preview of the opportunity.
Keep the Job Summary Short and Focused
Candidates should not need to read several paragraphs before understanding what the position involves.
LinkedIn recommends keeping an opening job summary to approximately three to four sentences. Its broader analysis also found a relationship between brevity and application behavior: job posts containing 150 words or fewer saw candidates apply nearly 18% more frequently than posts containing 450–600 words.
Earlier LinkedIn analysis of job-post performance found a similar pattern. Posts containing 1–300 words had an apply rate 8.4% above average, while posts containing 301–600 words performed 3.4% below average. LinkedIn also reported that more than half of its job views were occurring on mobile devices in that dataset, reinforcing the value of concise, scannable content.
These figures concern the broader job post rather than only the summary, but the underlying lesson is useful: brevity can improve usability when it removes unnecessary information rather than useful details.
| Job Summary Approach | Effect on Candidate | Recommendation |
|---|---|---|
| 1–2 vague sentences | Too little information | Add role purpose and impact |
| 3–4 focused sentences | Fast and informative | Strong default |
| Several dense paragraphs | Requires unnecessary reading | Condense |
| Long company history | Distracts from opportunity | Move elsewhere |
| Responsibilities copied into summary | Creates repetition | Summarize instead |
| Short but highly generic | Provides little value | Add specifics |
A concise summary should therefore be information-dense rather than information-poor.
Answer the Candidate’s Most Important Questions Quickly
A strong opening summary should help a candidate answer several questions almost immediately:
- What will I actually be doing?
- Why does this role exist?
- What team or function will I join?
- What impact could I make?
- What is distinctive about this opportunity?
- Why might I want to continue reading?
For example, compare these two summaries.
Weak example:
We are looking for a highly motivated Marketing Manager to join our dynamic and fast-growing organization. The successful candidate will be responsible for various marketing activities and work with multiple stakeholders.
The paragraph is technically understandable, but almost every phrase could apply to thousands of vacancies.
Stronger example:
We are hiring a Digital Marketing Manager to lead paid search, SEO and content acquisition for our B2B software business. You will work with the sales and product teams to grow qualified inbound leads across Southeast Asia. This role is ideal for a performance-focused marketer who wants ownership of acquisition strategy and measurable revenue impact.
The second version answers substantially more candidate questions without becoming much longer.
Explain What the Role Actually Does
The first sentence should normally identify the position’s central purpose.
Avoid openings dominated by adjectives:
Weak:
We are seeking an energetic, passionate, ambitious, innovative and results-driven individual to join our amazing team.
After reading the sentence, the candidate still does not know what they will do.
A better opening would be:
We are hiring a Senior Account Executive to develop new enterprise customers and manage the sales process from initial prospecting through contract close.
The second version immediately communicates the function of the role.
Indeed emphasizes that job descriptions should provide enough detail for candidates to assess whether they are qualified, while its 2026 employer guidance recommends leading with the information candidates need to quickly understand the role and decide whether it could be a fit.
Explain Why the Role Matters
A job summary becomes more compelling when it explains not only what the employee will do, but why their work matters.
Compare:
Task-focused:
You will create reports, analyze customer data and maintain dashboards.
Impact-focused:
You will analyze customer and product data to help our leadership team identify growth opportunities, improve retention and make faster commercial decisions.
The responsibilities may ultimately be similar, but the second version connects the employee’s work to business outcomes.
LinkedIn recommends using the summary to explain the importance of the position, how it fits within the organizational structure, and the mission or team it supports.
A useful formula is:
Role + Core Responsibility + Business Impact
For example:
As a Customer Success Manager, you will manage a portfolio of B2B customers, help them achieve measurable value from our platform and identify opportunities to improve retention and account growth.
Give Candidates a Reason to Continue Reading
A job summary should contain at least one meaningful reason why the opportunity deserves attention.
Depending on the role, that reason could include:
| Candidate Motivation | Information to Highlight |
|---|---|
| Career development | Mentorship, ownership, advancement |
| Professional impact | Influence over products, customers or strategy |
| Leadership | Team-building or decision-making authority |
| Innovation | New technology or product development |
| Flexibility | Remote or hybrid arrangement |
| Scale | Large customer base, market or operation |
| Learning | Exposure to new markets or technologies |
| Mission | Meaningful organizational objective |
| Growth | Expanding business or team |
| Autonomy | Ownership over projects or functions |
The important distinction is that these should be real characteristics of the position, not generic recruitment claims.
Instead of:
Join an exciting company with amazing career opportunities.
Consider:
You will be the first dedicated product marketer on the team, giving you ownership of positioning, launches and sales enablement as the company expands into three new markets.
Specificity makes the opportunity tangible.
Focus on the Candidate, Not Only the Company
Some job summaries spend almost the entire opening talking about the employer.
For example:
Founded in 2012, ABC Technologies is an innovative market-leading organization providing world-class solutions to clients worldwide. We have offices in six countries and are committed to excellence, integrity and innovation.
This information may be useful, but it does not yet explain the opportunity.
A better balance would be:
Join ABC Technologies as a Product Designer and help redesign the workflows used by our enterprise customers across six markets. Working alongside product managers and engineers, you will own research, interaction design and usability testing for a major product area.
Company information can then follow elsewhere.
Indeed describes the job description as an introduction to both the company and its employer brand, while recommending that the summary engage candidates with information about what makes the organization distinctive.
Replace Generic Claims With Evidence
Recruitment language becomes less persuasive when every claim is based on adjectives.
Consider replacing promotional phrases with specific facts whenever those facts are available.
| Generic Claim | More Informative Alternative |
|---|---|
| Fast-growing company | “Our engineering team is expanding from 20 to 35 people.” |
| Global organization | “Our customers operate across 18 countries.” |
| Exciting opportunity | “You will launch our first enterprise sales function.” |
| Innovative company | “You will work on our AI-powered recruitment platform.” |
| Great career progression | “The role can progress into team leadership as the function expands.” |
| Make an impact | “Your campaigns will directly influence qualified pipeline generation.” |
| Dynamic environment | “You will work directly with product, sales and customer success.” |
Only use figures that can be verified internally before publishing.
A useful rule is:
Specific evidence > promotional adjectives.
Use the Job Summary to Differentiate Similar Vacancies
Candidates may encounter dozens of vacancies with the same title.
Consider three companies advertising a Software Engineer position.
| Employer | Generic Summary | Differentiated Angle |
|---|---|---|
| Startup | “Join our engineering team.” | Build core product features with significant ownership |
| Bank | “Develop software applications.” | Modernize high-volume financial infrastructure |
| E-commerce company | “Work on our platform.” | Improve checkout systems handling large transaction volumes |
The title tells candidates what the occupation is.
The summary should tell them why this particular version of the occupation is interesting.
Prioritize Information Candidates Actually Care About
The summary should not become a dumping ground for every employment detail, but understanding candidate priorities can help employers decide what deserves prominent placement.
LinkedIn research found that 61% of candidates considered compensation the most important part of a job description, while qualifications and job details were each identified by 49%.
Separate LinkedIn research found that 90% of candidates identified responsibilities as one of the key elements helping them decide whether to apply.
| Information | Where to Communicate It |
|---|---|
| Core purpose of role | Summary |
| Major impact | Summary |
| Team or reporting context | Summary or role section |
| Primary responsibilities | Responsibilities section |
| Salary range | Compensation section or prominently near top |
| Required skills | Qualifications |
| Benefits | Benefits section |
| Company history | Company section |
| Full hiring process | Application/hiring section |
The summary should therefore preview the most important information without attempting to replace the complete job description.
Make the Summary Easy to Scan on Mobile
Job seekers frequently browse opportunities quickly and across different devices.
Indeed’s 2026 employer guidance specifically notes that many people skim job postings on phones or between other activities. It recommends short paragraphs, clear headings and placing important details such as location, work pattern, pay and top qualifications prominently.
Avoid a summary like this:
We are seeking an experienced digital marketing professional who possesses extensive knowledge across multiple digital marketing channels and who will be responsible for developing, implementing, managing and optimizing strategies across the organization while collaborating with different internal and external stakeholders…
Instead, break the information into shorter sentences:
We are hiring a Digital Marketing Manager to lead our customer acquisition strategy. You will own SEO, paid search and content performance while working closely with sales. Your goal will be to increase qualified pipeline and improve acquisition efficiency.
The second version is easier to process, particularly on a small screen.
Match the Tone to the Role and Employer Brand
Engaging does not mean excessively casual.
A startup hiring a social media creator may appropriately use a different tone from a financial institution hiring a compliance director.
| Role | Suitable Tone |
|---|---|
| Graduate Marketing Assistant | Accessible, encouraging |
| Software Engineer | Direct, technical, informative |
| Creative Director | Confident, creative |
| Finance Manager | Professional, precise |
| Compliance Director | Formal, authoritative |
| Hospitality Associate | Warm, welcoming |
| Senior Executive | Strategic, concise |
There is also evidence that excessive informality can hurt recruitment outcomes. LinkedIn reports research in which candidates reading extremely casual job descriptions were two to four times less likely to apply and up to four times more likely to dislike the employer.
The objective should therefore be human and engaging without becoming unprofessional.
Avoid Corporate Jargon and Empty Recruitment Language
Phrases such as these add little information:
- Work hard, play hard
- Rockstar
- Ninja
- Guru
- Self-starter
- Wear many hats
- Hit the ground running
- Dynamic environment
- World-class team
- Exciting opportunity
Some may occasionally be appropriate, but they should not substitute for actual information.
LinkedIn’s job-post quality guidelines recommend avoiding excessive internal jargon, ambiguous responsibilities, unprofessional language and spam-like wording.
Instead of:
We need a rockstar self-starter ready to hit the ground running in our fast-paced environment.
Write:
You will independently manage five to eight enterprise accounts and coordinate implementation projects with our product and customer success teams.
The second statement gives candidates information they can actually evaluate.
Adapt the Summary to the Seniority of the Position
Different candidates care about different dimensions of a role.
LinkedIn recommends emphasizing mentorship and growth opportunities for entry-level positions, while senior positions can focus more heavily on leadership challenges and strategic impact.
| Seniority | Useful Summary Focus |
|---|---|
| Internship | Learning, mentorship, practical experience |
| Entry-level | Development, training, first responsibilities |
| Mid-level | Ownership, specialization, measurable impact |
| Senior | Autonomy, complex problems, strategic contribution |
| Manager | Team leadership, performance, decision-making |
| Director | Organizational strategy, transformation, scale |
| Executive | Business direction, P&L, market and organizational impact |
For example:
Entry-level:
Join our finance team as a Junior Financial Analyst and build practical experience in forecasting, reporting and commercial analysis. You will work closely with senior analysts and receive structured support while contributing to monthly business reviews.
Senior-level:
As Director of Finance, you will lead financial planning and commercial analysis across the business, advise the executive team on strategic decisions and build the finance function required for our next stage of growth.
Both are engaging, but they appeal to different professional motivations.
Use a Simple Job Summary Formula
Employers struggling to write the opening can use this structure:
Who we need + What they will own + Why it matters + Why the opportunity is distinctive
For example:
We are hiring a Senior Product Manager to lead the development of our B2B recruitment platform. You will own product strategy and roadmap execution while working directly with engineering, design and commercial teams. Your work will shape how employers discover and hire candidates across multiple markets. This role offers significant ownership over a core product area as the platform expands.
Another useful structure is:
Role + Mission + Impact + Opportunity
The formula prevents the summary from turning into either an empty marketing paragraph or a miniature version of the entire job description.
Before-and-After Job Summary Example
Before:
ABC Company is seeking a highly motivated and experienced Sales Manager to join our dynamic team. The successful candidate should possess excellent communication and interpersonal skills and be capable of working in a fast-paced environment. This is an exciting opportunity for the right candidate.
The problems are substantial:
| Problem | Why It Weakens the Summary |
|---|---|
| “Highly motivated” | Generic |
| “Dynamic team” | Provides no evidence |
| “Excellent communication” | Says little about actual job |
| “Fast-paced environment” | Vague |
| “Exciting opportunity” | Unsupported claim |
| No responsibilities | Candidate cannot evaluate role |
| No business impact | Purpose remains unclear |
After:
We are hiring a B2B Sales Manager to lead a five-person sales team and grow enterprise revenue across Southeast Asia. You will own pipeline strategy, coach account executives and work with marketing to improve qualified lead generation. The role offers direct responsibility for regional revenue growth and the opportunity to build the sales processes supporting our next stage of expansion.
The revised summary explains:
- What the job is.
- What the employee owns.
- Who they manage.
- Which market they cover.
- Who they collaborate with.
- What outcome they influence.
- Why the opportunity could be professionally interesting.
Job Summary Quality Matrix
Before publishing, evaluate the summary against the following criteria:
| Criterion | Weak | Good | Excellent |
|---|---|---|---|
| Role clarity | Role remains vague | Main function explained | Purpose immediately obvious |
| Length | Dense or excessively long | Concise | 3–4 information-rich sentences |
| Responsibilities | Missing | Main responsibility mentioned | Ownership clearly communicated |
| Impact | Not mentioned | General impact | Specific business/customer impact |
| Candidate value | Employer-focused | Some benefits communicated | Clear reason to consider role |
| Company context | Generic corporate language | Relevant context | Context directly supports opportunity |
| Specificity | Mostly adjectives | Some concrete details | Evidence and measurable context |
| Readability | Dense paragraph | Easy to read | Highly scannable |
| Tone | Robotic or excessively casual | Professional | Professional and brand-appropriate |
| Repetition | Repeats later sections | Limited duplication | Efficiently previews key information |
Remember That the Summary Is Only the Opening
Conciseness in the summary should not result in an incomplete overall job posting.
Google’s job-posting documentation requires the description used for eligible JobPosting structured data to provide a complete representation of the job, including information such as responsibilities, qualifications, skills, working hours, education requirements and experience requirements. Google has separately advised publishers to provide complete descriptions so job seekers have enough information to make informed decisions.
That creates an important distinction:
The job summary should be concise. The overall job description should be complete.
A strong job summary gets candidates interested enough to continue reading. The sections that follow then provide the responsibilities, requirements, compensation, benefits, working arrangements and other information they need to decide whether to apply.
The best summaries therefore avoid both extremes. They are neither long corporate introductions nor vague two-line statements. They quickly communicate what the candidate will do, why the work matters, where the role fits and why the opportunity deserves their attention.
3. Clearly Define Responsibilities and Expectations
A compelling job description should leave candidates with a realistic understanding of what they will actually do after they are hired. While an engaging introduction may attract attention, clearly defined responsibilities and expectations help candidates decide whether the position genuinely matches their skills, interests, and career goals.
This section deserves particular attention because candidates actively look for it. LinkedIn reports that 90% of candidates consider responsibilities one of the key pieces of information that help them decide whether to apply. Its analysis of millions of paid U.S. job postings also found that employers devoted approximately 45% of job-description character count to responsibilities.
The objective, however, is not to create the longest possible list. A strong responsibilities section identifies the work that matters most, distinguishes everyday activities from longer-term outcomes, and gives candidates a realistic picture of how success will be measured.
Focus on the Core Responsibilities of the Role
Start with the activities that genuinely define the position.
If a responsibility represents only a tiny fraction of an employee’s time, it probably should not receive the same prominence as a core function.
For example, a Digital Marketing Manager might have dozens of individual activities, but the position could potentially be summarized around several major areas:
- Develop and execute digital acquisition strategies.
- Manage paid search and paid social campaigns.
- Oversee SEO and content performance.
- Analyze acquisition costs and conversion performance.
- Collaborate with sales on lead-generation initiatives.
- Manage marketing budgets and forecasts.
- Report campaign performance to management.
Candidates now have a much clearer picture of the position than they would get from a vague statement such as:
Responsible for all marketing-related activities and other duties assigned by management.
Indeed recommends outlining the position’s primary responsibilities, highlighting duties unique to the organization, and describing day-to-day activities so candidates can determine whether the position matches their capabilities.
Prioritize Responsibilities Instead of Creating a Laundry List
More responsibilities do not automatically create a better job description.
LinkedIn’s analysis of millions of paid U.S. job postings from April through September 2023 found that the responsibilities sections of higher-performing job posts were 9% shorter than those of lower-performing posts. High-performing job descriptions overall were also 7% shorter.
This suggests an important distinction:
Comprehensive does not mean exhaustive.
| Weak Approach | Better Approach |
|---|---|
| List every possible task | Focus on core responsibilities |
| 20–30 repetitive duties | Consolidate related activities |
| Include extremely minor administrative work | Prioritize meaningful work |
| Repeat requirements as responsibilities | Keep responsibilities and qualifications distinct |
| Describe every possible future scenario | Explain normal expectations |
| Use vague catch-all statements | Define actual areas of ownership |
A useful editing question is:
Would removing this responsibility materially change a candidate’s understanding of the role?
If not, it may not need prominent placement.
Describe What the Employee Will Actually Do
Avoid responsibilities that sound professional but communicate almost nothing.
Consider the following examples:
| Vague Responsibility | Clearer Responsibility |
|---|---|
| Handle marketing activities | Plan and execute paid search and social campaigns |
| Manage clients | Manage a portfolio of 20–30 B2B customer accounts |
| Support the sales team | Prepare proposals, sales reports and customer presentations |
| Work with stakeholders | Coordinate product launches with product, sales and marketing teams |
| Analyze data | Analyze customer retention and product-usage data |
| Manage social media | Plan and publish content across LinkedIn, Instagram and TikTok |
| Support recruitment | Source, screen and coordinate interviews for technical candidates |
| Manage projects | Own project timelines, dependencies, risks and stakeholder reporting |
| Handle finances | Prepare monthly management accounts and financial forecasts |
| Improve SEO | Conduct keyword research, optimize content and monitor organic performance |
Specificity helps candidates visualize their working day.
It can also improve recruitment efficiency because applicants can make a more informed decision about whether they possess the necessary experience.
Use Strong Action Verbs
Responsibilities become clearer when they begin with verbs describing observable work.
Useful verbs include:
| Function | Useful Action Verbs |
|---|---|
| Management | Lead, manage, supervise, coordinate, oversee |
| Creation | Design, develop, create, produce, build |
| Analysis | Analyze, evaluate, measure, investigate, forecast |
| Improvement | Optimize, improve, streamline, automate, enhance |
| Communication | Present, communicate, advise, negotiate, report |
| Execution | Implement, execute, deliver, operate, maintain |
| Commercial | Sell, develop, negotiate, retain, grow |
| Recruitment | Source, screen, interview, assess, onboard |
| Technical | Develop, test, deploy, configure, troubleshoot |
| Strategy | Plan, define, prioritize, formulate, recommend |
Compare:
Weak:
SEO responsibilities.
Better:
Develop and execute the company’s organic search strategy.
Even better:
Develop and execute an organic search strategy designed to increase qualified traffic and inbound leads.
The progression moves from a topic, to an activity, to an activity connected with an outcome.
Explain Outcomes, Not Just Activities
One of the most effective improvements employers can make is describing what the employee is expected to accomplish.
Candidates want to understand not only:
“What will I do?”
but also:
“What am I expected to achieve?”
LinkedIn recommends including explicit performance goals because measurable expectations provide candidates with a more accurate understanding of the role and what successful performance looks like.
Consider these examples:
| Activity-Based | Outcome-Oriented |
|---|---|
| Manage paid advertising | Manage paid acquisition campaigns to generate qualified sales opportunities efficiently |
| Write blog posts | Produce search-focused content that increases relevant organic traffic |
| Contact prospects | Build qualified sales pipeline through outbound prospecting |
| Answer customer questions | Resolve customer issues efficiently while maintaining service quality |
| Analyze product data | Identify behavioral patterns that inform product and retention decisions |
| Recruit candidates | Build qualified candidate pipelines for priority vacancies |
| Manage projects | Deliver projects against agreed scope, timeline and budget |
| Optimize website | Improve website conversion performance through testing and analysis |
The outcome-oriented versions provide context without requiring unrealistic promises.
Distinguish Responsibilities From Performance Expectations
Responsibilities and expectations are related, but they are not identical.
Responsibilities describe what the employee owns.
Expectations describe the standard or outcome associated with that ownership.
For example:
| Responsibility | Expectation |
|---|---|
| Manage customer accounts | Maintain strong retention and customer satisfaction |
| Produce monthly reports | Deliver accurate reports by agreed deadlines |
| Manage paid campaigns | Improve acquisition efficiency within agreed budgets |
| Lead engineering team | Maintain delivery quality and develop team capability |
| Source candidates | Maintain qualified pipelines for priority vacancies |
| Manage projects | Deliver against scope, budget and schedule |
| Handle support tickets | Resolve customer issues according to service standards |
A job description becomes significantly more informative when candidates understand both dimensions.
Separate Day-to-Day Responsibilities From Longer-Term Expectations
Some positions contain both routine activities and strategic objectives.
Indeed specifically recommends considering a distinction between day-to-day responsibilities and longer-term expectations or outcomes so candidates understand both the immediate and strategic dimensions of the position.
For example:
Day-to-Day Responsibilities
- Monitor paid advertising campaigns.
- Review campaign performance and budgets.
- Coordinate with designers and copywriters.
- Analyze conversion data.
- Prepare weekly performance reports.
Longer-Term Expectations
- Reduce customer acquisition costs.
- Improve marketing attribution.
- Expand acquisition into new channels.
- Build repeatable campaign processes.
- Improve alignment between marketing and sales.
This structure is particularly useful for management, product, marketing, engineering and strategy roles where employees perform regular operational work while pursuing longer-term objectives.
Explain What Success Looks Like
A candidate should ideally be able to imagine what successful performance might look like after joining the organization.
A useful framework is:
| Timeframe | Example Expectation |
|---|---|
| First 30 days | Learn systems, customers and existing processes |
| First 60 days | Begin independently managing core responsibilities |
| First 90 days | Own routine workflows and identify improvements |
| 6 months | Deliver measurable improvements within core area |
| 12 months | Demonstrate sustained performance against role objectives |
These timeframes should only be used when they genuinely reflect the organization’s expectations.
For a Sales Manager, for example:
First 90 days: Understand the existing pipeline, team capabilities and sales process.
Within six months: Establish a consistent forecasting and pipeline-management process.
Within 12 months: Improve sales-team performance against agreed commercial targets.
This is considerably more useful than:
Must be results-oriented and capable of achieving company objectives.
Use Metrics Carefully
Numbers can make expectations substantially clearer when the organization has legitimate targets.
For example:
Vague:
Manage a sales team.
Specific:
Lead and coach a team of eight Account Executives.
Vague:
Manage customer relationships.
Specific:
Manage a portfolio of approximately 30 enterprise customer accounts.
Vague:
Create content regularly.
Specific:
Plan and coordinate approximately eight to ten long-form content pieces each month.
Useful quantitative information might include:
- Team size.
- Account portfolio size.
- Typical project value.
- Number of projects.
- Geographic coverage.
- Budget ownership.
- Revenue responsibility.
- Expected content volume.
- Customer volume.
- Reporting frequency.
However, avoid false precision. If workload fluctuates substantially, use phrases such as “approximately,” “typically,” or “depending on business requirements.”
Do Not Turn Every Responsibility Into a KPI
Not everything needs a numerical target.
Consider a Human Resources Manager responsible for:
- Employee relations.
- Recruitment.
- Policy development.
- Performance management.
- Compliance.
- Manager coaching.
Trying to assign an arbitrary percentage or monthly quota to every responsibility could make the description less accurate.
Metrics work best when they clarify the scale or expected outcome of a role.
| Situation | Numerical Detail Useful? |
|---|---|
| Sales quota | Yes |
| Team size | Yes |
| Customer portfolio | Yes |
| Marketing budget | Often |
| Number of projects | Often |
| Employee relations quality | Usually qualitative |
| Leadership effectiveness | Combination |
| Collaboration | Usually qualitative |
| Strategic thinking | Usually qualitative |
Use numbers where they improve understanding, not merely because numbers appear more precise.
Show How the Position Fits Into the Organization
Responsibilities become easier to understand when candidates know who they will work with and where the position sits within the business.
Indeed recommends explaining who the employee reports to and how the position functions within the organization.
For example:
Report to the Head of Marketing and work closely with the Sales, Product and Customer Success teams.
Or:
Lead a team of six software engineers and collaborate with Product Managers and Product Designers to deliver customer-facing features.
This information helps candidates understand:
- Reporting relationships.
- Team structure.
- Management responsibility.
- Cross-functional collaboration.
- Decision-making authority.
A simple responsibility matrix can make this even clearer.
| Area | Employee Owns | Collaborates With | Reports To |
|---|---|---|---|
| SEO strategy | Yes | Content team | Head of Marketing |
| Paid acquisition | Yes | Creative team | Head of Marketing |
| Sales enablement | Shared | Sales team | Head of Marketing |
| Product launches | Shared | Product team | Head of Marketing |
| Marketing budget | Partial | Finance | Head of Marketing |
The matrix itself does not necessarily need to appear in every published vacancy, but it can be an excellent internal tool for defining the position before writing the description.
Clarify Ownership and Decision-Making Authority
One of the biggest sources of ambiguity in job descriptions is the word “manage.”
What does “manage the marketing strategy” actually mean?
Does the employee:
- Recommend the strategy?
- Approve it?
- Execute it?
- Manage the budget?
- Manage employees?
- Manage external agencies?
- Report results?
Where relevant, clarify the level of ownership.
| Term | Possible Meaning |
|---|---|
| Support | Contribute under another person’s ownership |
| Coordinate | Organize activities across people or teams |
| Execute | Carry out an established plan |
| Own | Hold primary responsibility |
| Lead | Direct work or decision-making |
| Manage | Control resources, processes or people |
| Approve | Hold decision authority |
| Advise | Recommend without final authority |
Clear ownership is particularly important for senior positions.
Instead of:
Help with product strategy.
Write:
Own product strategy for the employer-facing platform and recommend roadmap priorities to the VP of Product.
Candidates now understand both the responsibility and the scope of authority.
Avoid Unrealistic Role Creep
A job description becomes less credible when one position appears to contain several full-time professions.
For example:
Marketing Manager responsible for SEO, paid advertising, graphic design, video production, website development, PR, event management, sales development, customer support and office administration.
Candidates may reasonably interpret this as an understaffed organization attempting to hire several employees for the price of one.
A better approach is to identify the primary professional function and separate:
Core responsibilities
from
Occasional supporting activities
For example:
| Category | Example |
|---|---|
| Core | SEO strategy |
| Core | Content marketing |
| Core | Paid acquisition |
| Core | Marketing analytics |
| Supporting | Coordinate design requests |
| Supporting | Assist with occasional events |
| Not appropriate | Full-stack website development |
| Not appropriate | Customer support ownership |
| Not appropriate | Bookkeeping |
This exercise can reveal when the organization should actually create multiple positions.
Avoid the “Other Duties as Assigned” Trap
Many organizations include:
Perform other duties as assigned.
There may be legitimate operational reasons for including flexibility, but the phrase should not compensate for an incomplete responsibilities section.
A better version might be:
Support additional marketing initiatives that reasonably align with the scope and seniority of the role.
This communicates flexibility while reducing the impression that unlimited unrelated work can be assigned.
Responsibilities Can Support Skills-Based Hiring
Clear responsibilities can also broaden the employer’s approach to assessing candidates.
Rather than starting with:
Bachelor’s degree, MBA preferred, five years of experience required.
Employers can first ask:
What does this employee actually need to be capable of doing?
LinkedIn has reported that U.S. job postings mentioning responsibilities without mentioning requirements received 14% more applications per view than postings mentioning requirements without responsibilities. LinkedIn uses this finding to support a more skills-focused approach to job descriptions.
Separate LinkedIn data found that job posts explicitly listing skills in their requirements were associated with an 11% higher view-to-apply rate compared with posts that did not list skills there.
This does not mean employers should eliminate legitimate qualifications. Instead, responsibilities can become the starting point for determining which skills and qualifications are genuinely necessary.
Build Requirements From Responsibilities
One practical method is to map each major responsibility to the capability required to perform it.
| Responsibility | Required Capability |
|---|---|
| Build financial forecasts | Financial modeling |
| Manage Google Ads campaigns | Paid search expertise |
| Analyze customer behavior | Data analysis |
| Lead software engineers | Engineering leadership |
| Negotiate enterprise contracts | Commercial negotiation |
| Recruit technical candidates | Technical recruitment |
| Create SEO content strategy | SEO and content planning |
| Present to executives | Executive communication |
This creates a logical chain:
Responsibility → Skill → Requirement
rather than:
Traditional requirement → Add it because previous job descriptions had it.
The result can be a more focused and defensible job description.
Remember the SEO and Google Jobs Perspective
Complete responsibility information is useful not only to candidates but also to job-search systems.
Google’s current JobPosting documentation states that the description must provide a complete representation of the job, including responsibilities, qualifications, skills, working hours, education requirements and experience requirements.
Google has also specifically advised publishers to include relevant information within the job description so job seekers have sufficient context to make informed decisions.
Employers publishing vacancies on their own career websites should therefore avoid pages containing little more than a job title and an “Apply” button.
Clear, substantive job content improves the page for candidates while providing search engines with richer information about the vacancy.
Before-and-After Responsibilities Example
Consider a Content Marketing Manager vacancy.
Weak version:
- Write content.
- Manage SEO.
- Handle social media.
- Work with marketing.
- Analyze performance.
- Perform other tasks as required.
The responsibilities are understandable but provide almost no information about scale, ownership or outcomes.
Improved version:
- Develop and manage the company’s organic content strategy across priority product and industry topics.
- Build quarterly editorial plans based on keyword research, customer needs and commercial priorities.
- Coordinate writers, editors and subject-matter experts to produce high-quality long-form content.
- Optimize existing content to improve organic visibility, engagement and conversion performance.
- Monitor organic traffic, rankings, leads and content-assisted conversions using appropriate analytics tools.
- Collaborate with product and sales teams to identify customer questions and high-value content opportunities.
- Report monthly content and SEO performance to the Head of Marketing and recommend priorities for improvement.
The second version helps candidates understand:
- What they own.
- What they produce.
- Who they work with.
- How performance is assessed.
- Who they report to.
- What outcomes matter.
Responsibilities Quality Matrix
Before publishing the job description, review the responsibilities section using a simple quality matrix.
| Criterion | Weak | Good | Strong |
|---|---|---|---|
| Specificity | Generic activities | Main tasks identified | Precise areas of ownership |
| Prioritization | Everything listed | Core tasks emphasized | Responsibilities ranked by importance |
| Outcomes | Tasks only | Some outcomes | Clear connection to business results |
| Action language | Passive/vague | Mostly active | Strong action verbs throughout |
| Scale | Unknown | Some context | Team, budget, market or portfolio clarified |
| Reporting | Missing | Manager identified | Reporting and collaboration explained |
| Success | Undefined | General expectations | Clear performance outcomes |
| Length | Exhaustive | Manageable | Concise and information-rich |
| Realism | Multiple jobs combined | Mostly reasonable | Coherent professional scope |
| Candidate value | Hard to visualize | General picture | Candidate can imagine daily work |
A Practical Formula for Writing Strong Responsibilities
A useful structure is:
Action + Object + Context + Intended Outcome
For example:
Action: Analyze
Object: customer retention data
Context: across subscription cohorts
Outcome: identify opportunities to reduce churn
This becomes:
Analyze customer retention data across subscription cohorts to identify opportunities to reduce churn.
Another example:
Action: Manage
Object: paid search campaigns
Context: across Google Ads
Outcome: generate qualified B2B leads efficiently
This becomes:
Manage Google Ads campaigns to generate qualified B2B leads while maintaining agreed acquisition-cost targets.
Not every responsibility needs all four elements, but this framework helps eliminate vague statements.
Final Check: Could a Candidate Imagine Doing This Job?
Before publishing the vacancy, read only the responsibilities section and ask:
Could a qualified candidate reasonably describe what an average week in this position might look like?
If the answer is no, the responsibilities probably need more clarity.
A strong responsibilities section should explain what the employee owns, what they actually do, who they work with, what decisions they can make, and what successful performance looks like. It should contain enough detail to establish realistic expectations without becoming an exhaustive inventory of every possible task.
That balance matters because responsibilities are not merely administrative details. They are among the most important pieces of information candidates use to decide whether an opportunity deserves their application.
4. Separate Essential Requirements From Preferred Qualifications
One of the easiest ways to make a job description unnecessarily restrictive is to treat every desirable skill, credential, and experience level as mandatory. A strong job description should clearly distinguish between essential requirements that a candidate genuinely needs to perform the role and preferred qualifications that would be beneficial but are not necessary for consideration.
This distinction matters because every mandatory requirement acts as a filter on the available talent pool. LinkedIn recommends that employers reconsider lengthy requirements lists and instead focus on the skills candidates need to perform the actual responsibilities of the job. Its U.S. data found that job posts mentioning responsibilities without mentioning requirements received 14% more applications per view than posts mentioning requirements without responsibilities.
The objective is not to eliminate standards. It is to ensure that every mandatory requirement has a legitimate reason for being mandatory.
Understand the Difference Between Required and Preferred Qualifications
The distinction should be straightforward:
Essential requirements are capabilities or credentials without which someone could not reasonably perform the position.
Preferred qualifications can make someone more competitive or help them become productive faster, but their absence should not automatically disqualify an otherwise capable candidate.
| Category | Meaning | Example |
|---|---|---|
| Essential | Necessary to perform the job | Valid nursing license for a registered nurse |
| Essential | Core technical capability | SQL proficiency for a SQL-heavy data role |
| Essential | Legal/operational necessity | Required professional certification |
| Essential | Fundamental role capability | Ability to communicate with customers |
| Preferred | Helpful additional capability | Experience with the company’s CRM |
| Preferred | Relevant industry exposure | Previous SaaS experience |
| Preferred | Additional tool knowledge | Familiarity with HubSpot |
| Preferred | Useful credential | Relevant professional certification |
| Preferred | Additional language | Second language useful for some customers |
A useful test is:
If an otherwise excellent candidate did not have this qualification, would we definitely reject them?
If the answer is no, the qualification probably belongs under preferred, not required.
Start With the Work, Then Determine the Requirements
Requirements should ideally be derived from the responsibilities defined in the previous section.
Instead of beginning with:
Bachelor’s degree, five years of experience, MBA preferred, Salesforce certification required.
Start with what the employee needs to accomplish:
Build and manage enterprise sales pipeline, conduct product demonstrations, negotiate commercial agreements, and close new customers.
Then identify the capabilities necessary to perform those activities.
| Responsibility | Capability Needed | Requirement Type |
|---|---|---|
| Prospect enterprise customers | B2B prospecting skills | Essential |
| Run product demonstrations | Presentation skills | Essential |
| Negotiate contracts | Commercial negotiation | Essential |
| Maintain pipeline | CRM proficiency | Essential |
| Use Salesforce internally | Salesforce experience | Preferred if trainable |
| Sell HR technology | HR technology knowledge | Preferred if learnable |
| Manage international customers | Cross-cultural communication | Preferred/essential depending on role |
This creates a much stronger chain:
Responsibilities → Skills → Requirements
rather than:
Old job description → Copy old requirements → Add more requirements.
Keep the Must-Have List Genuinely Essential
Imagine a company hiring an SEO Manager.
A poorly designed requirements section might say:
Requirements
- Bachelor’s degree in Marketing.
- Minimum seven years of experience.
- Agency experience.
- SaaS experience.
- Google Analytics certification.
- Google Ads certification.
- Advanced Excel skills.
- WordPress experience.
- Ahrefs experience.
- Semrush experience.
- Screaming Frog experience.
- HTML knowledge.
- CSS knowledge.
- Basic JavaScript knowledge.
- Excellent presentation skills.
- Excellent writing skills.
The company has effectively created a very narrow candidate profile.
A better version could be:
Essential Requirements
- Demonstrated experience developing and executing SEO strategies.
- Strong technical and on-page SEO knowledge.
- Ability to conduct keyword and competitor research.
- Experience using analytics and search-performance data.
- Ability to translate SEO insights into actionable recommendations.
Preferred Qualifications
- Experience with SaaS or B2B SEO.
- Familiarity with Ahrefs, Semrush or comparable SEO platforms.
- WordPress experience.
- Basic understanding of HTML and web technologies.
- Experience managing writers or external agencies.
The employer is still maintaining a meaningful quality threshold, but it is evaluating candidates primarily around the capabilities needed to perform the work.
Avoid Arbitrary Years-of-Experience Requirements
Years of experience can be useful when they reflect the genuine complexity and seniority of a position. However, they are an imperfect proxy for capability.
Consider two candidates:
| Candidate | Experience | Relevant Capability |
|---|---|---|
| Candidate A | 7 years | Limited ownership; repetitive execution |
| Candidate B | 4 years | Led strategy, team and complex projects |
If the advertisement states:
Minimum 5 years of experience required.
Candidate B could theoretically be rejected despite potentially being better prepared for the position.
Instead of focusing exclusively on duration, employers can define the level of capability expected.
Traditional requirement:
Minimum five years of digital marketing experience.
Capability-focused alternative:
Demonstrated experience independently planning, executing and optimizing multi-channel digital acquisition campaigns.
Years of experience can still be included when useful, but employers should ask whether the exact threshold is necessary or merely conventional.
Be Careful With Degree Requirements
Educational qualifications deserve the same scrutiny.
Harvard Business School, Accenture and Grads of Life analyzed more than 26 million U.S. job postings and surveyed 600 business and HR leaders while studying “degree inflation” in middle-skill jobs. Their research found substantial mismatches between the credentials employers requested and those held by people successfully performing certain occupations.
One particularly striking example involved production supervisors. In 2015, 67% of job postings for production supervisors requested a college degree, while only 16% of people already employed in those positions held one.
The research also found that two-thirds of surveyed employers agreed that requiring a bachelor’s degree for a middle-skill position made that job harder to fill. Employers generally viewed experienced workers without degrees as nearly or equally productive across multiple performance measures.
The researchers estimated that more than 6 million U.S. middle-skill jobs were at risk of degree inflation.
This does not mean degrees are irrelevant. Some positions genuinely require extensive formal education.
The question is whether the specific job requires one.
Use a Degree-Relevance Test
Before making a degree mandatory, consider:
| Question | If Yes | If No |
|---|---|---|
| Is the degree legally required? | Essential | Continue assessment |
| Is it necessary for professional licensing? | Essential | Continue assessment |
| Does the job require specialist academic knowledge? | Potentially essential | Continue assessment |
| Could equivalent experience provide the same capability? | Consider alternatives | Degree may be justified |
| Are successful current employees doing the job without it? | Reconsider requirement | Requirement may be justified |
| Was the degree simply copied from an old JD? | Reassess it | Evaluate normally |
A more inclusive formulation might therefore be:
Instead of:
Bachelor’s degree in Marketing required.
Consider:
Bachelor’s degree in Marketing, Business or a related discipline, or equivalent relevant professional experience.
Or, where the degree contributes little to job performance, remove the requirement entirely.
Understand the Cost of Unnecessary Degree Filters
The potential effect on the talent pool can be substantial.
A later Harvard Business School and Burning Glass Institute study on the emerging “degree reset” noted that adding a bachelor’s-degree requirement immediately excludes the 64% of working-age U.S. adults who do not hold one from consideration for that vacancy.
This is why employers should avoid using education merely as a convenient proxy for qualities such as:
- Communication.
- Reliability.
- Critical thinking.
- Professionalism.
- Problem solving.
- Digital literacy.
If those capabilities matter, assess those capabilities directly wherever possible.
Distinguish Between Trainable and Non-Trainable Requirements
Another useful method is to ask whether a missing capability could reasonably be learned after hiring.
Suppose a company uses HubSpot.
A candidate has five years of relevant marketing automation experience but has worked primarily with Salesforce and Marketo.
Should lack of HubSpot experience automatically disqualify them?
Probably not, if the underlying capability transfers easily.
| Requirement | Trainability | Likely Classification |
|---|---|---|
| Specific CRM platform | High | Preferred |
| Company-specific software | Very high | Preferred |
| Industry terminology | High | Preferred |
| Basic internal process | Very high | Not necessary in JD |
| Fundamental coding ability | Lower for immediate developer role | Essential |
| Professional medical license | Cannot substitute through onboarding | Essential |
| Commercial negotiation ability | Moderate/experience-dependent | Often essential |
| Specific analytics tool | Often high | Frequently preferred |
| Leadership capability | Longer development horizon | Essential for leadership role |
This approach helps employers distinguish skills required on day one from skills that can reasonably be developed during onboarding.
Avoid Over-Specifying Software Tools
Job descriptions frequently require experience with every tool currently used by the company.
For example:
Must have experience with HubSpot, Salesforce, Slack, Notion, Asana, Zoom, Google Workspace and Looker Studio.
But how many of those tools genuinely determine whether someone can perform the job?
A better approach could be:
Experience using CRM, project-management and analytics platforms; familiarity with HubSpot and Looker Studio is advantageous.
This shifts the emphasis from brand-specific software familiarity to transferable capability.
The same principle applies to technical tools.
Instead of:
Must have exactly three years of Ahrefs experience.
Consider:
Strong experience with professional SEO research and analysis platforms such as Ahrefs, Semrush or equivalent tools.
Unless a specific platform genuinely requires deep specialist expertise, tool familiarity is often easier to teach than the underlying professional discipline.
Clearly Label Must-Haves and Nice-to-Haves
Do not force candidates to guess which qualifications are negotiable.
A simple structure works well:
Essential Requirements
- Proven experience managing B2B sales opportunities.
- Strong prospecting and negotiation skills.
- Ability to independently manage a sales pipeline.
- Strong written and verbal communication skills.
- Experience using CRM systems.
Preferred Qualifications
- Experience selling SaaS products.
- Familiarity with Salesforce.
- Experience selling into Southeast Asian markets.
- Knowledge of HR technology.
- Additional regional language skills.
This structure tells candidates exactly how to interpret the criteria.
Alternative headings include:
| Essential Section | Preferred Section |
|---|---|
| Must-Have Qualifications | Nice-to-Have Qualifications |
| Required Skills | Preferred Skills |
| Essential Criteria | Desirable Criteria |
| What You Need | What Would Be Helpful |
| Minimum Qualifications | Preferred Qualifications |
Consistency and clarity matter more than the exact terminology.
Do Not Turn “Preferred” Into a Hidden Requirement
Employers should also ensure that the recruitment process follows the distinction made in the advertisement.
If the job description says:
Salesforce experience preferred.
but recruiters automatically reject everyone without Salesforce experience, then Salesforce was never truly preferred. It was an undisclosed essential requirement.
A useful internal matrix can prevent this problem.
| Qualification | Essential? | Preferred? | Auto-Reject If Missing? |
|---|---|---|---|
| B2B sales experience | Yes | No | Yes |
| Negotiation skills | Yes | No | Yes |
| CRM experience | Yes | No | Yes |
| Salesforce | No | Yes | No |
| SaaS experience | No | Yes | No |
| HR technology experience | No | Yes | No |
| Bachelor’s degree | No | Yes/Not needed | No |
Recruiters, hiring managers and applicant-tracking-system rules should all follow the same logic.
Avoid “Unicorn Candidate” Job Descriptions
One common recruitment mistake is continually adding desirable characteristics until the employer has described a candidate who barely exists.
For example:
We need someone with enterprise sales experience, SaaS experience, recruitment industry experience, five years of management experience, Salesforce expertise, an MBA, three regional languages, technical product knowledge and an existing customer network.
Each individual requirement may sound beneficial.
Collectively, they may reduce the candidate pool dramatically.
A useful classification framework is:
| Classification | Question |
|---|---|
| Must Have | Can someone perform the role without this? |
| Strong Preference | Would this materially accelerate performance? |
| Nice to Have | Would this add useful secondary value? |
| Trainable | Can we teach this relatively quickly? |
| Irrelevant | Does this actually predict success in the job? |
Anything in the final category should simply be removed.
Focus on Skills-Based Hiring Where Appropriate
Skills-based hiring shifts attention from proxies such as pedigree and arbitrary credentials toward whether someone possesses the capabilities necessary to perform the work.
LinkedIn explicitly recommends that employers consider relaxing unnecessary requirements and focus instead on the performance expected from the employee and the skills they will use in their day-to-day work.
A skills-focused requirement section might therefore look like this:
| Traditional Requirement | Skills-Focused Alternative |
|---|---|
| Marketing degree required | Ability to develop and execute marketing strategy |
| 5+ years required | Demonstrated experience owning comparable campaigns |
| Salesforce certification | Ability to manage complex CRM pipelines |
| Agency experience required | Ability to manage multiple concurrent client projects |
| MBA preferred | Strong commercial and strategic decision-making |
| Journalism degree | Strong research, interviewing and writing skills |
Credentials can still be valuable evidence of competence, but they do not always need to be the only acceptable evidence.
Be Careful With the “Women Apply at 100%, Men at 60%” Statistic
One frequently repeated argument for shortening requirements lists claims that women apply only when they meet 100% of the qualifications while men apply when they meet 60%.
LinkedIn previously cited this claim and separately reported behavioral data showing women applied to 20% fewer jobs than men on its platform.
However, employers should not present the 100%-versus-60% figure as established scientific fact.
A 2024 paper published in the European Journal of Social Psychology directly tested the popular claim across four studies. Researchers found no gender difference in application intentions at either 60% or 100% qualification fit in the first study, and the later studies did not establish a robust application-intention difference of the magnitude suggested by the popular claim. Women did report a higher desire to feel prepared, but that did not reliably translate into the supposed application behavior.
The practical lesson remains sensible without relying on a questionable statistic: unnecessary requirements create unnecessary barriers for candidates.
Write Requirements That Candidates Can Evaluate
Avoid subjective phrases such as:
Must be exceptional.
Must be a superstar.
Must have a winning personality.
Must be extremely intelligent.
These statements provide no objective basis for self-assessment.
Instead, describe observable capabilities:
| Vague | Better |
|---|---|
| Excellent marketer | Experience planning and optimizing multi-channel campaigns |
| Strong leader | Experience coaching and managing professional teams |
| Great communicator | Ability to present complex information to non-technical stakeholders |
| Data-driven | Ability to analyze performance data and translate findings into actions |
| Sales superstar | Demonstrated ability to develop and close B2B opportunities |
| Technical genius | Strong proficiency in the required programming languages and architecture |
Candidates can evaluate themselves against observable capabilities much more effectively.
Build a Requirement Validation Matrix
Before publishing the job description, hiring teams can review each requirement systematically.
| Requirement | Needed Day One? | Trainable? | Predicts Performance? | Essential? |
|---|---|---|---|---|
| Core professional skill | Yes | Low | High | Yes |
| Relevant communication ability | Yes | Moderate | High | Yes |
| Specific internal software | No | High | Low | No |
| Industry experience | Maybe | Moderate | Moderate | Usually preferred |
| Bachelor’s degree | Depends | N/A | Depends on role | Review |
| Exact years of experience | No | N/A | Imperfect proxy | Review |
| Professional license | Yes | No | Legally necessary | Yes |
| Company-specific knowledge | No | High | Low initially | No |
| Additional language | Depends | Moderate | Role-dependent | Review |
If hiring managers struggle to explain why a requirement is essential, that is a strong signal that it should be moved to preferred qualifications or removed.
Before-and-After Requirements Example
Consider a Customer Success Manager vacancy.
Before:
Requirements
- Bachelor’s degree required.
- Minimum five years of SaaS experience.
- Minimum three years of Customer Success experience.
- Salesforce experience required.
- HubSpot experience required.
- Zendesk experience required.
- Previous HR technology experience.
- Project management certification preferred.
- Excellent communication skills.
- Advanced Microsoft Excel skills.
This description could eliminate capable candidates because of tools, industry background or credentials that may be learnable.
After:
Essential Requirements
- Experience managing ongoing B2B customer relationships.
- Ability to understand customer objectives and develop success plans.
- Strong communication, presentation and stakeholder-management skills.
- Experience identifying customer risks and coordinating solutions across internal teams.
- Ability to interpret customer and product-usage data.
- Experience working with CRM or customer-success platforms.
Preferred Qualifications
- SaaS Customer Success experience.
- Experience with HR technology.
- Familiarity with Salesforce, HubSpot or comparable platforms.
- Experience managing enterprise customers.
- Project-management experience.
The revised version still establishes a meaningful hiring standard while allowing candidates with transferable experience to compete.
Essential vs Preferred Qualification Decision Matrix
A final decision matrix can help employers classify borderline criteria.
| Question | Essential | Preferred | Remove |
|---|---|---|---|
| Legally required? | Yes | ||
| Required for professional licensing? | Yes | ||
| Needed to perform core duties immediately? | Usually | ||
| Difficult to learn during reasonable onboarding? | Possibly | Possibly | |
| Can be learned quickly? | Yes | ||
| Merely familiar company software? | Usually | ||
| Useful industry background? | Usually | ||
| Copied from previous JD without justification? | Review/remove | ||
| Arbitrary years-of-experience threshold? | Review | Review | |
| Does not relate to actual responsibilities? | Yes | ||
| Makes a good candidate stronger but isn’t necessary? | Yes |
Apply the “Why?” Test to Every Requirement
Before publishing, take every requirement and ask:
Why must the successful candidate have this?
If the answer is clear and connected directly to job performance, keep it.
If the answer is:
“Because we’ve always required it.”
“Because the previous person had it.”
“Because it would be nice.”
“Because most companies ask for it.”
then reconsider its classification.
A clear and compelling job description should set a high but relevant bar, not create an obstacle course of credentials. By separating genuine must-haves from preferred qualifications, employers can communicate expectations more accurately, support skills-based hiring, and avoid unnecessarily excluding potentially strong candidates before the recruitment process has even begun.
5. Make the Job Description Transparent, Inclusive, and Candidate-Focused
The strongest job descriptions do more than explain what an employer wants. They also give candidates enough information to decide whether the opportunity is right for them.
That means shifting from an employer-only perspective — “Here is everything we demand from applicants” — toward a two-way value proposition:
What does the employer need, what will the candidate receive, and what should both sides realistically expect from the employment relationship?
Transparency is increasingly important because candidates want practical information early. Indeed’s updated 2026 employer guidance recommends leading with information such as location, work pattern, core responsibilities and pay so candidates can assess opportunities quickly. Indeed also recommends realistic salary ranges, details about compensation structure and information about career progression where possible.
Google takes a similar candidate-experience approach. Its JobPosting guidelines require the job description to be a complete representation of the position, including responsibilities, qualifications, skills, working hours, education requirements and experience requirements.
The final principle of writing a compelling job description is therefore simple:
Reduce uncertainty for the candidate.
Include a Realistic Salary or Compensation Range
Compensation is one of the most consequential pieces of information candidates use when evaluating opportunities.
Instead of:
Competitive salary based on experience.
Consider:
Base salary: $70,000–$85,000 per year, depending on relevant experience.
Or for a sales position:
Base salary: $60,000–$70,000 per year, plus uncapped commission. Target annual earnings at 100% quota: approximately $100,000.
The second approach gives candidates significantly more information.
Indeed recommends including a realistic pay range where possible and explaining how compensation is structured, including bonuses, commissions or other incentives. It also notes that pay-transparency laws apply to certain employers and positions in some jurisdictions.
Make the Salary Range Meaningful
A technically disclosed but unrealistic salary range provides little value.
Consider:
Poor transparency:
Salary: $40,000–$150,000.
Better transparency:
Base salary: $65,000–$80,000 annually, depending on experience.
Better for commission-based employment:
Base salary: $50,000–$60,000 plus commission, with target total annual compensation of $85,000–$100,000 at 100% quota attainment.
Employers should clarify what the figure represents.
| Compensation Element | Information to Consider Including |
|---|---|
| Base salary | Minimum and maximum |
| Currency | USD, GBP, EUR, SGD, VND, etc. |
| Payment period | Hourly, monthly or annually |
| Commission | Structure or target earnings |
| Bonus | Eligibility and broad structure |
| Equity | Eligibility where relevant |
| Overtime | Eligibility where relevant |
| Allowances | Transport, meals, housing, etc. |
| Review cycle | When appropriate |
Google’s JobPosting structured-data specification supports actual employer-provided base salaries as either a single amount or a minimum-to-maximum range, with units including hourly, daily, weekly, monthly and yearly compensation.
Keep Salary Information Consistent Everywhere
Transparency also means consistency.
If the job page says:
$70,000–$85,000
but structured data submitted to search engines says:
$80,000–$100,000
the information is contradictory.
Google explicitly requires information contained in JobPosting structured data to match what candidates can see on the actual job page. Its documentation identifies salary appearing in markup but not on the visible page as an example of a content-guideline violation.
Google has emphasized this principle for years, specifically instructing publishers that salary and location information in structured data should match the visible job description.
For employers publishing vacancies on their own websites, the principle should therefore be:
Job page = structured data = job board information = actual employment opportunity.
Clearly State Whether the Job Is Remote, Hybrid, or Onsite
Candidates should not have to reach the interview stage to discover where they are expected to work.
Avoid:
Flexible working environment.
What does “flexible” mean?
Instead, write:
Hybrid: Employees work from our London office three days per week and may work remotely for the remaining two days.
Or:
Fully remote within the United States. Candidates must be legally eligible to work and reside in the U.S.
Or:
Onsite position based in Singapore. This role requires five days per week in our Raffles Place office.
The distinction is especially important for remote vacancies because “remote” does not necessarily mean work from anywhere.
Explain Geographic Restrictions for Remote Jobs
A company may advertise a fully remote position while limiting candidates to:
- One country.
- Certain states or provinces.
- A specific timezone.
- Regions where the company has legal employment entities.
- Locations where employees have appropriate work authorization.
Make these restrictions clear.
For example:
This is a fully remote position open to candidates residing in Vietnam, Thailand, Malaysia, Singapore, Indonesia or the Philippines. Candidates should be available for regular collaboration during GMT+7 to GMT+8 business hours.
Google’s current JobPosting specification supports this distinction technically. Fully remote jobs can use jobLocationType to identify telecommuting positions and applicantLocationRequirements to specify where remote candidates are permitted to reside. Google requires at least one eligible country for fully remote positions represented this way.
This reinforces a useful SEO and candidate-experience principle:
“Remote” should describe the working arrangement; geographic eligibility should describe where the employee can actually be located.
Include Working Hours and Schedule Expectations
Working hours can dramatically change the attractiveness and practicality of an opportunity.
Compare:
Vague:
Flexible hours may be required.
Transparent:
Standard working hours are Monday to Friday, 9:00 a.m.–6:00 p.m. Some evening calls with U.S.-based customers may be required approximately twice per month.
Candidates now understand the trade-off before applying.
Relevant information may include:
| Employment Situation | Information Candidates Need |
|---|---|
| Standard office role | Typical working hours |
| Shift work | Shift pattern |
| Retail | Weekend requirements |
| Hospitality | Evening/weekend expectations |
| Global remote team | Collaboration timezone |
| Sales | Travel expectations |
| Healthcare | On-call requirements |
| Seasonal employment | Peak-period expectations |
| Flexible role | Core collaboration hours |
Google’s JobPosting guidelines explicitly identify working hours as information that should be represented within a complete job description.
Be Clear About Employment Type
Candidates should know whether they are applying for:
- Full-time employment.
- Part-time employment.
- Permanent employment.
- Fixed-term employment.
- Contractor work.
- Temporary employment.
- Internship.
- Freelance work.
- Per-diem work.
Google’s JobPosting system formally supports employment classifications including FULL_TIME, PART_TIME, CONTRACTOR, TEMPORARY, INTERN, VOLUNTEER and PER_DIEM, demonstrating how fundamental this information is to job discovery.
Do not advertise something simply as a “full-time opportunity” if the person will actually be engaged as an independent contractor.
Explain Benefits With Specificity
“Excellent benefits” tells candidates very little.
Instead of:
We offer a competitive benefits package.
Consider:
Benefits include private medical insurance, 20 days of annual leave plus public holidays, a $1,000 annual professional-development budget, parental leave and a monthly home-office allowance.
Indeed recommends highlighting meaningful benefits and gives examples including:
- Paid time off.
- Flexible hours.
- Medical, dental and vision coverage.
- Retirement plans.
- Remote-work stipends.
- Tuition reimbursement.
- Paid parental leave.
Specific benefits give candidates something concrete to compare.
Benefits Transparency Matrix
| Vague Description | More Transparent Alternative |
|---|---|
| Great healthcare | Private medical, dental and vision coverage |
| Generous leave | 25 days of annual leave plus public holidays |
| Learning opportunities | $1,500 annual learning budget |
| Flexible working | Hybrid, two office days per week |
| Remote-friendly | Fully remote within approved countries |
| Retirement benefits | 5% employer retirement contribution |
| Great parental support | 16 weeks paid parental leave |
| Performance rewards | Annual bonus of up to 15% |
| Career development | Formal promotion reviews twice annually |
| Wellness benefits | $50 monthly wellness allowance |
The more meaningful the benefit is, the more useful it is to describe it precisely.
Explain Career Growth Without Making Empty Promises
Candidates often care about what happens after they get the job.
Avoid:
Excellent career progression opportunities.
Instead:
Successful Senior Account Executives may progress into Enterprise Account Executive or Sales Team Lead positions as the commercial team expands.
Or:
Engineers receive a formal performance and development review every six months, with separate individual-contributor and engineering-management career tracks.
Indeed’s 2026 employer guidance specifically recommends highlighting potential progression opportunities, such as opportunities to build skills, take on greater responsibility or move into related roles.
Again, specificity makes the claim credible.
Use Inclusive and Candidate-Friendly Language
Inclusive job descriptions avoid wording that could unnecessarily signal that certain groups of qualified candidates are less welcome.
Indeed recommends using inclusive language and revising terminology that may be exclusionary to people considering the opportunity.
Consider obvious examples:
| Avoid | Consider |
|---|---|
| Salesman | Sales Representative |
| Chairman | Chairperson or Chair |
| Waitress | Server |
| Cameraman | Camera Operator |
| Repairman | Repair Technician |
But inclusivity extends beyond gendered titles.
Employers should review whether language unnecessarily implies assumptions about:
- Age.
- Gender.
- Disability.
- Family status.
- Physical ability.
- Cultural background.
- Educational pedigree.
- Career path.
For example:
Young and energetic team seeking digital natives.
could become:
Collaborative digital team seeking a marketer with strong knowledge of current digital channels.
The second version focuses on the capability relevant to the job.
Distinguish Genuine Physical Requirements From Assumptions
Some jobs legitimately have physical requirements.
A warehouse position, for example, might require an employee to lift packages regularly.
In that situation, communicate the actual requirement:
Regularly move packages weighing up to 20 kg using appropriate handling procedures and equipment.
Avoid vague formulations such as:
Must be physically fit.
The first describes an observable job requirement. The second asks candidates to interpret an undefined personal characteristic.
The same principle applies throughout the job description:
Describe the capability required by the work rather than assumptions about the person who should perform it.
Write From the Candidate’s Perspective
After drafting the description, employers should switch perspectives.
Instead of asking:
Did we explain everything we want?
ask:
Does the candidate have everything they need to evaluate this opportunity?
A candidate-focused job description should answer questions such as:
| Candidate Question | Job Description Should Explain |
|---|---|
| What will I do? | Responsibilities |
| What am I accountable for? | Expectations and outcomes |
| Am I qualified? | Essential requirements |
| Could I still apply without every extra skill? | Preferred qualifications |
| What will I earn? | Compensation |
| Where will I work? | Location |
| Can I work remotely? | Work arrangement |
| When will I work? | Schedule |
| Who will I report to? | Reporting structure |
| Who will I work with? | Team structure |
| What benefits are offered? | Benefits |
| Can I develop here? | Growth opportunities |
| What happens after I apply? | Hiring process |
If several of these questions remain unanswered, the job description may still be too employer-centric.
Explain the Hiring Process
Recruitment itself can be a source of uncertainty.
A candidate may wonder whether the process involves:
- One interview or five.
- A technical assessment.
- A take-home assignment.
- A presentation.
- Reference checks.
- Background screening.
- A final executive interview.
Where practical, give candidates an overview.
For example:
Our hiring process consists of a 30-minute recruiter conversation, a 60-minute interview with the hiring manager, a practical case discussion and a final team interview. We aim to complete the process within approximately two to three weeks.
This information allows candidates to prepare and evaluate the commitment required.
Keep the Application Process Simple
Candidate focus should continue after the job description.
Google’s JobPosting specification includes a directApply property for positions that offer a short and simple application experience without unnecessary intermediate steps.
Google’s content policies also require legitimate job postings to provide candidates with a way to apply. Pages that merely advertise opportunities without providing an application path are not permitted in its jobs experience.
A candidate should ideally move logically through:
Discover job → Understand job → Evaluate fit → Apply
rather than:
Discover job → Create account → Verify email → Search for job again → Re-enter resume → Complete 12 pages → Apply
Every unnecessary step introduces friction.
Be Transparent About the Employer
Candidates should know who they are considering working for whenever confidentiality is not genuinely necessary.
Useful company information includes:
- What the organization does.
- Primary customers or market.
- Team size where relevant.
- Stage of growth.
- Role of the department.
- Mission or purpose.
- Workplace culture.
- Reporting structure.
However, avoid turning the job description into a corporate brochure.
Too employer-focused:
Founded in 1998, we have spent more than 25 years building our award-winning organization…
More candidate-focused:
Join our 12-person engineering team to build payment infrastructure used by more than 5,000 small businesses across Southeast Asia.
The second statement still communicates company information, but connects it directly to the candidate’s potential work.
Never Misrepresent the Opportunity
Transparency is not simply good recruitment practice. Search platforms also expect accurate job information.
Google’s job-posting policies prohibit misleading representation, fake or non-existent vacancies, postings designed primarily to collect applicant information, and other deceptive practices.
Employers should therefore avoid:
- Advertising expired jobs.
- Publishing evergreen vacancies that do not actually exist.
- Misrepresenting salary.
- Calling an onsite role remote.
- Advertising a permanent job that is actually contract work.
- Inflating job titles.
- Hiding significant working conditions.
- Misrepresenting the hiring company.
Google has specifically highlighted expired jobs as a poor candidate experience because job seekers may invest time evaluating a vacancy only to discover that applications are no longer accepted.
Transparency Can Also Support Job Posting SEO
Candidate transparency and search optimization are increasingly aligned.
Google says JobPosting structured data can make vacancies eligible for its specialized job-search experience, where candidates can filter opportunities using criteria such as job title and location.
Google also states that job seekers prefer postings with explicitly stated salaries over those without them when discussing structured-data completeness.
For employers publishing vacancies on their own career sites, useful information can therefore serve two audiences simultaneously:
| Information | Candidate Benefit | Search/Structured Data Benefit |
|---|---|---|
| Clear title | Understand role | Job title matching |
| Location | Assess commute | Geographic relevance |
| Remote status | Assess flexibility | Remote-job classification |
| Eligible locations | Know if they can apply | Geographic targeting |
| Salary | Assess financial fit | Salary information |
| Employment type | Understand arrangement | Employment classification |
| Full description | Assess opportunity | Content completeness |
| Expiration date | Know vacancy is current | Job lifecycle management |
Google also requires a complete description containing relevant information such as qualifications, skills and benefits so job seekers can make informed decisions.
SEO optimization should therefore not mean inserting more keywords. For job descriptions, it often means providing better structured, accurate and complete information.
Before-and-After Transparency Example
Consider this vacancy:
Before:
We are seeking a motivated Account Executive to join our dynamic team. Competitive compensation and excellent benefits are available. The successful candidate should be flexible and willing to work in a fast-paced environment. Remote working may be available for suitable candidates.
Candidates are left with several unanswered questions.
| Question | Answer Available? |
|---|---|
| Salary | No |
| Commission | No |
| Location | No |
| Remote policy | Unclear |
| Working hours | No |
| Benefits | No |
| Employment type | No |
| Reporting structure | No |
| Hiring process | No |
After:
We are hiring a full-time B2B Account Executive to develop new enterprise customers across Southeast Asia. The role offers a base salary of $50,000–$60,000 plus uncapped commission, with target annual earnings of approximately $90,000 at 100% quota attainment.
This is a hybrid position based in Singapore, with two required office days each week. Standard working hours are Monday to Friday, with occasional customer calls outside normal hours.
Benefits include private medical insurance, 22 days of annual leave, an annual professional-development budget and flexible working hours. You will report to the Regional Sales Director and work closely with Sales Development and Customer Success.
The hiring process includes a recruiter conversation, hiring-manager interview, sales case discussion and final leadership interview.
The second description does not merely sound better.
It gives candidates the information required to make a rational decision.
Candidate-Focused Job Description Matrix
Before publishing, assess the vacancy across the following dimensions:
| Dimension | Weak | Good | Strong |
|---|---|---|---|
| Compensation | “Competitive” | Salary provided | Range + variable pay explained |
| Benefits | “Great benefits” | Benefits listed | Specific entitlement explained |
| Location | Missing | City stated | Exact work arrangement explained |
| Remote policy | “Flexible” | Remote/hybrid stated | Eligibility and schedule clarified |
| Working hours | Missing | General schedule | Hours + exceptions explained |
| Employment type | Ambiguous | Type stated | Type and duration clarified |
| Requirements | Long undifferentiated list | Requirements defined | Essential/preferred separated |
| Inclusivity | Potentially exclusionary | Mostly neutral | Capability-focused throughout |
| Career growth | Generic promise | Opportunities mentioned | Concrete progression explained |
| Hiring process | Unknown | Stages mentioned | Stages and approximate timeline |
| Employer information | Corporate marketing | Relevant overview | Connected to candidate opportunity |
| Application | High friction | Standard application | Simple, clear process |
Use the Candidate Transparency Test
Before publishing the final job description, imagine receiving the advertisement from an employer you know nothing about.
Could you answer:
What will I do?
What do I need to qualify?
What will I earn?
What benefits will I receive?
Where will I work?
Can I work remotely?
What hours will I work?
Who will I report to?
What opportunities could this role create for me?
What happens after I apply?
If candidates need to attend an interview merely to discover basic information about the opportunity, the job description is probably not transparent enough.
A clear and compelling job description should ultimately function as a decision-making tool for both sides of the recruitment process. Employers use it to attract people capable of performing the role, while candidates use it to decide whether the responsibilities, expectations, compensation, working conditions and career opportunity justify applying.
When employers combine accurate information, inclusive language, realistic requirements and candidate-focused transparency, they can create job descriptions that are not merely more attractive. They are also more useful, credible, search-friendly and capable of helping the right candidates self-select into the recruitment process.
Conclusion
Writing a clear and compelling job description is about much more than listing responsibilities and qualifications. A strong job description helps candidates understand the opportunity, evaluate whether they are a good fit, and make an informed decision about applying. For employers, it can create clearer expectations, attract more relevant applicants, strengthen employer branding, and improve the overall efficiency of the hiring process.
The five tips covered in this guide provide a practical framework for creating better job descriptions. Start with a clear and search-friendly job title that reflects terminology candidates actually use. Follow it with a concise and engaging job summary that quickly communicates the purpose, impact, and value of the role. Then clearly define responsibilities and expectations so candidates understand what they will do and what successful performance looks like.
Employers should also separate essential requirements from preferred qualifications. Not every desirable skill, credential, software platform, degree, or previous industry experience needs to become a mandatory requirement. Focusing on the capabilities genuinely required to perform the job can create a more realistic candidate profile and support a more skills-focused hiring process.
Finally, make every job description transparent, inclusive, and candidate-focused. Clearly communicate important information such as compensation, benefits, location, remote or hybrid arrangements, employment type, working hours, career development opportunities, and the hiring process whenever possible. Candidates should not need to reach the final interview before discovering fundamental details about the opportunity.
Before publishing any vacancy, ask a simple question: Could a qualified candidate read this job description and clearly understand what the job is, what they will be expected to accomplish, what qualifications genuinely matter, and what they will receive in return?
If the answer is yes, the job description is doing its job.
The best job descriptions are not necessarily the longest or the most creative. They are specific, accurate, concise, searchable, transparent, and easy to understand. They replace vague corporate language with meaningful information, unrealistic wish lists with relevant requirements, and promotional claims with concrete details about the opportunity.
Employers can also use modern AI job description generators to accelerate this process. These tools can help structure job descriptions, suggest responsibilities and skills, improve readability, and identify information that may be missing. However, every AI-generated job description should still be reviewed by a recruiter or hiring manager to ensure that the responsibilities, qualifications, salary information, benefits, and employment conditions accurately represent the real position.
Ultimately, a job description is often one of the first meaningful interactions between an employer and a potential employee. Investing the time to make it clear and compelling can help attract candidates who understand the opportunity, meet the right requirements, and are genuinely interested in joining the organization.
A better hiring process can therefore begin with something surprisingly simple: a better job description.
If you find this article useful, why not share it with your hiring manager and C-level suite friends and also leave a nice comment below?
We, at the 9cv9 Research Team, strive to bring the latest and most meaningful data, guides, and statistics to your doorstep.
To get access to top-quality guides, click over to 9cv9 Blog.
To hire top talents using our modern AI-powered recruitment agency, find out more at 9cv9 Modern AI-Powered Recruitment Agency.
People Also Ask
How do you write a clear and compelling job description?
Use a searchable job title, concise summary, specific responsibilities, realistic requirements, and transparent information about salary, benefits, location, and working arrangements.
What makes a good job description?
A good job description clearly explains the role, responsibilities, expectations, essential skills, qualifications, compensation, benefits, location, and employment conditions candidates need to evaluate the opportunity.
What are the most important parts of a job description?
The key parts include the job title, job summary, responsibilities, essential requirements, preferred qualifications, salary, benefits, location, employment type, working arrangements, and application process.
How long should a job description be?
A job description should be long enough to provide essential information without unnecessary detail. Focus on clarity, scannability, and relevance rather than trying to reach a specific word count.
How do I choose the right job title for a job description?
Choose a recognizable, accurate job title that candidates are likely to search for. Include seniority or specialization when useful and avoid internal jargon, abbreviations, keyword stuffing, and creative titles.
Why is a clear job title important?
A clear job title helps candidates immediately understand the position and can improve discoverability across job boards and search engines by matching terminology job seekers commonly use.
What should a job summary include?
A job summary should briefly explain the purpose of the role, major responsibilities, team context, expected impact, and what makes the opportunity attractive to suitable candidates.
How do you write an engaging job summary?
Start with what the employee will do, explain why the role matters, and highlight a meaningful aspect of the opportunity. Keep the summary concise, specific, and focused on information candidates value.
How many responsibilities should a job description include?
There is no universal number. Prioritize the core responsibilities that define the position and consolidate related tasks rather than creating a long list containing every possible duty.
How should job responsibilities be written?
Write responsibilities with clear action verbs such as manage, develop, analyze, coordinate, design, or optimize. Explain what the employee owns and connect important activities with expected outcomes.
What is the difference between responsibilities and expectations?
Responsibilities describe what an employee owns or does, while expectations describe the standards, outcomes, or performance associated with those responsibilities.
Should job descriptions include performance expectations?
Yes, where appropriate. Clear performance expectations can help candidates understand what successful performance looks like and reduce uncertainty about the employer’s priorities.
What are essential requirements in a job description?
Essential requirements are skills, capabilities, credentials, licenses, or experience genuinely necessary to perform the core responsibilities of the position successfully.
What are preferred qualifications in a job description?
Preferred qualifications are skills or experiences that could strengthen a candidate’s suitability but are not necessary to perform the job and should not automatically determine eligibility.
Why should essential and preferred qualifications be separated?
Separating them helps candidates understand which requirements are mandatory and which are optional, reducing confusion and preventing desirable but unnecessary qualifications from becoming unintended barriers.
Should employers require a college degree in job descriptions?
Only when a degree is genuinely necessary for the role, professional licensing, or specialist knowledge. Otherwise, employers can consider relevant skills, experience, certifications, or equivalent capabilities.
Should job descriptions require a specific number of years of experience?
Use experience thresholds only when they meaningfully reflect role complexity. Demonstrated capability and comparable achievements can sometimes provide better evidence of suitability than an arbitrary number of years.
Should salary be included in a job description?
Including a realistic salary range improves transparency and helps candidates evaluate financial fit before applying. Employers should also comply with applicable pay-transparency requirements in their jurisdiction.
How should salary be written in a job description?
State the currency, salary range, and payment period clearly. For variable compensation roles, consider explaining base salary, commission or bonus structure, and realistic target earnings.
Should employee benefits be included in a job description?
Yes. Clearly describing meaningful benefits such as healthcare, annual leave, retirement contributions, parental leave, learning budgets, or flexible working can help candidates evaluate the overall opportunity.
How do you make a job description more inclusive?
Use neutral, capability-focused language, remove unnecessary requirements, avoid gendered or exclusionary terminology, and describe genuine job requirements rather than assumptions about the ideal candidate.
What language should you avoid in a job description?
Avoid unclear jargon, excessive corporate buzzwords, discriminatory language, unexplained abbreviations, unrealistic claims, and vague phrases such as “rockstar,” “ninja,” or “competitive salary” when specific information is available.
How can a job description improve candidate experience?
A transparent job description reduces uncertainty by clearly communicating responsibilities, requirements, compensation, benefits, work arrangements, location, working hours, and the hiring process.
Should remote or hybrid arrangements be included in a job description?
Yes. Clearly state whether the position is remote, hybrid, or onsite. For remote jobs, explain geographic restrictions, timezone expectations, residency requirements, or required office attendance where applicable.
Should working hours be included in a job description?
Include working hours when they affect candidate decisions, especially for shift work, global teams, weekend schedules, on-call positions, or jobs requiring regular work outside conventional business hours.
How can you make a job description SEO-friendly?
Use an accurate job title, relevant skills and keywords, clear location information, descriptive headings, natural language, and complete job information. Avoid keyword stuffing or inserting unrelated search terms.
What are common job description writing mistakes?
Common mistakes include vague titles, excessive requirements, unclear responsibilities, long introductions, hidden salary information, internal jargon, keyword stuffing, outdated information, and failing to distinguish must-haves from preferences.
Can AI write a job description?
Yes. AI job description generators can create structured drafts, suggest responsibilities, refine wording, and identify missing information. Employers should review generated content to ensure every detail accurately reflects the real role.
How often should job descriptions be updated?
Review job descriptions whenever responsibilities, requirements, compensation, reporting structures, working arrangements, or business needs change. Employers should also review older descriptions before reposting vacancies.
What should I check before publishing a job description?
Check that the title is searchable, responsibilities are specific, requirements are realistic, salary and benefits are accurate, work arrangements are clear, language is inclusive, and application instructions are complete.
Sources
LinkedIn Indeed Google Search Central Google for Developers Harvard Business School Accenture Grads of Life Burning Glass Institute European Journal of Social Psychology Wiley Online Library






















![Writing A Good CV [6 Tips To Improve Your CV] 6 Tips To Improve Your CV](https://blog.9cv9.com/wp-content/uploads/2020/06/2020-06-02-2-100x70.png)


