02 · Position for income · Chapter 04 of 35
Decode a job description like evidence, not like a wall of text
Postings are shopping lists written by committees. Your job is to separate must-haves from wishes, then map your proof to the must-haves.
10 min read
A job description is not a contract and it is not scripture. It is a signal of what the employer thinks they need, mixed with leftover language from the last posting, mixed with HR compliance phrases. Read it as evidence of priorities.
Four layers in every posting
- Responsibilities — the work. Highlight action verbs: coordinate, analyze, sell, manage, build, support, lead, resolve, implement, forecast, document.
- Requirements — the gates. Separate true must-haves (license, work authorization, specific software used daily, years in a regulated setting) from preferences (bachelor’s degree when the work is skill-based, ‘nice to have’ tools).
- Repeated language — if ‘stakeholder,’ ‘queue,’ ‘quota,’ ‘HIPAA,’ or ‘month-end close’ appears three times, it is not filler. Mirror it only when it is true.
- Questions — capture unclear scope, metrics, team size, schedule, tools, and whether this role is new or backfill. Those become interview questions and networking questions.
The must-have vs. flexible test
| Usually a real gate | Often flexible if proof is strong |
|---|---|
| Required license, security clearance, or certification named as mandatory | Degree when equivalent experience is listed |
| Specific ERP/EHR/CRM the team lives in, if they say ‘daily’ | A second tool in the same category (HubSpot vs. Salesforce at coordinator level) |
| Shift, location, travel, lifting, on-site days | ‘5–7 years’ when you have 4 years of the same outcomes |
| Language fluency if the customer base requires it | Industry experience when the process skills transfer |
| Legal work authorization for that country | Every bullet in a 22-bullet wish list |
A 12-minute decode ritual
- 01Copy the posting into a plain document. Job links die.
- 02Highlight 8–15 meaningful terms: title, skills, tools, credentials, domain words, outcomes.
- 03Mark each Yes / Related / No against your real history.
- 04If fewer than half the core responsibilities are Yes or honest Related, skip the role. That is qualification, not fear.
- 05Write three bullets you would need to move or rewrite on your resume before applying.
- 06Write two questions the posting did not answer.
Decode snippet — ‘Customer Success Coordinator’
Posting repeats: onboarding, Zendesk or similar, QBR prep, churn risk flags, Salesforce hygiene, 40–60 accounts. Must-haves: CRM, written customer communication, ability to run a book of existing accounts (not hunt new logos). Flexible: ‘SaaS experience’ if you have onboarding in another subscription or account-based environment. No: ‘build the CS strategy from scratch’ — that is a manager role hiding in a coordinator title. Decision: apply if you have ticket + account coordination proof; do not apply if your only history is one-off retail transactions with no follow-up.
Do this now
- Decode one live posting with the Yes / Related / No method in the Keyword Sheet.
- If the role is a No on a true gate, archive it. Do not ‘just apply anyway.’
4 / 35