How to Write a Job Description for a Resume (2026)

8 min read

Searchers land here with two different problems mashed into one phrase. HR teams write job descriptions to hire. You write job descriptions on a resume to prove you already did comparable work, and you don't need to pretend the two documents are the same thing.

Check your resume for free against the posting you care about tonight. If must-have tools only appear in a Skills paragraph, you're not done yet.

You'll compare honest mirroring against stuffing, map posting lines to bullets you own, and stop before the file turns into a word cloud. That's the whole job for this rewrite pass, and it won't take all night if you stick to one req.

This won't make a stretch role fit. It stops a qualified candidate from losing to someone who translated the same history into the employer's language without inventing tools they never touched.

Posting language vs Experience proof

The employer posting is forward-looking: responsibilities they want filled next quarter. Your resume job description is backward-looking: what already happened on your watch, with dates and tools attached.

Recruiters compare those two texts side by side, but they are not running a keyword bingo card. They are checking whether your latest role sounds like the room they are hiring into.

Before: You treat the posting as a paste target and wonder why silence follows.
After: You treat it as a phrase bank for bullets you can defend with scope and metrics.

Before: You list every duty you were ever assigned.
After: You lead with outcomes and let duties sit inside the verb choice.

For a line-by-line worksheet on a single req, use how to use a job description to rewrite resume bullets . This page stays on the fork: mirror language without stuffing.

Greenhouse and Workday both index recent Experience heavily. The first two bullets under your latest employer carry more search weight than a paragraph labeled Core Competencies.

Early-career candidates can mirror posting verbs inside internship and project bullets the same way tenured hires mirror them under a full-time title. The scale is smaller; the honesty rule is identical.

Career changers should translate old nouns into new ones only when the work is truly the same. Teacher to instructional designer is a fair swap when modules replaced lesson plans. It is not fair when you never built e-learning assets.

How to write a job description for a resume from the posting

Work on one priority req tonight. Twenty focused minutes beats another generic export sent to forty portals.

Pull phrases, not paragraphs

1. Highlight must-have tools, title variants, and verbs that repeat in the posting.
2. Open your master resume and list proof that already matches each highlight.
3. Rewrite bullets one and two under your current job so one must-have lands in the first eight words.
4. Reorder older roles only when the req cares about depth, not when you are padding history.
5. Export and confirm Experience still parses as plain text before you attach the file.

Copy-paste mapping (read each line before you edit):

{`Posting line: "Own pipeline hygiene in Salesforce; partner with RevOps on forecast accuracy."
Your proof: Managed 280-opportunity SMB book in Salesforce; cut stale-stage deals 19% in two quarters with RevOps.
Posting line: "Write customer-facing release notes and internal runbooks."
Your proof: Published 36 release notes in Confluence; reduced support escalations on new features 14% over six months.`}
            

I've screened stacks of these in Workday and Greenhouse, and the file that moves is boring on layout but specific on bullet one: tool, scope, and a number you can explain without reading the posting back to me.

Before: Bullet one says responsible for pipeline management.
After: Bullet one names Salesforce, book size, and a pipeline metric tied to a quarter.

Before: You add Snowflake because the posting mentions it once.
After: You add Snowflake only if you queried models or built dashboards there last year.

Keep each bullet to one or two lines on standard margins. If you need two metrics, split the line instead of writing a paragraph recruiters will skip on a phone screen.

Duty language from your old HR write-up is a starting draft, not the finish line. Translate assigned tasks into outcomes, then swap nouns to match the req. See how to tailor resume bullets to the job description without lying when you are tempted to invent scope.

Stuffing habits that fail screens

• Pasting full sentences from the employer posting into your summary.
• Repeating every acronym from the req in a Skills list with no bullet proof.
• Using the exact posting title as your resume headline when your official title differed.
• Swapping employer names but keeping the same six bullets for every application.
• Adding soft-skill adjectives the posting uses without a result behind them.

Stuffing feels like progress because the Word doc suddenly matches the posting highlight color. Mirroring is slower because you have to locate real proof first.

Before: You optimize for keyword density and hide weak bullets at line five.
After: You optimize for bullet order and accept that some reqs are not worth a rewrite.

When every bullet still reads like a duty stack, read why listing duties does not work anymore before you mirror more adjectives into the same shape.

Score match before you mass-apply

Run the export you will attach. Fix Experience wording before you chase another synonym swap.

Score your job match on the posting plus your current file. Missing tools you truly have belong in bullets, not only in a list at the bottom.

Run the free ATS check and read extracted text for your latest role. If bullet one truncates inside a table cell, mirroring will not matter until layout is plain again.

When the req also asks for a letter, draft after bullets pass. Use the cover letter generator for a plain file, then customize the opening line with one mirrored noun from the posting.

If you're rebuilding from a broken template, build your resume in a single-column layout so mirrored terms stay inside plain Experience bullets instead of text boxes.

Pick mirroring when you can tell the story

How to write a job description for a resume, in one rule: each employer block shows proof, and the posting only supplies the vocabulary layer on top of proof you already own.

Choose stuffing when you are optimizing for a feeling. Choose mirroring when you can explain bullet one for sixty seconds without opening the req. If you cannot, skip the tool name and keep the honest scope.

Job searching is draining enough without turning your Experience section into a highlight reel of someone else's wish list. You're making the match readable, not cloning the posting.