Skills-Based Hiring vs Experience-Based Hiring: What Indian Startups Are Getting Wrong

Ask any Head of Talent at an Indian Series B startup how they filter candidates for a senior hire, and the honest answer usually involves some version of the same shortlist: IIT or IIM on the CV, five-plus years at a recognisable company, and maybe a particular employer logo that signals "they survived a high-performance culture." These signals get applied quickly, feel defensible in a debrief, and have a long track record of social acceptability in Indian professional circles.

The problem is that none of them reliably predict whether someone will perform well in the specific role you're hiring for. They predict that someone was good at getting into competitive institutions and good at getting hired by well-known companies. Those are real achievements. But they are proxies — and at startup speed, where the job itself is still being defined, proxies are expensive.

---

What Experience-Based Hiring Actually Is (And Why It Feels Safe)

Experience-based hiring uses past inputs — titles held, companies worked at, years in a domain, degrees earned — as the primary signal for future performance. It's intuitive because it's pattern-matching: if someone has done something similar before, they'll probably do it again.

The heuristic works reasonably well in stable, well-defined jobs where the role at Company A is genuinely similar to the role at Company B. It breaks down badly in startup contexts, where roles are ambiguous, scope changes frequently, and the gap between "performed well in a structured environment" and "can operate with no playbook" is enormous.

Pedigree signals are especially unreliable at the startup stage for two reasons. First, they compress a lot of irrelevant information — how good someone was at cracking competitive exams at age 18 tells you very little about their judgment at 32. Second, they systematically exclude people who took non-linear paths, came from tier-2 cities, or built real skills at companies without famous logos — which, in India, is a very large pool of capable people.

---

What Skills-Based Hiring Actually Means

Skills-based hiring evaluates candidates on demonstrated ability to do the tasks the role actually requires — not on proxies for past success in adjacent situations.

This sounds obvious. In practice, most teams don't do it, because it requires more upfront work: you have to define what the role actually demands before you design any evaluation. That's harder than skimming for resume signals, which is why the default persists.

Here's where experience-based hiring visibly fails in a startup context:

The 8-year veteran who can't operate without structure. A candidate with eight years at a large consumer company, managing a regional P&L with a full team beneath them, joins a Series B as Head of Growth. The brand name was right. The title was right. Six months in, they're drowning — because the role requires building from scratch, not managing an inherited machine. The experience was real. The skills required for this role weren't what the experience demonstrated.

The 2-year candidate who outperforms expectations. A candidate with two years of experience, no tier-1 college tag, but specific, demonstrable skills — building and iterating growth loops, writing SQL to pull their own data, running experiments without hand-holding — joins the same startup in a parallel role. They ramp in three weeks and ship independently within a month.

The resume filter that eliminates the second candidate before they're ever seen. This is the actual cost of pedigree-first screening. It's not just that you hire the wrong person — it's that you never evaluate the right one.

---

The Business Case for Doing It Differently

The argument for skills-based hiring isn't ideological. It's operational.

Faster time-to-hire. When you know exactly what 8-10 skills you're hiring for, you can run a focused assessment early in the funnel instead of three rounds of subjective interviews designed to intuitively confirm a gut feeling. The structured assessment gives you a comparable, objective data point across candidates. You still do interviews — but they're shorter, more purposeful, and you enter them already knowing the candidate can do the work.

More accurate signal. A resume tells you what someone has done. An assessment tells you what they can do — right now, in conditions similar to the actual job. These are different things. Someone who managed a team for five years at a large company may not be able to write a coherent growth strategy brief under a 90-minute constraint. Someone with two years who can demonstrates something more relevant to the role.

A wider, fairer candidate pool. This is under-discussed in Indian hiring conversations, but it matters. Skills-based screening removes the first-filter bias toward urban, tier-1-college candidates who've had more access to well-known employers. It opens the funnel to people who built real capability in less visible environments. For a startup competing for talent against better-funded companies, this is a material advantage — you get access to candidates your competitors are filtering out.

---

Where Skills-Based Hiring Has Real Limits

A skills-based assessment tells you a lot. It doesn't tell you everything, and it's worth being honest about that.

It doesn't fully capture culture fit or working style. Whether someone will collaborate well with your specific team, handle conflict constructively, or thrive in your particular founder dynamic — these things are hard to assess in a structured test and still require a good interview.

It doesn't predict leadership potential or judgment under ambiguity. For senior roles where the biggest demands are making calls with incomplete information and earning followership from a team, a skills test is a necessary condition, not a sufficient one. Use it to filter, not to decide.

It works best when the role is well-defined enough to map to specific skills. If the role is genuinely ambiguous — "we'll figure it out with the right person" — you need to do the hard work of defining what "right" means before any assessment is useful. Skipping role definition and jumping straight to a test produces a bad test.

The practical conclusion: skills-based assessment should be one input in a structured hiring process, not the whole process. It replaces the resume screen, not the interview.

---

How to Start (Without Overcomplicating It)

The simplest version of skills-based hiring looks like this: before you open a role, write down 8-10 specific things the person will need to be able to do in their first 90 days. Not traits. Not values. Specific tasks.

If you're hiring a growth analyst, the list might include: can independently query and interpret data to identify a trend, can write a concise brief a PM can act on, can design and size an experiment before running it. That list becomes your assessment design brief.

If you're not sure where to start with mapping a role to skills, there's a low-friction way to test the approach: the skills search on the Dextes homepage lets you type any role name and instantly returns 10-12 relevant skills to assess — no signup required. It's not a replacement for the thinking, but it's a useful starting point when you're looking at a blank page. Adapt what comes back to your specific context, remove what doesn't apply, add what's missing.

From there, the path to a structured assessment is shorter than most teams expect. The hard part is doing the role definition — once you have that, building the test is mechanical.

---

The Honest Conclusion

Skills-based hiring isn't a trend that's going to peak and fade. It's the direction the market is moving, driven by the simple reality that pedigree signals are becoming less informative as the pool of experienced candidates homogenises and competition for talent increases.

For Indian startups specifically — where hiring speed matters, brand-name employer budgets are limited, and the gap between metro and non-metro talent is real — the shift to skills-based evaluation is both strategically sound and practically accessible. It's not a major investment. It's a process change.

The teams that make that change now are building a more accurate, faster, and fairer hiring machine than the ones still skimming for IIT tags. That compounding advantage shows up in quality of hire, in ramp time, and eventually in team performance.

If you want to see what a structured, skills-based assessment looks like in practice — Dextes is free to start. Build one for a live role this week and see what the data looks like compared to what you'd have inferred from the resume.