The Zelcast thesis

For years, founders would ask the people who back Zelcast the same question: who should I hire and how do I actually get them? Strong engineers would ask them the mirror of it: which of these companies is worth a bet?

Zelcast is backed by people who have founded companies, hired hundreds of engineers, and invested in a few hundred startups, and after enough years of that you know who is good on both sides. Their introductions turned into hires, and the hires into the best people at those companies. The reason is that operating teaches you what to look for.

All of it comes from doing it badly, and then less badly, at their own companies. A few things hold up over and over.

Engineering output follows a power law. The gap between a good engineer and a great one is not twenty percent. On the problems that decide whether a startup lives, it is closer to ten times, because the great ones choose the right problem before they solve it.

The first ten engineers set a ceiling. A-players recruit A-players. One mediocre early hire will lower the bar for every hire after and no one will notice until it’s expensive to fix. Talent density is the only startup advantage that compounds on its own.

Interviews are a mediocre signal at best. The strongest signal in hiring is a person who worked beside someone for two years and will stake their name on them.

The cost of a wrong hire is not symmetric. Google can absorb a thousand hiring mistakes a year without noticing. A twelve-person company that hires the wrong senior engineer loses a year, and most seed-stage companies don’t have one to spare.

Why the open market fails at the top

Job boards and application pipelines are a market for people who are looking. The best engineers mostly aren’t looking. They’re employed, paid well, and buried under messages they don’t read, so the open market systematically shows companies everyone except the people they want. We wrote about this selection effect on its own, but the short version is that a great applicant pool and the great engineers are two different populations.

Big-company signals miss the early-stage game

The deeper problem is that the recruiting industry learned its craft inside big companies, so it screens on big-company signals: the brand on the last job, the years in the title, keywords in the stack. Those work when the role is a well-specified lane inside a system that catches mistakes.

At an early-stage company they barely predict anything, because half the job is deciding what the job is.

The things that decide the outcome, what someone builds unprompted, how fast they move through ambiguity, whether the people around them get better, never appear on a resume, and a keyword screen won’t see them. A keyword can match a profile to a req, but judging whether a person can carry a company takes someone who has been inside one small enough to know.

AI breaks the volume model

The AI era makes this worse for the old model, because outreach is now free. Any recruiter can send ten thousand personalized messages before lunch, and none of them get read. Sourcing tools all pull from the same indexes, so everyone is looking at the same lists of the same people. Volume no longer buys anything. What still counts is knowing who is great and being someone both sides trust.

At the same time, AI has raised the stakes of every hire. A great engineer with today’s tools does work that took a small team five years ago, so the best companies are staying smaller, longer. That means fewer seats, and each hire carries a large share of the outcome.

Quality is the entire game

Recruiting is also built as a volume business: it’s measured in submittals per week and seats per quarter, and paid as a fee on fill. The math works because at scale hiring is statistical and a big company can afford to be a little wrong a thousand times. An early-stage company gets maybe ten swings, and every one of them is ten percent of the company. At that stage, fifty resumes distract from the one person who matters.

We run the opposite model: fewer introductions, each made with high conviction. We live with both sides of every one we make, which keeps us honest. We would rather show a founder one right person than twenty possible ones.

Relationships are the product

We get to know engineers before the right role exists: what they want to build, what they care about, what kind of founder they would follow, what would make them leave a good job. Most of the engineers we work with aren’t looking, and we aren’t trying to place them. We keep up the relationship so that when the right thing appears, we both recognize it in the first conversation.

We do the same on the other side. Before we put anyone in front of a company, we learn how the company works: what the founders believe, how decisions get made and what the culture rewards. At an early-stage company that context is almost the whole match. The same brilliant engineer is a great hire at one startup and a disaster at the next, and a JD won’t tell you which.

Why only startups under 100 people

We don’t work with Microsoft, Salesforce, Oracle, Google, or OpenAI. They’re fine companies that don’t need us. Past a certain size, hiring is a process problem of pipelines, panels, committees and calibration. Big companies are good at process and the market is full of firms that serve them.

For startups with under a hundred people, hiring is a judgment problem, and there’s no committee to average out a mistake. Every hire will visibly move the company’s ceiling, and the person has to be right on dimensions a pipeline won’t measure: how they handle ambiguity, whether they raise the bar around them, and whether a founder can build on them. That judgment comes from having sat in the seat and paid for the mistakes.

Why only the top 1%

Matching only means something when both sides are scarce. Most engineers can find a fine job and most roles can be filled without us, so that part of the market works well enough. The narrow slice at the top is where it fails, and it’s the only part we work in: the small number of engineers who change a company’s trajectory, and the small number of companies intense enough to deserve them.

Where this goes

Our ambition is specific: we want the first ten engineers at the most consequential startups of the next decade to have been chosen for the things that matter, by people who knew how to see them. Software widens how much of the market we can cover and AI has made that coverage wider still. The judgment at the end is still human.