The one idea
A job description is not a specification. It is a negotiating position written by several people who did not talk to each other.
The hiring manager writes what the work needs. HR adds standard requirements. Someone copies clauses from an older advert for a different role. Nobody deletes anything, because deleting looks like lowering the bar.
The result is a document where the genuinely required items and the decorative ones sit in the same bulleted list, in the same font.
Your job as a reader is to work out which line is load-bearing.
Most job adverts ask for more than the job needs. Find the two or three things it really needs and judge yourself on those.
Separate the JD into must-haves, trainables, and filler. Map your evidence against the must-haves and name the gap explicitly before deciding.
A JD is a noisy signal about a role. Treat repeated mentions, the day-to-day responsibilities section, and the job title itself as high-confidence signals; treat the long tool list as low-confidence.
The mental model: three buckets
Read every line and drop it into one of three buckets.
| Bucket | What it looks like | What it means |
|---|---|---|
| Load-bearing | Appears in the title, repeats in responsibilities, or is legally required (a licence, a degree for a regulated role) | You need this, or a clear substitute |
| Trainable | Named once, in a tool list, alongside four similar tools | They would like it. They will teach it if you show the underlying skill |
| Filler | "Excellent communication skills", "self-starter", "wears many hats", "rockstar" | Carries almost no information about the job |
The test for load-bearing: does this appear in the description of what you would do all day? If the responsibilities say "build and maintain weekly sales dashboards", then dashboard-building is load-bearing and the specific tool is probably trainable. If the responsibilities never mention Python but the requirements list it, Python is probably filler someone pasted in.
Reading the responsibilities section first
Most people read the requirements first because it feels like the test. Read the responsibilities first — the section that says what you would do.
That section is written by whoever needs the work done, and it is the only part that describes reality. Everything else is a filter someone built around it.
Then, when you go back to the requirements, you can ask of every line: would someone doing those responsibilities actually need this?
A JD lists "3+ years of experience" but the responsibilities are: prepare monthly MIS reports, maintain the vendor tracker, coordinate with three regional teams, and support the quarterly audit.
None of that needs three years. It needs someone organised who is good with spreadsheets and not frightened of email. The "3+ years" is a habit, not a requirement. Apply, and lead with evidence that you have done coordination work — a college fest, a family business, a volunteer role.
A JD for a "Marketing Executive" lists content writing, SEO, paid ads, email campaigns, event management, video editing, and CRM administration.
That is three jobs. The company either does not know what it wants, or it intends one person to do all of it for one salary. Both are worth knowing before you interview. Ask in the interview: "Which of these takes up most of the week?" The answer tells you what the job really is — and whether the company has thought about it at all.
Spotting one role advertised as three
Some adverts describe a job. Others describe a headcount problem.
Signals that a single role has been stuffed with multiple jobs:
- Skills from unrelated disciplines in one list — design and backend development, or accounting and social media.
- Seniority mismatch — "own the strategy" next to "handle data entry".
- No mention of a team. If you would be the only person doing this function, you are the whole function.
- The title contains a slash. "Marketing / Operations Associate" is two jobs with a slash in between.
This is not automatically a reason to refuse. A broad role at a small company can teach you more in a year than a narrow one teaches in three. But go in knowing, and ask what success looks like in the first six months — a company that cannot answer that has not thought about the role at all.
Working out your real gap
From advert to decision, in six steps
1 of 6Copy the advert into a document. You need to mark it up. You cannot do this by scrolling.
Try this
Here is a fragment of a real-shaped job advert:
Business Analyst — Fresher Responsibilities: Gather requirements from internal teams. Document processes. Build and maintain reports in Excel. Present findings in weekly reviews. Requirements: Bachelor's degree. 0–2 years experience. Proficiency in Excel, SQL, Python, R, Power BI, Tableau. Strong communication skills. Detail oriented. Ability to work in a fast-paced environment.
Sort the requirements into the three buckets before reading on.
Your challenge
Level 3 · IndependentFind three live job adverts for roles you would genuinely want in the next year. Run all three through the six steps.
You have succeeded when you can produce a single list: the skills that appeared as load-bearing in two or more of the three adverts, and for each one, either your evidence or the word "none".
That list is worth more than any generic "skills to learn in 2026" article, because it was derived from the specific jobs you want rather than from what was popular to write about.
What people usually get wrong
- Treating the requirements list as a pass mark. It is a wish list. Applying when you meet the load-bearing items is normal and expected.
- Applying to everything to increase the odds. Fifty untargeted applications produce fewer interviews than eight targeted ones, and they burn the time you needed for the targeted ones.
- Reading requirements before responsibilities. You will judge yourself against the filter before you have understood the job.
- Assuming the years-of-experience number is real. It is often copied from a previous posting. Judge it against the responsibilities.
- Ignoring what the advert does not say. No mention of a team, a manager, or what success looks like is itself a finding.
- Dismissing a role because of one missing tool. Tools are the most trainable thing on the list and the most heavily listed.
How someone experienced does it
Experienced applicants read the advert for what went wrong before.
"Must be comfortable with ambiguity" often means the role has no defined process yet. "Fast-paced, dynamic environment" frequently means understaffed. "Must manage multiple stakeholders" can mean the last person was caught between two managers who disagreed. None are disqualifying; all are things to ask about in the interview, and asking makes you look like someone who has worked before.
They notice the posting date and re-posts. A role open four months, or posted three times, is telling you something — the pay is out of line, the requirements are impossible, or the manager is hard to satisfy. Worth asking gently: "How long has this position been open?"
And they treat the advert as the first draft of their interview questions. Every load-bearing item is what the interviewer will probe, because it is what they care about. Preparing one example each beats preparing for everything.
When not to use this
This analysis is wasted on internal referrals and on roles where you already know someone doing the job. In both cases you have a better source than the advert — ask the person.
It is also less useful for mass-hiring programmes: campus placements, graduate schemes, and large service-company drives often hire against a standard aptitude and interview process rather than against the posted description. For those, the advert genuinely is a formality, and preparing for the process matters more than parsing the text.
Why the gap between advert and reality keeps growing
Job adverts are written under two competing pressures.
The hiring manager wants applicants who can do the work. The recruiting function wants a defensible filter — something to point at when explaining why one applicant progressed and another did not. Concrete filters are easier to defend, so "5 years of Python" survives editing while "can figure things out" does not, even though the second predicts performance better.
Add automated screening and there is further incentive to list every tool that might appear in a resume, so no good applicant is missed by keyword matching. Nobody is being dishonest. The document serves several purposes at once, and only one of them is describing the job.
Which is why the responsibilities section is more reliable: it is the part written to inform rather than to filter.
Prove it
Produce a one-page gap analysis for the single job you most want right now.
Three sections: what this job is mostly about (one sentence), the load-bearing requirements with your evidence beside each, and the two things you will build or learn in the next month to close the largest gaps.
Keep it. You will use it again in the resume lesson, because those load-bearing items are exactly what your resume needs to prove.
Keep learning this
Paste this into any AI assistant. It turns the assistant into a tutor that tests you instead of just answering you.
Act as an experienced practitioner who is good at teaching. I have just learned analysing a job description and identifying real requirements. Assume I am intelligent but relatively new to this — treat me as beginner level. Work through this in order, and wait for my reply at each step: 1. Ask me 5 questions that test whether I actually understood analysing a job description and identifying real requirements. Do not reveal the answers yet. 2. After I answer, tell me which parts I got right, which I got wrong, and which I only half-understand. Explain only what I misunderstood — do not re-teach what I already know. 3. Give me one practical challenge based on something I could genuinely encounter at work or in daily life. Do not solve it for me. 4. Evaluate my solution the way an experienced person would judge it, including what a professional would have done differently. 5. Tell me what to learn next, and why that comes next. 6. Give me trustworthy sources for deeper study — prefer official documentation, primary research or standards bodies over blogs and videos. Rules for you: no buzzwords. No motivational filler. Say "I'm not certain" when you are not certain, and tell me which parts of your answer I should verify myself. Clearly separate facts from your recommendations and your opinions.
Become independent at this
Use this when you want a path from where you are to actually good, with checkpoints you can test yourself against.
I want to become independently capable at reading job descriptions and assessing fit — not permanently dependent on AI, tutorials or step-by-step guides. Design a progression for me with five stages: Beginner, Guided practice, Independent practice, Real-world application, Professional level. For each stage tell me: - what I must know - what I must be able to do without help - the mistakes people make at this stage - one practical challenge - one real project that would prove I reached this stage - one way I can test myself honestly Then tell me the signals that I am ready to move to the next stage, and the signals that I have skipped ahead too early. Keep the theory to the minimum I actually need. Focus on ability I can transfer to situations you and I have not discussed.