Founder's Dharma

The First Hire That Changed How I Hire Everyone Else

MR
Mrinal Rai
5 min read

The Cost of a Resume-First Mentality

When you are grinding out of a small office in Bengaluru, your first few hires feel like oxygen. You are drowning in Jira tickets, client emails, and cold calls. You just need hands. You need bodies that can execute. My initial instinct was to hire for pedigree—the big names, the flashy projects, the safe bets that look good on a Series A pitch deck.

I was wrong. I hired a brilliant engineer once who had all the right credentials. He was technically elite, but he looked at a broken supply chain integration as a math problem to be solved in a silo, not a operational failure impacting a client's bottom line. He spent two weeks optimizing code that didn't need optimization, while our server was down for a warehouse client in Bhiwandi. That was when I realized that in B2B SaaS, your first hires are not just employees; they are the cultural architects of your company.

The Pivot: Hiring for 'Systemic Empathy'

My approach changed when I hired someone who didn't have the standard 'hot' startup resume. They had spent three years working on the ground in logistics, dealing with truck drivers, gate passes, and the chaotic reality of Indian trucking. They knew what 'real-time visibility' actually meant when you are standing in a dusty yard at 2 AM.

This person didn't just write code; they understood the friction of the product. They taught me that the best hires are those who possess 'systemic empathy'—the ability to see the connection between a line of SQL and the physical movement of a truck on a highway. Once I started hiring for this, the quality of our engineering team shifted overnight. We stopped building features that looked good on a demo and started building products that actually solved operational pain.

Your first ten hires don't just work for you; they define the threshold of talent for every person you hire thereafter.

The Ripple Effect

There is a dangerous gravitational pull in early-stage startups. If you hire someone who is just 'okay' because you are in a rush, they will inevitably hire people who are slightly worse than them. It is the regression to the mean. Conversely, when you hire someone exceptional who cares deeply about the user's problem, they act as a force field. They refuse to work with anyone who lowers the standard.

  • Stop checking for keywords: Look for how they approach a complex, ambiguous problem with no clear documentation.
  • Test for ownership: I ask candidates to walk me through a time they broke something and how they handled the fallout. The ones who hide behind 'it was a team error' are a pass. The ones who take the blame are the ones I want to build with.
  • Culture is what you tolerate: If you hire a brilliant jerk, you have told your team that brilliance is an excuse for bad behavior. That is a debt you will pay for years.

Recruiting is the most important product you will ever build. Treat it with the same rigor you apply to your codebase. If you get the DNA right early, the company grows into a beast. If you compromise on the first few, you will spend your entire time as a founder cleaning up the mess of your own hiring mistakes. Hire slow, hire for depth, and always, always hire for the long-term integrity of the product.

hiringstartup-growthleadershipb2b-saasscheduled30
Join the Chronicle
Get essays, reflections, and builder wisdom — delivered rarely, crafted carefully.
Continue Reading