Separate must-haves from nice-to-haves in a job posting and map each requirement to your evidence.
Why it matters
A job posting is a wish list written by several people, sometimes copied from an older posting. Read literally, many entry-level postings seem to want years of experience and a dozen tools. Learners often either apply to nothing (because they do not meet every line) or apply to everything with the same CV (and hear nothing back). Reading postings well lets you apply to the right jobs with the right evidence.
The core idea: decode, then map
Read every posting in two passes:
- Decode it: what does this team actually need someone to do in the first six months?
- Map it: for each requirement, what evidence do you have?
Anatomy of a posting
| Section | What it tells you |
|---|---|
| Title and level | "Junior", "Associate", "I" or "Entry-level" are good signs. "Senior" or "Lead" usually means several years. |
| About the team | the product, users and team size; useful for your cover letter and interview |
| Responsibilities | the real daily work; the best clue to what they will test you on |
| Requirements / qualifications | the must-haves (often called "required" or "minimum") |
| Preferred / nice to have / bonus | not required; strengths that set candidates apart |
| Benefits, salary range, location | many places now require salary ranges in postings; check remote, hybrid or on-site |
Worked example
Junior Data Analyst. You will build weekly sales dashboards, answer ad-hoc questions from the sales team and help clean our CRM data. Requirements: strong SQL; experience with Excel or Google Sheets; clear written communication; bachelor's degree or equivalent experience. Nice to have: Python, Tableau or Power BI, experience in retail.
Decode:
- Daily work: dashboards, quick SQL questions, data cleaning.
- Must-haves: SQL, spreadsheets, writing, a degree or equivalent experience (so not strictly required).
- Nice-to-haves: Python, a BI tool, retail.
Map (a learner's table):
| Requirement | Evidence | Status |
|---|---|---|
| Strong SQL | late-buses project (joins, window functions); SQL Fundamentals course | yes |
| Excel/Sheets | library dashboard in Google Sheets | yes |
| Written communication | project READMEs; blog post on the bus analysis | yes |
| Degree or equivalent | no degree; 2 years in retail operations + portfolio | partial |
| Python (nice) | pandas in the bus project | yes |
| BI tool (nice) | none | gap |
| Retail (nice) | 2 years as a store supervisor | yes |
The learner meets most must-haves and has a retail background the posting values. Apply, and spend a weekend building one small Power BI or Tableau Public dashboard to close the gap for future applications.
Reading between the lines
- "Or equivalent experience" means the credential is flexible.
- "Familiarity with" is weaker than "strong" or "expert in".
- Years of experience on entry-level roles are often soft, but "5+ years" on a junior posting is a sign of a confused or unrealistic posting.
- A long list of unrelated technologies often means the posting was assembled by committee; focus on the responsibilities.
- Hard requirements are real: a teaching licence, a security clearance, the legal right to work in the country, or a certification required by a government contract cannot be argued around.
Red flags
- Requests to pay for training, equipment or a background check before hiring.
- Unpaid "trial projects" that look like real client work.
- Interviews only by chat app, offers without interviews, or requests for bank details early. These are common job scams.
- No company name or a company you cannot find any information about.
Tailoring your application
Use the posting's language in your CV when it is true for you. If it says "build dashboards", write "Built a weekly dashboard tracking..." rather than "Created visualisations". Many companies use applicant tracking systems that search for these terms, and human reviewers scan for them too. Lead each bullet with a result: "Cut a monthly report's run time from 40 s to 3 s by adding an index".
Common mistakes
- Not applying unless you meet 100%. Many hires meet most, not all, requirements.
- Ignoring hard requirements such as licences, clearances or right to work.
- Sending the same CV everywhere.
- Skipping the responsibilities section, which predicts the interview.
Quick recap
- Decode what the team needs, then map each requirement to your evidence.
- Separate must-haves from nice-to-haves; "or equivalent" means flexible.
- Apply when you can evidence most must-haves; close the biggest gaps over time.
- Watch for scams and respect true hard requirements.
Try it
Open the Do tab to map a real posting to your evidence.