
Writing a Jobs to Be Done (JTBD) framework for recruitment is about shifting your focus from what a candidate is to what they want to accomplish. Instead of listing a static wishlist of skills, you outline the core progress a candidate aims to make in their career by taking on your role. The very first step is to identify the functional, emotional, and social jobs the role fulfills. For example, a candidate isn't just "looking for a job"; they are "hiring" a position to achieve career stability, gain mastery over a new technology, or reduce their commute time.
To write this effectively, start by deconstructing the hiring manager's actual business problem. Ask: What is the specific struggle our team faces that this person will solve? Then, translate that into the candidate's language. Use a structured format:
A strong JTBD statement avoids buzzwords. Instead of "must be a team player," you write: "The candidate is hired to unblock a cross-functional team that has been stalled by misaligned priorities." The data backs this up. According to a 2025 LinkedIn Talent Solutions report, job descriptions that use a problem-centric narrative (focused on the specific job to be done) see a 42% higher application-to-screen conversion rate than traditional skill-based descriptions. Below is a comparison of the two approaches:
| Aspect | Traditional Job Description | Jobs to Be Done Description |
|---|---|---|
| Focus | Candidate's past skills and titles. | Candidate's future contribution and motivation. |
| Language | "3+ years of experience with Python." | "Your job is to automate our data pipeline so the team can ship features 2x faster." |
| Outcome | Attracts passive, checklist-based applicants. | Attracts proactive problem-solvers who see the role’s purpose. |
| Conversion Rate | Baseline. | +35-50% higher conversion (Source: LinkedIn Talent Insights, 2025). |
The key is to remove the friction from the candidate's decision-making process. By clearly stating the job to be done, you help them self-select, which drastically improves the quality of your candidate pool. This approach also forces managers to be honest about what the role actually entails, reducing early turnover.

I think the most practical way to write a Jobs to Be Done is to interview your top performers in the role first. Ask them what actual problem they solved when they started. Was it fixing a broken process? Teaching other teams a skill? I then write the description around that core struggle. For example, I wrote one recently that started with: "Our engineering team is drowning in technical debt. Your job is to untangle the mess and leave the codebase cleaner than you found it." It attracted a completely different type of applicant—people who actually enjoyed refactoring, not just building new features. It’s a simple shift, but it gets right to the point.

From my experience, the key is to ditch the "requirements" section and replace it with "the mission." I write a single sentence at the top of the posting that describes the primary job to be done. For a project manager, I wouldn't write "needs PMP certification." I'd write: "Your job is to keep a 10-person team from blowing the deadline on a Q3 product launch." That’s the functional job. It tells the candidate exactly what they are signing up for. It’s honest and it filters out people who might be qualified on paper but hate that kind of pressure.

I look at it from a career progression angle. The candidate is "hiring" a job to advance their career narrative. So I frame the Jobs to Be Done as a growth trajectory. For example, a mid-level engineer isn't just writing code; their job is to "learn how to lead a critical system design and get promoted to senior in 18 months." I write the description to highlight that emotional job: the desire for mastery and recognition. I include a bullet point like: "Your specific


