How to Find a Technical Co-Founder (From Someone Who's Been One Six Times)

I have been the technical co-founder six times, across the US, the UAE, and India. Some of those companies worked. Some died slowly and taught me more than the ones that worked. Along the way I have also been on the receiving end of more "I just need someone technical" pitches than I can count, at events, over LinkedIn, through friends of friends.

So this guide is written from the other side of the table. Not "10 platforms to find a technical co-founder" (you can Google that list in ten seconds, and it won't help), but what actually makes a good engineer say yes to you, what makes us quietly say no, and the questions you should be asking before you start looking at all.

First, understand what you're actually asking for

When you ask someone to be your technical co-founder, you are not hiring a developer. You are asking a person who can comfortably earn $150k-300k a year, or run their own thing, to work for nothing for one to three years, in exchange for paper that is statistically most likely to end up worth zero.

That is the ask. It's a big one. Everything in this guide follows from taking it seriously.

A real technical co-founder does much more than write code. They choose the architecture your company will live with for years. They decide what to build now and what to fake until later. They hire and manage the first engineers. They sit in investor meetings and answer the "how does this scale" questions. They tell you, honestly, when the thing you want in two weeks is a two-quarter project, and then find you the two-week version that still moves the business.

If what you actually need is "someone to build the app," you don't need a co-founder. You need a builder, and you should pay for one instead of spending 30-50% of your company on the wrong person. I'll come back to that at the end, because it's the single most common mismatch I see.

What non-technical founders get wrong

Nearly every pitch I have ever turned down failed in one of four ways. None of them were about the idea.

You pitch the idea, not the evidence

The idea is the cheapest part of a startup. Every engineer who has been around for a few years has a folder of their own ideas; they don't need yours. What we cannot generate on our own is your evidence: customers who talk to you, a waitlist that grew without ads, an industry you know from ten years inside it, a letter of intent, revenue from a manual version of the service.

"I have an idea for an app" gets a polite coffee. "I've been in logistics for 12 years, I've pre-sold this to three fleet operators I already know, and I need a partner to build what I've been doing in spreadsheets" gets a second meeting. The difference isn't polish. It's proof that you can do your half of the company.

You treat equity like salary

I still see offers like "5% for building the MVP." Think about what that sentence says: you value the entire technical half of the company at one twentieth of it, before the company exists. Any engineer good enough to build your product alone can also do the maths, and what the maths says is that you don't see them as a partner.

The reverse mistake is just as bad: offering 50% instantly to anyone who says yes, with no vesting and no cliff. That's not generosity, it's a time bomb. If they walk away after four months, they walk away with half your company. I cover the actual numbers below.

You look for a coder, not a co-founder

Technical skill is the entry requirement, not the decision. I've watched a company with a brilliant engineer die because the co-founders never agreed on how hard each of them would work. On paper they were equal partners. In real life one treated it as a side hobby while the other spent savings on it.

You are choosing someone for a multi-year working relationship under stress, ambiguity, and no salary. The questions that matter are not "can they build it" but: do they finish things? Have they shipped products people actually used, not just repos? Can they explain a technical trade-off to you in plain language without making you feel stupid? When you disagree, do they argue for the business or for their ego?

You hide the hard questions until it's too late

Hours per week. What "all in" means. Personal runway. Who decides what when you disagree. What happens if one of you wants out in a year. Every dead company I've been close to skipped at least one of these conversations at the start and paid for it at the worst possible moment.

If raising these topics in the second or third serious conversation feels too awkward, you are not ready for a co-founder. The awkwardness never gets smaller, it only gets more expensive.

Where technical co-founders actually are

Now the part everyone asks about first, which is deliberately not first in this guide.

Your second-degree network beats everything else. Almost every co-founder relationship I've been part of started with a warm connection: a former colleague, a friend's friend, someone I'd already worked near. Make a list of every engineer you have ever worked with, then ask each one "who's the best engineer you know who's restless?" People love answering that question. Ten coffees into that list, you will know who's in the market.

Go where builders already are, and contribute before you pitch. Communities like Indie Hackers, relevant subreddits, founder Slack and WhatsApp groups, local startup meetups, and hackathons all work, but only if you show up as someone useful rather than someone hunting. Answer questions in your domain. Share what you learned pre-selling. The founders who extract value from communities get ignored; the ones who add value get DMs.

Co-founder matching platforms are fine as a supplement, not a strategy. YC's co-founder matching is the credible one and worth doing properly (a specific, evidence-heavy profile). But treat every platform match as the start of a long vetting process, not the end of your search. The failure rate of "we matched online and incorporated in three weeks" pairings is exactly what you'd expect.

The best move of all: work together before you commit. Hire them for a small paid project. Do a hackathon together. Build a landing page and run an experiment as a two-week trial. You will learn more from one fortnight of real collaboration than from ten interviews. Every co-founder decision I've made without working together first, I've regretted at least partially.

How to pitch an engineer (a script that works)

When you do sit down with someone good, here is the structure that has actually worked on me:

1. Lead with your evidence, in two minutes. What you've validated, what you've sold, what you uniquely know. Not the vision slide. The traction slide, even if traction is just "20 real conversations and here's what changed my mind."
2. Be precise about what you bring every week. "Vision" is not a job. Sales calls, customer development, fundraising, regulatory navigation, content, distribution: name your lane and show you're already driving in it.
3. Show them the boring truth. Your runway, your hours, your obligations, your timeline to first revenue. Engineers are professionally suspicious of hand-waving. The founder who volunteers the uncomfortable numbers reads as ten times more credible.
4. Ask about their ambitions before you sell yours. Maybe they want to be a CTO of 50 people. Maybe they want to stay hands-on forever. Maybe they secretly want their own company in two years. Better to find out now.
5. Propose a trial, not a marriage. "Let's spend three weeks building the smallest testable version, then decide" is an easy yes. "Join me, here's 30%" on meeting two is an easy no.

The equity conversation, with actual numbers

Here's the honest version most posts dance around.

If you are pre-product and pre-revenue, and the technical co-founder will build the entire product while you handle everything else full time, the defensible range is near-equal: 40-50% of the founder pool. The bigger your evidence (revenue, funding committed, deep domain moat, full-time head start measured in years not weeks), the more the split can tilt your way, into the 55-70 / 45-30 zone. If you find yourself justifying 90/10 with "but it was my idea," reread the section above about ideas.

Whatever the number, the structure matters more than the split:

• Four-year vesting with a one-year cliff, for both of you. This is not a sign of distrust. It IS the trust mechanism. It makes "50% to someone who leaves in month four" impossible, which is exactly why generous splits become safe to offer.
• Put decision rights in writing. Product calls, technical calls, spending limits, what needs both signatures.
• Agree the exit script now. What happens if one of you wants out, gets an offer they can't refuse, or simply stops showing up. Ugly to discuss at the start, catastrophic to improvise later.

A split that leaves either founder resentful will cost you far more than the equity ever was worth. I have watched resentment kill a company that the market was actively trying to keep alive.

When you shouldn't look for a co-founder at all

This is the section my six rounds of experience most wants you to read.

A co-founder search done properly takes three to nine months. The equity is the most expensive money you will ever spend. And the failure mode, a mediocre partnership entered because you were tired of searching, is worse than not finding anyone, because now the wrong person owns a third of your company and votes on its future.

You probably don't need a technical co-founder if:

• Your product is a well-understood build (a marketplace, a booking flow, a dashboard, a mobile app over an API). You need it built well, not invented.
• You have or can raise enough to pay for development, even modestly.
• Your unfair advantage is distribution or domain knowledge, and the technology serves it, not the other way round.

You probably do need one if the technology IS the moat (novel AI systems, hard infrastructure, security-critical products), if you can't fund development any other way, or if investors in your space effectively require a technical founder on the cap table.

If you're in the first group, the arithmetic is worth doing coldly. Thirty percent of a company that succeeds is worth vastly more than the cost of getting the product built and renting senior technical judgment until the company can afford its own. That's literally the trade I offer founders now: I build MVPs priced per screen and work as a fractional CTO with the pricing public, at a monthly cost that is a rounding error next to a co-founder's equity. Sometimes, a few months in, those engagements turn into something more permanent, and that's the best possible way to choose a co-founder: after you've already worked together.

And if you've read all this and still want the equity partner, that conversation exists too. I take on technical co-founder partnerships very selectively, maybe one a year, and everything on this page is exactly the bar I apply.

The short version

Find your evidence before you find your engineer. Fish in your second-degree network and in communities where you contribute first. Work together before you commit. Split the equity like you both believe the company will be huge, and vest it like you both know it might not be. Have the awkward conversations while they're still cheap. And check, honestly, whether you need a co-founder at all, because the answer changes everything about your next six months.

If this was useful, I write about building startups from the technical side a couple of times a month; the newsletter signup is just below. And if you'd rather rent this experience than search for it, here's how I work with founders as a fractional CTO.