Pull five things out of the posting and write them on one page: the must-haves, the nice-to-haves, the words the posting repeats, the problem the team is trying to solve, and the culture signals. For a typical 900-word posting that takes about ten minutes, and the page you end up with is the document you write the resume and cover letter from.
Most people skip this. They read the posting once, feel roughly qualified, and start editing the resume. Then they tailor to the wrong things, because a posting buries its real priorities under a mission paragraph, a benefits list and a legal disclaimer.
Why a brief beats a read-through
Advertisement
Harvard's career office puts the goal simply: your resume should reflect the types of skills the employer would value. You cannot reflect what you have not isolated, and a posting does not isolate anything for you. It lists 14 responsibilities as if they mattered equally. They do not.
A brief forces the ranking. Once you have five short lists on one page, the resume edit becomes mechanical: one bullet per must-have, one sentence per problem, the repeated words placed once each where they are true.
The five things to extract
Work through the posting in this order. Keep a blank page open and write as you go.
1. Must-haves
Anything under "Requirements," "Minimum qualifications" or marked "required." Strip the generic ones (strong communication skills, team player) and you are usually left with four to seven real items: a tool, a credential, a number of years, a type of experience.
2. Nice-to-haves
Anything marked "preferred," "a plus," "bonus," "ideally" or "familiarity with." Also move any must-have here that is clearly aspirational, like eight years in a tool that has existed for five. The must-have versus nice-to-have split is the single most useful thing in the brief, because it tells you which gaps to address and which to ignore.
3. Repeated words
Any noun or verb that appears three or more times across the posting. Those are the job description keywords, and they matter twice: once because a person wrote them repeatedly without noticing, and once because resume databases are searched on them. Purdue's writing lab makes the same point about scannable resumes: include nouns and noun phrases that are likely to be used in a database search.
4. The problem the team has
Read the responsibilities as symptoms. "Build reporting from the ground up" means there is no reporting. "Own the vendor relationship" means the last person did not. The first responsibility listed is almost always the one they are hiring for; the last three are what everyone on the team does.
5. Culture signals
"Fast-paced," "wear many hats," "self-starter," "cross-functional," "hybrid, three days in office." Write down the exact phrases and what they imply. Also note what is missing: no salary, no manager title, no team size. Absence is a signal too.
A worked example: 900 words to one page
Here is an invented posting of the kind you see every day. Marketing Operations Specialist, Brightline Health, Denver, hybrid. The full posting runs 912 words. These are the parts that matter:
You will own our HubSpot instance end to end, including lead routing, lifecycle stages and campaign reporting. You will build dashboards for the marketing and sales leadership team and present results monthly. You will partner with Sales Ops to clean and de-duplicate our contact database. Requirements: 3+ years in marketing operations, HubSpot administration experience, advanced Excel, experience with lead scoring. Preferred: Salesforce, SQL, healthcare experience. We move fast, we are a small team, and everyone here does a bit of everything.
Timed, the extraction took eleven minutes. Here is the brief.
| Brief item | What the posting gave up |
|---|---|
| Must-haves | 3+ years marketing ops, HubSpot admin, advanced Excel, lead scoring |
| Nice-to-haves | Salesforce, SQL, healthcare background |
| Repeated words | "HubSpot" (6 times), "reporting" or "dashboards" (5), "lead" (5), "Sales" (4) |
| The problem | Reporting does not exist yet and the contact database is dirty; leadership wants numbers monthly |
| Culture signals | "Move fast," "small team," "does a bit of everything," hybrid three days, no salary listed |
Notice what the brief did to the posting. Fourteen responsibilities became one problem. Ten requirements became four that matter and three that would be nice. Nine hundred words became about 120, and every one of them tells you what to write next.
Map the brief to the resume
Give each must-have one bullet that proves it, near the top of the most recent role. For Brightline that is four bullets: one on HubSpot administration, one on a reporting build, one on lead scoring, one that shows Excel at a real level (a model, a reconciliation, not "proficient in Excel").
Nice-to-haves get a bullet only if you actually have them. Do not invent a Salesforce line because it is preferred; do add a short "healthcare client" mention if it is true, because it costs nothing.
Repeated words go in verbatim, once each, where they are already accurate. Write "HubSpot," not "marketing automation platform," if HubSpot is what you used. Then run the resume and posting through the ATS resume checker to see which must-haves the resume still never mentions by name. There is usually one.
Map the brief to the cover letter
The problem row is your middle paragraph. State their problem in your words, then give one piece of evidence that you have solved it before: "You need monthly reporting that does not exist yet. At my last company I built the first marketing dashboard from a HubSpot export in six weeks, and leadership still uses it."
The culture row sets the register. "Small team, does a bit of everything" means one sentence about range is welcome; a stiff formal tone is not. Paste the brief and your two or three facts into the cover letter generator and you will get a draft that already speaks to the right problem instead of praising the company's mission.
When the posting says nothing
Some postings produce an empty brief. The must-haves are "a bachelor's degree and strong communication skills," the responsibilities could describe any office job, and no problem emerges no matter how you read it.
Treat that as information. It is either a template posting an agency reuses, an evergreen listing kept open to collect resumes, or a role that is not really being filled. Run it through the ghost job detector before you spend an afternoon on it, and if you apply anyway, apply with your general resume and move on.
Ten minutes, five lists, one page
Skim once for structure, then read once with the five headings on a blank page and fill them in. Count repeated words rather than guessing. Write the problem as a sentence, not a list.
If the posting is very long, paste it into our free text summarizer first to get a condensed version you can read in a minute, then do the five-item extraction by hand, because the ranking is the part only you can do.
FAQ
How long should a job description summary be?
One page, and shorter is better. The five lists plus a one-sentence problem statement come to 100 to 200 words for most postings. If your brief runs longer than that, you have copied responsibilities instead of ranking them; go back and cut everything that appears only once.
Do I need to meet every must-have before I apply?
No. Postings are wish lists written before the hiring manager has met a single candidate, and the must-have section often includes items that belong under preferred. If you meet most of the must-haves and can speak to the first two responsibilities, apply, and address the gap in one plain sentence in the cover letter rather than hoping nobody notices.
Should I copy job description keywords into my resume?
Yes, once each, and only where they are true. Use the posting's exact noun for a tool or method rather than a synonym, because a database search matches the word, not the idea. Do not repeat a keyword five times or hide a keyword block in white text; a person reads the resume after the software does, and both approaches read as padding at best.
What is the difference between a must-have and a nice-to-have in a job description?
A must-have is a requirement the employer will screen on: a credential, a tool, a minimum number of years. A nice-to-have is something that would make the job easier but will not disqualify you, and postings usually mark them with "preferred," "a plus" or "ideally." When a posting does not label them, assume the first three or four requirements are real and everything after that is negotiable.
