A working guide to writing job posts that hold up under scrutiny — from the job seeker scrolling on a lunch break to the one who wasn’t even looking.
By Tista Munshi · Reading time: 11 minutes
Most job descriptions are written the way a form is filled out — obligations first, humanity somewhere near the bottom, if at all. They read like they were assembled from a template three reorganisations ago, and in a lot of companies, they were. That would be a minor stylistic complaint if job descriptions weren’t also, for most candidates, the very first and sometimes only impression a company makes. A poorly built job post doesn’t just fail to attract talent. It quietly convinces the right people that they don’t belong here, and it doesn’t even tell them why.
This piece is about fixing that — not with tricks, but with a clearer understanding of who is actually reading the post, and what they need from it before they’ll act.
Why Most Job Descriptions Fail Before They’re Even Read
Open ten job postings for the same role at ten different companies and you’ll find the same five paragraphs rearranged. A list of responsibilities that reads like a task audit. A wall of requirements that seems designed to filter out anyone with self-respect. A one-line mention of “competitive salary” that tells the reader nothing except that the number is probably not competitive. And somewhere, almost as an afterthought, a line about “growth opportunities” that could belong to any job, at any company, in any decade.
None of this is malicious. It happens because job descriptions are usually written under time pressure, by whoever is free that week, using whatever template exists from the last hire. The result is a document built for compliance and internal sign-off — not for the person on the other side of the screen, deciding in about thirty seconds whether to keep reading.
The Thirty-Second Reality
Recruiters and job seekers behave the same way when they scan: eyes go to the title, then the first two lines, then they either commit or move on. If those first few lines don’t answer “is this worth my time,” everything below them — however well written — goes unread. Structure, in this sense, is not decoration. It is the mechanism that decides whether the rest of your message gets a chance.
The Psychology Gap: Active vs. Passive Candidates
It helps to stop thinking of “candidates” as one audience. An active candidate has already decided to leave, has a resume open in another tab, and is comparing your post against four others in the same session. A passive candidate isn’t looking at all — they’re doing their actual job, and your post has to interrupt that with enough relevance to earn a second look.
What Active Candidates Need
A title that matches exactly what they’re searching for — not a cute internal name for the role.
Fast clarity on salary band, location, and work mode, because they are actively comparing offers.
A short, low-friction application process. Every extra field is a reason to close the tab and try the next listing.
What Passive Candidates Need
A reason the move is worth the disruption — not just a list of duties similar to what they already do.
Evidence of the team and culture, since they have no urgency pushing them to overlook uncertainty.
Respect for their time: passive readers give a post far less benefit of the doubt than someone already job hunting.
The core insight: a job description written only for active candidates will read as transactional to a passive one, and a job description written only to “sell the dream” will frustrate an active candidate hunting for hard facts. The strongest postings do both, in the right order.
Press enter or click to view image in full size
Anatomy of a Job Description That Actually Converts
A job description that works for both audiences tends to follow a consistent internal logic, even when the writing style varies. Below is the structure worth building from.
The Job Title
Resist the instinct to make it clever. “Growth Ninja” and “People Superhero” score points internally and lose search visibility externally, because nobody searches those terms. Use the title a candidate would actually type into a search bar — seniority level included.The Opening Hook
The first two sentences carry more weight than the rest of the post combined. Say what the role actually changes — for the product, the team, or the company — before listing what the person will be doing day to day.Responsibilities, Written as Outcomes
“Manage social media calendars” describes a task. “Grow organic reach by planning and executing a consistent content calendar” describes an outcome a candidate can picture themselves achieving. Where possible, write to the second version.Requirements vs. Nice-to-Haves
Separate the two, honestly. Research on hiring behaviour has repeatedly shown that inflated requirement lists discourage qualified candidates — particularly women — from applying, even when they meet the substance of the role (Mohr, 2014). A shorter, honest list produces a stronger applicant pool than a defensive one.Compensation and Culture
Where local norms and law allow, include a salary band. Absence of a number doesn’t hide a low offer — it just filters out candidates who would have accepted it, alongside the ones who wouldn’t have.The Call to Action
End with exactly what happens next — how long the process takes, how many rounds, who they’ll hear from. Ambiguity here is one of the most common reasons candidates disengage after applying.
Writing for Passive Candidates: The Silent Majority
Estimates vary, but a large share of the professional workforce — often cited around three-quarters — is not actively job hunting at any given time, even though many are open to a better opportunity if one is presented well (LinkedIn Talent Solutions, 2023). Ignoring that group in favour of pure keyword-stuffed, application-form-first writing means competing only for the smaller, more contested pool of people already applying everywhere.
Write on Medium
Writing for passive candidates means leading with context before instructions: what the team is building, why the role exists now, what changes for the person a year in. It’s closer to a short editorial than a form. The details an active candidate wants — salary, location, process — still belong in the post, just placed so they don’t have to carry the entire pitch alone.
Making Job Posts Findable: SEO and Generative Search Basics
A well-written job description that nobody finds does no work at all. Two separate but related things determine whether a post surfaces: traditional search engine optimisation, and increasingly, how well it’s structured for the AI-driven answer engines many candidates now use to ask “what companies are hiring [role] in [city].”
For Traditional Search
Use the exact role title candidates search for, including common synonyms, once naturally in the body.
State the city and work mode (remote, hybrid, onsite) plainly — location modifiers are some of the highest-intent search terms in job search.
Name the specific tools, platforms, or skills required, since these double as long-tail search terms.
For Generative and AI-Assisted Search (GEO)
Generative engines summarise and recommend based on how clearly a page answers a question. A job post structured with clear headings, direct statements of role, location, and requirements, and no ambiguous jargon is easier for these systems to extract and represent accurately — which increasingly means it’s easier for a candidate to be pointed toward it, even without a direct search.
How an ATS Like Xyntara Turns a Good Job Description Into Better Hires
Writing a strong job description is only half the equation — the other half is knowing whether it’s actually working. This is where a modern applicant tracking system earns its place in the process, not as a replacement for good writing, but as a feedback loop for it.
On Xyntara, a free Indian job portal and ATS built for both recruiters and job seekers, a posting doesn’t just sit static after publishing. Recruiters can see how a listing performs — views versus applications, where candidates drop off, which roles attract strong matches quickly and which stall — and use that signal to revise language, retitle a role, or adjust the requirements list before it costs another two weeks of low response. For candidates, Xyntara’s resume parsing and scoring gives a practical, immediate read on how well a profile aligns with a posting, closing some of the guesswork on both sides of the same conversation.
The point isn’t that software writes better job descriptions. It’s that a platform designed around the whole hiring loop — posting, applying, screening, feedback — makes it far easier to notice when a job description isn’t working, and to fix it with evidence instead of instinct.
Common Mistakes That Quietly Repel Good Candidates
Overloaded Requirement Lists
Fifteen “must-haves” for a mid-level role signals either poor role scoping or an unrealistic search — both of which discourage strong candidates who read carefully.
Buried or Missing Compensation
Silence on salary is increasingly read as evasiveness rather than discretion, particularly among younger job seekers who have grown up with more pay transparency online.
Jargon Without Translation
Internal shorthand (“L4,” “Pod structure,” team nicknames) means nothing to an external reader and adds friction exactly where clarity is needed most.
No Sense of the Team
A role described purely in terms of tasks, with no mention of who the person will actually work with, leaves passive candidates with nothing to imagine themselves joining.
A Long, Uncertain Process With No Timeline
Candidates tolerate a multi-round process far better when they know what it looks like in advance.
A Practical Checklist Before You Hit Publish
Press enter or click to view image in full size
Frequently Asked Questions
What is the difference between writing for active and passive candidates?
Active candidates are already searching and comparing openings, so they respond well to clear titles, salary ranges, and fast application steps. Passive candidates aren’t looking, so the post has to do more work — establishing the mission, the growth path, and the team culture before it asks for anything at all.
How long should a job description be?
Most well-performing postings fall between 400 and 700 words — long enough to answer the questions a serious candidate actually has, short enough that nobody abandons it halfway through.
Should I list salary in a job description in India?
Where feasible, yes. A visible range reduces mismatched applications and reflects the transparency Indian job seekers increasingly expect from modern job portals.
How does an ATS like Xyntara help with job description quality?
It won’t write the description for you, but it shows how a posting actually performs — views, application rate, and where candidates drop off — so revisions can be based on real behaviour instead of guesswork.
What keywords should a job description include for better search visibility?
The exact job title candidates search for, the seniority level, core skill or tool names, the work mode, and the city — these are the terms both search engines and job-portal filters rely on most heavily.
Conclusion
A job description is rarely treated as a piece of writing that has to earn a reaction, but that’s exactly what it is. The candidates worth hiring are reading closely, comparing tone against substance, and deciding — often in the time it takes to read two sentences — whether the rest is worth their attention. Structuring the post around both the person already looking and the person who wasn’t planning to look today is less about following a formula and more about respecting that thirty-second window for what it actually is: the whole pitch.
Final Thoughts
None of this requires a copywriting background. It requires slowing down long enough to ask who is actually going to read this, and what they’d need to know before they’d act on it. The companies that get this right aren’t necessarily the ones with the biggest hiring budgets — they’re the ones willing to rewrite a job post after noticing it isn’t working, rather than assuming the candidates were the problem.
References
Mohr, T. S. (2014). Why Women Don’t Apply for Jobs Unless They’re 100% Qualified. Harvard Business Review. hbr.org/2014/08/why-women-dont-apply-for-jobs
LinkedIn Talent Solutions (2023). The Ultimate List of Recruiting Statistics. business.linkedin.com/talent-solutions
Society for Human Resource Management (SHRM). Writing Job Descriptions. shrm.org/topics-tools/how-to-develop-job-descriptions
Xyntara. Job Portal & Recruitment Management Platform — Feature Details. xyntara.com
Written by: Tista Munshi
About the Author: Tista Munshi is a content strategist specialising in SEO and Generative Engine Optimisation (GEO). She helps brands create search-intent-driven content aligned with evolving digital discovery trends in India.
Top comments (0)