Job descriptions can cost hires—rewrite before screening

Rewrite job – A hiring manager spent three weeks screening candidates for a digital marketing role, made an offer, and learned two months later the hire didn’t match what the business actually needed. The gap wasn’t performance—it was the job description itself, written for

For three weeks, a hiring manager worked through strong résumés and solid interviews for a digital marketing role. The process moved quickly enough that an offer went out, and the candidate accepted. Two months later, she called. “They’re great, but they’re not what we actually needed.”

The disconnect was immediate, and it wasn’t about talent. What the business needed was someone to rebuild a broken attribution model and realign paid media spend with a new revenue target. What the job description asked for. though. was someone to “manage campaigns across Google and Meta.” On paper and on day one. the role were two different jobs.

That story isn’t unusual. It happens across every function and level: job descriptions end up describing a role that existed. not the one a business actually needs now. By the time a position gets approved, circulated, and posted, the organization has already moved. The result is hiring for last quarter’s problems while today’s challenges go unaddressed—and the best candidates usually recognize it.

About a quarter of job seekers already say job descriptions are misleading or have unreasonable requirements. For them, it’s not just a perception issue. It’s a design problem.

The fix has to start before anyone even opens a search.

Start by defining the role before describing it. Most job descriptions begin with the wrong reference point—last year’s version of the role. a competitor’s post. or a platform wish list. A better starting question is what business problem the person will own in the next 12 to 18 months. not just what tasks they’ll handle. “Fix declining organic traffic” is a business problem. “Manage SEO” is a task. One points candidates toward outcomes; the other rewards checkbox work.

That clarity should also separate what the person will inherit from what they’ll have to build from scratch. A candidate who thrives with structure can struggle in ambiguity, and the reverse is also true. If the starting line includes no existing strategy. no clean data. and no defined process. that needs to appear in the job description—not be revealed only after the third interview.

Ownership level matters just as much. Many job posts describe senior-level responsibility with coordinator-level authority. If the person will need to align with three other departments. navigate competing priorities. and influence without direct control. say so. Candidates who need clean lanes will self-select out. Candidates who are built for that reality will lean in.

Then rewrite the job description around outcomes. The most common pattern. especially in digital marketing. is posts that list nearly every platform in the tech stack while saying almost nothing about what success looks like. The implicit message becomes tool familiarity; the actual need becomes problem-solving.

A practical shift is to swap platform requirements for outcome expectations. Instead of “3+ years of experience in HubSpot. ” a post can call for “Experience building or inheriting a CRM workflow and improving lead-to-close conversion.” Instead of “Proficiency in Google Ads. ” it can ask for “Proven ability to diagnose underperforming paid campaigns and reallocate budget toward higher-return channels.” The point is not to remove technical depth—it’s to surface candidates who think about the work the way the company needs them to.

Outcomes also expose when a job description is quietly asking for three roles in one. If you stack outcome after outcome that spans strategy, execution, and analytics with equal weight, you may be describing a team, not a single hire.

Finally, design the interview to simulate the actual job. A typical interview tests what someone knows. It often fails to show how they’ll operate when priorities conflict, data is messy, or the path forward is unclear—conditions that are “most of the time.”

In digital marketing searches, the strongest signal can come from realistic case studies. Give candidates a scenario that mirrors a challenge the team is facing. Ask them to prioritize it, identify what questions they need answered, and explain where they’d start.

The questions that matter dig into how people think, not just what they’ve memorized. “Tell me about a time the data told you one thing and your gut told you another. What did you do?” and “Walk me through a campaign or project that failed. What did you learn, and what would you change?” aren’t tricks. They mirror the situations a new hire will face in month two.

A lot of what sends top candidates walking comes down to structural signals. When every interviewer describes the role differently, it’s a sign the team doesn’t have internal alignment. If leadership can’t articulate the priorities. a high performer reads that as a lack of a clear path to success. And when the interview focuses entirely on platform experience—without any real questions about business outcomes—it signals the company values task completion over strategic thinking. Growth-oriented candidates don’t want to inherit that kind of mismatch.

The candidates leaving aren’t being difficult. They’re protecting themselves. They know that ambiguity at the hiring stage often becomes ambiguity on the job—and that makes it very hard to win.

If a company wants to attract and keep great people, the hiring process has to reflect the clarity the person will need to succeed. That clarity has to begin the moment the candidate reads the job post.

job descriptions hiring recruiting digital marketing attribution model paid media Google and Meta revenue targets candidate experience HR interview design