
Jobs Theory, also known as the Jobs to Be Done (JTBD) framework, is a powerful lens for understanding why people “hire” a product, service, or even a job. In a recruitment context, it shifts the focus from traditional job descriptions and candidate profiles to the underlying progress a person is trying to make in their career at a specific moment. When I apply this theory to hiring, I stop asking “What skills does this candidate have?” and instead ask “What job is this candidate trying to get done by taking a new role?” For example, a senior engineer might not be looking for a better salary; they might be trying to achieve autonomy to lead a project or escape a toxic company culture. The same goes for employers: the “job” they need done isn’t just filling a vacancy—it’s solving a business problem like reducing time-to-market or improving team morale.
Here’s a quick comparison of how traditional hiring and JTBD-based hiring differ in practice:
| Aspect | Traditional Hiring | Jobs Theory Hiring |
|---|---|---|
| Focus | Skills, experience, education | The progress the candidate wants to make |
| Job description | List of duties and requirements | Statement of the “job” the role will help accomplish |
| Candidate screening | Resume keywords, years of experience | Behavioral questions about career milestones |
| Employer branding | Company perks, culture | Stories of how the company helps people achieve their goals |
| Retention strategy | Salary adjustments, benefits | Continuous alignment with employees’ evolving “jobs” |
Using this framework, I’ve seen hiring teams cut time-to-fill by 30% and improve retention rates because candidates are matched on deeper motivations. The key is to uncover the emotional and functional drivers behind a job change. For instance, a candidate may say they want a “better work-life balance,” but the real job to be done might be “I need to be present for my child’s school events without guilt.” When you address that specific job, you create a much stronger offer.

I’m a job seeker who discovered Jobs Theory last year, and it completely changed how I evaluate offers. Instead of just looking at salary and title, I now ask myself: What progress am I really trying to make? For me, it was about gaining more control over my schedule so I could start a side project. That helped me turn down a high-paying role that demanded long hours and accept a lower-paying one with flexible hours. The framework made my decision clearer and more confident—no more second-guessing.

As someone who designs job descriptions for a large company, I now use Jobs Theory to craft candidate-centric postings. I start by identifying the “job” a top performer would want to get done—like mastering a new skill or leading a cross-functional team. Then I write the job description around that progress, not just a list of tasks. The result? Applicant quality improved noticeably because the descriptions attract people who are intrinsically motivated by the role, not just anyone scanning for keywords.

In my coaching conversations, I guide clients to apply Jobs Theory to their own career. I ask them to map out their last two job changes and identify the real progress they were trying to make—not just the title or salary. Usually, it’s something like “I wanted to feel valued” or “I needed to work on projects that mattered.” Once they see that pattern, they can target companies that offer that specific progress. It’s a practical tool that cuts through the noise of generic career advice.

When I’m hiring for my team, I use Jobs Theory to understand why people stay or leave. I hold informal “exit interviews” with current high performers to learn what job they’re getting done by staying. For example, one developer told me they stayed because they got to mentor junior engineers—that was their unspoken job. Now I build that into role design and retention conversations. It’s helped me reduce voluntary turnover by 20% in one year, simply by aligning the work with the progress people actually want.


