Why Hiring Is Still Broken - And What Sixteen Years of Building Teams Taught Me About It
Authored by: Mrityunjaya Prajapati
The most expensive hiring mistake I ever made had nothing to do with a bad interview. The candidate was sharp, well-spoken, and came with credentials that looked exactly right on paper. Three weeks into the role, the gaps became visible. The certifications were real. The competency they were supposed to represent wasn't.
That experience wasn't unusual. Over sixteen years of building companies - across digital payments, Web3 infrastructure, and now credential technology - I've hired close to eighty people across India, the UAE, and Africa. And the version of that story, where someone's documented qualifications and their actual working capability don't match, has repeated itself more times than I'd like to count. It's not a candidate integrity problem, though that's part of it. It's a systemic information problem. The hiring process, in most organizations, is built on credentials that were never designed to be verified at speed or at scale.
The document problem nobody talks about
When you're hiring across multiple geographies simultaneously - which became normal for us as we scaled - the credential verification burden multiplies quickly. A degree from a university in Madhya Pradesh, a certification from a training institute in Dubai, a portfolio of Web3 project contributions from a developer in Lagos. Each one requires a different verification path. Most of the time, under hiring pressure, the verification either doesn't happen thoroughly or takes long enough that the candidate has already accepted another offer.
So what actually happens in practice? Hiring managers develop proxy signals. Years of experience. Names of previous employers. The quality of how someone talks about their own work. These are reasonable proxies. They're also easy to game, and they consistently disadvantage candidates who have genuine competency but weaker institutional backgrounds - first-generation professionals, people from tier-2 and tier-3 cities, workers from the informal sector who built real skills outside formal credentialing systems.
In my experience, some of the strongest hires I've made came from backgrounds that wouldn't have passed an automated credential screen. And some of the most disappointing ones had credentials that looked impeccable.
The problem is that the hiring process is optimizing for the wrong signal.
What building a developer community of 20,000 taught me about talent
When we were growing our Web3 developer community, the traditional hiring playbook didn't apply. There were no established degree programs for the skills we needed. The certifications that existed were months behind where the technology actually was. Job boards returned candidates who had learned the right vocabulary without having done the real work.
What we shifted to was a contribution-based assessment. Can you build something? Can you solve a specific problem? Can you articulate why a particular architectural decision makes sense for this use case? The evaluation moved from what someone claimed to have done toward what they could demonstrably do in front of us.
This sounds obvious. It's surprisingly rare in practice, especially in organizations that have scaled enough to have formalized hiring processes. Formalization tends to push companies back toward credential screening because it's faster and easier to administer than competency evaluation at volume.
The tension between speed and quality in hiring is real. But the solution most companies reach for - faster credential screening - solves the speed problem while making the quality problem worse.
The specific mistakes I've watched companies make
Hiring under pressure is where the most expensive decisions happen. When a team is stretched, when a client deadline is approaching, when the previous person in the role has already left - the instinct is to move fast and verify less. That trade-off almost always costs more than the delay it avoided.
The second mistake is treating onboarding as the place where hiring errors get corrected. Onboarding is not a remediation tool. By the time a competency gap becomes visible during onboarding, the organization has already invested in recruitment, selection, and the first weeks of employment. The correction should happen at the assessment stage, not afterward.
The third mistake is geographic bias in hiring standards. When teams are distributed across multiple countries - as mine have been - there's a tendency to apply different rigor to candidates depending on where they're based. The candidate in a major metro gets a structured technical assessment. The candidate in a smaller market gets an informal conversation. The result is a team where qualifications are inconsistently evaluated, and actual capability distribution becomes difficult to understand.
Standardizing the assessment process across geographies is harder than it sounds, particularly when the skills themselves aren't well-represented in formal credentialing systems in every market. But it's the only way to build a team where the hiring process is actually generating useful information rather than just confirming existing biases about where talent comes from.
Why verification needs to happen before the interview, not after the offer
The conventional sequence in most hiring processes is: screen applications, interview candidates, select a finalist, then verify credentials before the offer is finalized. That sequence is backwards in terms of where verification actually adds value.
By the time an organization reaches the offer stage, they've already invested significant time in a candidate. The psychological pressure to complete the hire is real. Credential verification at that stage functions more as a formality than a genuine filter, and discrepancies that would have eliminated a candidate earlier in the process get rationalized or overlooked.
Moving verification earlier - making credential legitimacy a pre-screening condition rather than a post-selection checkpoint - changes the quality of the candidate pool that reaches the interview stage and reduces the pressure to rationalize problems late in the process.
The practical barrier to doing this has always been speed. Manual verification takes time. Verification services add cost and lag. And for skills that aren't represented in traditional credentialing systems, there often isn't a reliable verification path at all.
This is the gap we're working on closing with Skill Passport - building the infrastructure layer that makes credential verification near-instant and makes skill identity portable and tamper-proof for workers across formal and informal sectors. The vision is straightforward: a hiring manager should be able to understand a candidate's verified competency profile before the first conversation, not after the final one.
What actually changes hiring outcomes
Three things, based on what's worked across the companies I've built:
Assess what the role actually requires, not what looks good on a job description. Most job descriptions are wish lists assembled by committee. The actual day-one requirements of the role are usually narrower and more specific. Hiring against the actual requirements changes who you're looking for.
Separate competency evaluation from credential review. They're measuring different things. A credential tells you what someone was assessed to know at a point in time. A competency evaluation tells you what they can do now. Both matter. Neither is sufficient on its own.
Build verification into the beginning of the process, not the end. The later the verification happens, the less useful it is. The earlier it happens, the more it shapes who reaches your interview stage.
The hiring process, as most organizations run it today, generates a surprisingly small amount of reliable information about candidates. Fixing that is less about better interviewing techniques and more about building a better information infrastructure around the entire process.
Sixteen years of getting this wrong in various ways has made me fairly certain of that.
Author Bio: Mrityunjaya Prajapati, widely known as Jay, is the Founder and Architect of Skill Passport, a blockchain and AI-powered credential infrastructure platform building verifiable skill identity for workers, institutions, and employers across India and globally.