Glossary
Hiring Bar
The minimum standard of skills, experience, and fit required to hire someone.
By Amit Tyagi, Fitoor Capital · AletheiaAI Glossary
Definition
A hiring bar is the explicit or implicit threshold a company sets for evaluating candidates. It covers technical ability, problem-solving, cultural alignment, and execution speed. Meeting the bar means getting hired; falling short means rejection, regardless of other strengths.
Why it matters: Early-stage startups live or die by team quality. One bad hire at a 10-person company reduces productivity by 10%, drains management bandwidth, and delays product-market fit. A high bar prevents this. It also compounds: strong founders hire strong people; weak founders hire weaker people.
The bar should be documented and applied consistently across roles. For a Series A fintech startup in India, this might mean: 5+ years fintech or payments experience, shipped 2+ products, can code or design independently, understands Indian regulatory context (RBI, NPCI rules). A high bar isn't elitist—it's pragmatic. Early-stage runway is finite.
India Context
India's tech talent market is fragmented. Urban tech hubs (Bangalore, NCR, Mumbai) have deep supply of engineers from tier-1 colleges and startups. But outside these pockets, talent is thinner and often lower-quality by default. This creates a temptation for founders to lower the bar due to scarcity. Many do—and regret it.
Indian labor law adds friction: probation is typically 3–6 months, but wrongful termination claims are common and expensive. Once someone is hired beyond probation, removing them legally requires documentation and is time-intensive. This makes hiring a semi-permanent decision, raising the stakes for getting it right. Founders often hire faster than they should, then struggle to course-correct.
Benchmark: Strong Indian early-stage tech teams aim for IIT/IIIT or 3+ years of startup experience for engineers. For product and business roles, candidates should show track record of scaling—user growth, revenue, or operating metrics—not just job titles.
Example
Razorpay's hiring approach (2014–2016): Harshil Mathur and Shashank Kumar, while building the payments platform, hired only engineers who had shipped products or worked at high-growth startups. They rejected many candidates from large IT services firms even if technically sound, because those hires wouldn't move fast enough in a 5-person team. This high bar slowed hiring but created a compact, execution-focused team. By Series B, Razorpay's engineering productivity was 2–3x peers in the cohort.
The tradeoff: It took them longer to scale to 20 engineers than competitors who hired faster. But quality compounded, and they needed fewer management layers to course-correct.
Frequently Asked Questions
Related Terms
Apply what you've learned
See this term at work on real Indian companies.
AletheiaAI checks market narratives against the filings behind them — screener, company disclosures, and sector reports across India’s listed companies, free.