Writing Job Descriptions and Screening Notes With Copilot

The job description for a role you've hired for six times before still takes an hour to write, because the last one is buried in an old email thread, half the requirements have quietly changed, and "quick edit" always turns into a rewrite. Copilot is a genuine time-saver for this specific kind of task: turning a rough set of requirements into a structured draft, and turning a stack of resumes into organized screening notes. It is not a hiring decision-maker, and treating it like one is where this goes wrong. The Beginner's Guide to Copilot covers the general fundamentals; this article stays specific to the hiring-adjacent writing work.

Writing the job description: give it the boring details first

A job description written from a one-line prompt ("write a job description for a marketing manager") comes back generic in the exact way every other generic job posting is generic. The requirements that separate your actual open role from a template are the details you'd normally have to explain to a new recruiter: reporting line, the specific tools the person will touch daily, what "senior" means on your team versus the title's usual meaning elsewhere.

The gap between a lazy prompt and a specific one shows up directly in the opening paragraph a candidate reads first:

Bad prompt: "Write a job description for a marketing manager."

That produces something like: "We're looking for a rockstar Marketing Manager to join our team and wear many hats in a fast-paced environment. The ideal candidate is a self-starter who thrives in ambiguity and is passionate about marketing. Responsibilities include managing campaigns, collaborating with stakeholders, and driving results."

Better prompt: "Write a job description for a Marketing Manager who reports to the VP of Marketing, manages one direct report, and owns our email and paid social calendar."

That's closer, but it still reads like a list of facts rather than a role: "We're hiring a Marketing Manager to own our email and paid social calendar. You'll manage one direct report and report to the VP of Marketing. We're looking for someone with B2B marketing experience who's comfortable working independently."

Excellent prompt: the full version below, with the reporting line, the actual tools, the must-have versus nice-to-have split, and an explicit ban on cliches.

The instruction to avoid specific generic phrases is doing real work in that prompt. Without it, Copilot defaults to the same handful of job-posting cliches everyone else's postings already use, which do nothing to help a good candidate self-select in or a mismatched one self-select out.

Turning a stack of resumes into screening notes

This is the part of hiring Copilot can genuinely compress, and also the part where it's easiest to over-trust it. Copilot in Word can help you build structured notes for each candidate against the criteria you set, but it should never be the thing that decides who advances.

Here's what that looks like against a real, invented resume excerpt for the Marketing Manager role above:

Jordan Alvarez. Senior Marketing Associate, Fenwick Retail Group, 2021 to present: ran quarterly campaigns for B2B retail accounts, briefed freelance designers on creative assets, some exposure to Marketo for email automation. Prior: Retail Associate, Boru Coffee Co., 2019 to 2021. B.A. Communications, State University, 2019.

Run against Jordan's excerpt, that produces something like this, organized rather than scored:

The instruction not to rate or score the candidate is deliberate. Asking Copilot to score candidates pushes it toward making a judgment call from incomplete information, in a process where the input (a resume) is a poor proxy for the thing you actually care about (how someone will perform in the role). Asking it to organize facts against your criteria keeps the actual evaluation with you, where it belongs, and gives you a consistent format to compare candidates against each other quickly. The "exact scope isn't stated" line matters as much as the facts around it: it turns a silent gap in the resume into something the interviewer knows to ask about, instead of an assumption in either direction that nobody actually checked.

Screening notes that hold up if someone asks why

A useful screening note format documents what you found and why it matters, so that six weeks later when someone asks why a candidate did or didn't advance, the note actually answers the question instead of just restating a vibe.

Applied to Jordan's summary from above, the finished note looks like this:

That last row is why this format holds up later: it doesn't say Jordan lacks management experience, it says the resume didn't address it, which is the accurate claim and the one that survives a follow-up question six weeks from now.

Where a human has to take over

Copilot can't interview anyone, can't read tone or evasiveness in a phone screen, and shouldn't be the final word on whether a candidate's experience is "close enough" to what's required. It's also a poor fit for anything touching legally sensitive language, like accommodations, leave policy, or termination documentation, where the exact wording carries real consequences and should go through whatever legal or compliance review your organization already has in place. Use it to compress the drafting and organizing work, and keep the actual judgment calls, and anything with legal weight, with a person.