How to Read a Job Description: What Really Screens You Out

2026-10-12

Most advice on reading a job description says the same thing: highlight the keywords, match your resume to them, apply if you meet 60 percent of the requirements. That advice treats a job posting like a checklist. It is not one. A job posting is a committee document, and different lines in it carry very different weight. If you treat every line equally you will either skip jobs you should have applied for or burn hours tailoring applications for jobs where one missing line was always going to end the process.

I spent more than 25 years in agency leadership, including as an EVP at Starcom, and I wrote, approved, and argued over job descriptions for most of that time. The pattern is consistent: the people who wrote the posting do not mean every line the same way. This guide gives you a three-tier method to sort any posting in about ten minutes, a verb decoder that tells you what the job really is, a full worked example, and a scorecard that tells you whether to apply, apply through a referral, or move on.

Why a job description is a committee artifact

A typical posting is assembled from at least three sources. The hiring manager contributes the real work: the first several responsibilities, usually in the order of what is on fire. HR or a recruiter contributes the standard frame: degree requirements, years of experience, equal opportunity language, and the "ability to work in a fast-paced environment" paragraph. Stakeholders from adjacent teams contribute additions late in the process: "familiarity with Salesforce," "experience partnering with legal," "strong executive presence." Often a fourth source is the resume of the person who just left, converted into requirements.

This matters because each source has a different level of commitment to its lines. The hiring manager will fight for the first few responsibilities. HR will enforce the legal and compliance lines. Everyone else's additions are wishes. When you read a posting as one voice, you cannot tell which line is a wall and which is a wish. When you read it as three or four voices, the structure becomes obvious.

The Gate, Weight, Wishlist method

Sort every line of the posting into one of three tiers before you decide anything.

Tier 1: Gates (binary, checkable, enforced)

A gate is a requirement that someone can verify as true or false in under a minute, and that the company has a reason to enforce. If you fail a gate, no amount of strong experience elsewhere rescues the application. Gates include:

Work authorization and location. "Must be authorized to work in the US without sponsorship." "Onsite three days a week in Chicago." These are filtered by the applicant tracking system or by the recruiter's first pass.
Licenses and certifications the work legally requires. A CPA for a technical accounting role, an RN license, a security clearance, a Series 7. If the law requires it, the company cannot waive it.
Hard language, travel, or schedule requirements. "Fluent in Spanish." "Travel 50 percent." "Rotating weekend coverage."
Regulated-domain tenure. "Five years in a regulated financial services environment" is often a gate because the compliance team reviews it, even when the rest of the posting is flexible.

The test for a gate: could a recruiter reject you on this line without reading the rest of your resume? If yes, it is a gate. Note that a degree requirement is a gate only when the role legally needs it, or when the company is large and rigid enough that the ATS auto-filters on it. At most employers a "Bachelor's degree required" line is softer than it looks, and a strong adjacent track record routinely substitutes. But check, because at some large employers it is enforced mechanically. When in doubt, find someone who works there and ask.

Tier 2: Weighted requirements (the actual job)

Weighted requirements are the skills and outcomes the hiring manager will use to decide between finalists. You identify them with three tests.

The position test. Responsibilities near the top of the list are typically the hiring manager's priorities. The last four bullets are usually boilerplate or additions. If a skill appears in the first three responsibilities, treat it as weighted.
The repetition test. If the same capability appears in the summary, the responsibilities, and the qualifications, it is weighted. A posting that mentions "stakeholder management" once is being polite. A posting that says it in the summary, in two responsibilities, and in the qualifications is describing the central pain of the job.
The title test. Whatever the title implies must show up in the weighted list. A "Senior Manager, Lifecycle Marketing" posting that spends most of its words on email, retention, and segmentation is telling you the weight is lifecycle, even if "paid acquisition" appears once in a long list.

Most postings have between four and seven weighted requirements. Those are the lines you must be able to speak to with specific evidence on your resume, your LinkedIn profile, and in the interview.

Tier 3: Wishlist (preferred, bonus, familiar with)

Wishlist lines are easy to recognize once you look for them. They live after phrases like "preferred," "nice to have," "bonus," "familiarity with," and "exposure to." They also include lists of tools after a conjunction ("Salesforce, HubSpot, Marketo, or similar"), adjective stacks ("self-starter, strategic, collaborative, scrappy"), and years-of-experience numbers that exceed what the hiring manager's own team has. Wishlist lines should never stop you from applying. They matter at the margin when two finalists are otherwise equal.

One caution on years of experience. "8+ years" is a wishlist line far more often than a gate. It exists because someone needed a number. The exception: when the posting also says the role leads a team of people with that tenure, or the title is Director or above, in which case the seniority signal is real even if the exact number is not.

The verb decoder: Build, Run, Fix, Grow

The single most useful thing I teach people about job descriptions is to read the verbs, not the nouns. Nouns tell you the function. Verbs tell you the situation you are walking into, and the situation determines who gets hired. There are four main verb families.

Build / Launch / Establish / Stand up. The function does not exist yet or exists informally. The company wants someone comfortable with ambiguity, who has done a zero-to-one before, and who can operate without a playbook. Evidence that wins: you created something where nothing existed, and you can say what the first 90 days looked like.
Run / Manage / Oversee / Own. The function exists and works. The company wants continuity and reliability. Evidence that wins: you ran a comparable scope for multiple cycles without drama, you hit targets repeatedly, and your team stayed.
Fix / Turn around / Improve / Streamline / Modernize. Something is broken and leadership knows it. The company wants a diagnostician with political skill, because fixing means changing how other people work. Evidence that wins: before-and-after results where you inherited a mess, and a clear account of how you handled resistance.
Grow / Scale / Expand / Accelerate. The function works at a small size and the company wants it bigger. Evidence that wins: you scaled something through at least one inflection, and you know what broke along the way.

Many postings mix these. The mix tells you the real job. "Build and run our lifecycle program" is two jobs, and the hiring manager may not have noticed. When you see a mix, ask in the first interview which one is more urgent. The answer tells you what to emphasize for the rest of the process.

Also read the collaboration language. A posting full of "partner with," "align with," and "influence" describes a matrix organization where you will have responsibility without authority. A posting that says "own," "decide," and "report directly to the VP" describes real authority. "Wear many hats" and "fast-paced" almost always mean understaffed. That is not automatically bad, but it should change what you ask about team size and budget before you accept.

Worked example: one posting, fully triaged

Here is a condensed, invented posting so you can see the method run end to end. It is not a real company.

Senior Manager, Customer Lifecycle Marketing

Summary: We are looking for a lifecycle marketer to own and grow our email and in-app programs for our subscription product. You will partner closely with Product and Data to improve retention.

Responsibilities: (1) Own the lifecycle roadmap across onboarding, activation, and win-back. (2) Build segmentation and testing programs that improve 90-day retention. (3) Manage a team of two. (4) Partner with Product on in-app messaging. (5) Report on performance to the VP of Marketing monthly. (6) Collaborate with Creative on templates. (7) Stay current on industry trends.

Qualifications: 6+ years in lifecycle or CRM marketing. Experience with a marketing automation platform (Braze, Iterable, Klaviyo, or similar). Strong analytical skills. Bachelor's degree. Self-starter in a fast-paced environment. Preferred: SQL, experience in a subscription business, MBA.

The triage

Gates. The posting lists no license, location, or authorization language in this excerpt, so the only candidate gate is the Bachelor's degree. At a company of this kind, treat it as soft unless the careers page says otherwise.

Weighted. The first two responsibilities carry the weight: owning a lifecycle roadmap and building segmentation and testing programs that move 90-day retention. "Retention" appears in the summary and again in responsibility (2). "Partner with Product" appears in the summary and responsibility (4), so cross-functional influence is a fourth weighted item. The marketing automation platform is repeated in the qualifications and implied by the whole job. So the weighted list is: lifecycle roadmap ownership, segmentation and testing for retention, working with Product, and fluency in an automation platform. Managing a team of two is weighted lightly, since two people is a small team and signals a player-coach role.

Wishlist. SQL, MBA, subscription experience, and "stay current on industry trends." The tools list "or similar" means any comparable platform counts.

Verbs. "Own and grow" and "improve retention" place this in the Run and Grow families, with a light Fix element since retention is the stated problem. This is not a zero-to-one role.

The candidate side

Say you are a CRM marketing manager at an e-commerce brand with five years of experience. You have run email and SMS programs and A/B tests, you used Klaviyo, you have not worked in subscription, and you have managed one contractor. Score yourself against the weighted list only: roadmap ownership (yes, you built the quarterly CRM plan), segmentation and testing for retention (yes, repeat purchase rate is retention's close cousin), working with Product (weak, you worked with web developers, not product managers), automation platform (yes, Klaviyo counts as "or similar"). That is three clear yeses and one weak match, with the wishlist mostly missing. You fall short on the 6+ years line, but that line is wishlist-grade for a Senior Manager role at this kind of company.

Decision: apply. Then use the weighted list to rewrite the parts of your application that touch it, in the same language the posting uses.

The rewrite

Before, in your resume:

Managed email and SMS campaigns for an online apparel brand. Ran A/B tests on subject lines and send times. Worked with web team on site updates.

After, aimed at this posting:

Owned the CRM roadmap for an online apparel brand across onboarding, post-purchase, and win-back flows in Klaviyo. Built a segmentation model by purchase frequency and category and tested 31 variants over two quarters, lifting 90-day repeat purchase rate from 22 percent to 27 percent. Partnered with the product team on the account-page redesign that carried loyalty messaging, the closest equivalent to in-app lifecycle work.

Notice what changed. The verbs match the posting (owned, built). The evidence maps to the weighted items in the order the hiring manager listed them. The weak area, product partnership, is addressed with the closest honest equivalent instead of being ignored. The numbers in this example are illustrative, so use your own real figures. If you do not have a number, use the approach in how to quantify achievements without metrics.

Your LinkedIn headline should echo the same weighted items, not the title you hold: CRM and Lifecycle Marketing | Retention, Segmentation, and Testing | Klaviyo. For more on headline construction, see LinkedIn headline for job seekers.

The apply, refer, or skip scorecard

After you triage, run the posting through this scorecard. It takes two minutes.

Gates. Do you pass every gate? If you fail one, skip unless you have a referral who can confirm the gate is flexible. Do not spend time tailoring.
Weighted coverage. Count your clear matches against the weighted list, and count adjacent matches separately. With five weighted items, four or more clear matches is a strong apply. Two or three clear matches plus adjacent ones is an apply-with-referral: your resume alone will be a coin flip, but a person vouching for you changes the odds. One or fewer clear matches is a skip, or a stretch application you should not invest hours in.
Verb fit. Have you actually done what the main verb says? Someone who has only run programs should be cautious about a Build posting, and the reverse is also true. If the verb family does not match your record, you need a story that explains why you are ready, not just a resume.
Posting age. A posting more than three weeks old at a company that is not known for slow hiring may be stale. See how to spot ghost jobs before you invest.
Effort budget. Spend your tailoring time in proportion. For an apply, tailor the top third of your resume and your headline. For a skip, spend nothing. For a referral play, spend the time on the message to the person, not on the resume.

How to use the posting after you apply

The triage is not finished when you hit submit. The weighted list is your interview map. For each weighted item, prepare one specific story with a situation, the decision you made, and the result. Prepare a second, shorter story for the item you are weakest on, framed honestly as adjacent. Then prepare two questions that show you read the verbs: "Is the more urgent priority in the first six months to build the testing program or to improve the programs already running?" That single question tells the interviewer you can read what they are really hiring for.

It also helps with applicant tracking systems. Because you mirrored the weighted language instead of stuffing every keyword, your resume reads naturally to a human and still contains the terms an ATS looks for. See how to beat applicant tracking systems for the mechanics.

Five mistakes this method prevents

Treating years of experience as a gate. It rarely is. Apply anyway when the weighted items match.
Tailoring to the wishlist. People rewrite their resume around a preferred tool that the hiring manager will not weigh. Put your effort in Tier 2.
Ignoring the verbs. Two postings with the same title can describe opposite jobs.
Applying to everything at 60 percent. The 60 percent rule counts lines. The method counts weight. Sixty percent of the weighted list is a strong application. Sixty percent of the wishlist is nothing.
Skipping the gates check. A missing license or authorization line wastes the entire effort. Check gates first, before anything else.

A one-page version you can reuse

Copy this into a note and fill it in for every posting before you invest time:

Gates: list them, mark pass or fail.
Weighted (4 to 7 items): list them, mark clear, adjacent, or none.
Wishlist: list the two you can mention if asked.
Main verb family: Build, Run, Fix, or Grow. Do I have a matching story?
Decision: apply, apply with referral, or skip.
Top-third resume change: one sentence.
Headline echo: one phrase.

Once you have done this for five postings, you will do it in the time it takes to read the posting once. The bigger benefit is cumulative: your search stops being a volume game and becomes a series of deliberate bets, and the profile and resume you present are built around what each employer actually weighs.

Check your profile against the postings you are chasing

The method above only works if your LinkedIn profile and resume carry the evidence the weighted list asks for. If you are not sure they do, an Avery audit scores your profile against the role you are targeting and gives you specific rewrites for the headline, About section, and experience bullets. See Avery audit options.