How to Write a Job Description Based on the Job to Be Done in 2026?

[DelDallas]

The best way to write a job description using the "Job to Be Done" (JTBD) framework is to start by identifying the core outcome the new hire needs to achieve, not the list of skills they should have. Most traditional job ads focus on a wishlist of qualifications, which leads to generic applications and misaligned hires. JTBD shifts the focus to the emotional and functional progress the candidate will help the team make.

For example, instead of writing "We need a Senior Software Engineer with 5 years of Java experience," you write: "We need someone who will reduce our software deployment time from 4 hours to 15 minutes." This immediately attracts candidates who are motivated by that specific challenge, not just a paycheck.

To implement this, follow a three-step process. First, interview your current top performers to understand what "job" they were hired to do. Second, strip away all the "nice-to-have" skills and focus on the single most important outcome the role must deliver in the first 90 days. Third, write the job description as a story of progress, using language that describes the struggle the candidate will solve.

Here is a clear comparison of how a traditional job description differs from a JTBD-focused one:

Aspect	Traditional Job Description	Job to Be Done (JTBD) Description
Title	Senior Marketing Manager	Marketing Manager to Drive 20% Pipeline Growth
Focus	Skills: SEO, Google Ads, content creation	Outcome: Increase qualified leads by 30% in 6 months
Example Line	"Must have 5 years of B2B experience."	"Help our sales team stop chasing cold leads by building a referral engine that generates 50 warm intros per month."
Candidate Appeal	Attracts "checklist" applicants	Attracts problem-solvers and motivated individuals

Remember, the goal is to sell the progress, not the position. When you write a job description this way, you naturally filter for candidates who are driven by purpose and results, which dramatically improves your talent retention rate and reduces the time spent on candidate screening.

[Joanna]

I always start by asking the hiring manager one question: "What is the one thing that must get better in your team in the next six months?" If they say "customer response time," then every line of the job ad should show how the new person will own that timeline. I skip the generic "team player" clichés and write bullet points like "You will own the ticket queue and bring our average response time under 2 hours." It makes the job feel real, not like a list of chores.

[FernandoMarie]

As someone who reads dozens of job ads every week, the ones that grab me are the ones that describe a problem I actually want to solve. If you write a job to be done, you tell me that my first month will be spent fixing a broken onboarding process, not just attending meetings. That honesty is rare. It makes me feel like the company knows what they need, and that I can make a real difference from day one. I apply to those roles immediately.

[DeJuliette]

The biggest mistake I see is writing a job description that sounds like a legal compliance document instead of a call to action. A JTBD approach forces you to define the "before" and "after" state of the hire. For example, before: "Our sales team is losing deals because proposals take 3 days to create." After: "You will cut proposal creation time to 4 hours." If you cannot define that gap, you are not ready to hire. That clarity saves everyone time and money.

[DelKendra]

From a team perspective, writing a job to be done helps avoid hiring clones. When I write a traditional JD, I copy my own skills. When I write a JTBD JD, I look at the team's current gaps. For instance, we are great at building features but terrible at documentation. So the job is not "find a JavaScript developer." It is "find someone who will make our documentation so clear that new engineers can ship code on day one." That attracts a different type of person, and it balances the team perfectly.