I’ve been applying the Jobs to Be Done (JTBD) framework in recruitment for years, and honestly, it’s a game‑changer for understanding what truly drives a candidate’s decision. At its core, JTBD asks: What job is the candidate hiring a company to do? It’s not about the role’s title or salary alone—it’s about the progress they want to make in their career or life. For example, a senior engineer might “hire” a startup to gain autonomy, while a mid‑level manager might “hire” a corporate role for stability and mentorship.
In practice, I start by mapping out the functional, emotional, and social jobs behind a hire. Functional jobs are obvious (e.g., “earn ₹15L+ per year”), but emotional ones—like “feel respected” or “avoid Monday dread”—often matter more. Social jobs involve how others perceive the candidate (e.g., “be seen as a thought leader”).
To make this concrete, I often compare traditional hiring with a JTBD‑informed approach:
| Aspect | Traditional Hiring | JTBD‑Informed Hiring |
|---|
| Focus | Skills & experience | Progress & motivation |
| Interview question | “What did you do?” | “What problem were you trying to solve?” |
| Candidate fit | Keyword match | Emotional & social alignment |
| Retention driver | Compensation | Purpose & growth |
The framework forces me to dig deeper. Instead of asking “Why do you want this job?”, I ask “What’s the job you’re trying to get done in your career right now, and how does this role help you do it?” That shift alone has improved my offer acceptance rates by over 30% in the past two years. The key is to listen for the progress they’re seeking, not just the responsibilities they list.
A word of caution: JTBD isn’t a quick fix. It requires empathy, structured interviews, and a willingness to challenge assumptions. But when done right, it helps you attract candidates who stay because the role genuinely fulfills their deeper needs.
