How to find a technical cofounder (and why most people never do)

If you've ever posted "looking for a technical cofounder" and heard nothing back, you're in good company. It's one of the most asked questions in startup communities, and one of the most argued about. A 2024 Hacker News thread titled "You won't find a technical co-founder" pulled in over 300 comments. Most of them were engineers explaining, pretty bluntly, why they say no.

Here's what they said, in plain words, and what actually works.

Why the usual search fails

The pitch is "I have the idea, you build it." Engineers hear this constantly. In that thread, the most common complaint was founders who see themselves as "the ideas person" but bring nothing else. An idea alone isn't a contribution, because everyone has ideas. What's rare is someone who can sell, who knows a market deeply, or who already has customers waiting.

Matching sites are a "market for lemons." That phrase came up in a thread about YC's cofounder matching. The best people rarely sit on an open marketplace. They get picked up quickly, usually by someone they already know. So you end up sorting through a lot of people who are also still looking. To be fair, a person from YC joined that thread and others said it worked for them. It can work. Just don't make it your only plan.

Your network says no. In another thread, a founder said everyone they knew was comfortable in a well-paid job. That's normal. People don't leave a stable job for an idea. They leave it for momentum.

What engineers look for before they say yes

The same few things came up again and again:

• Proof you can execute. A clickable prototype, a waitlist, five customer interviews, a pre-sale. Anything that shows you'll do the hard non-code work.
• Real domain knowledge. You know the industry, the buyers and the problem better than anyone they've met.
• Full commitment. You're working on it now, not "once I find a cofounder."
• A fair deal. Equal-ish equity and a real say in the product, not a salary-shaped promise.

Notice that all four are things you can show, not things you can claim.

What actually works

1. Start building before you find them. One of the simplest answers in the thread was "start building by yourself, talk about your work." Paul Graham's advice, linked in the same thread, points the same way: build things you care about with people who care about the same things, and don't call it a startup at first.

2. Work together on something small first. A weekend project, a hackathon, a one-month prototype. You learn more about someone in two weeks of building than in ten coffee chats. If it doesn't click, nobody has given up equity.

3. Go where builders already are, in person. Hackathons, university labs and clubs, build nights and coworking spaces. The important part is going repeatedly. You don't find a cofounder at one event. You find them on the fourth time you see each other working on something.

4. Lead with what you've done. "Here's what I've shipped and here's what I'm stuck on" gets a very different reaction from "I need a technical cofounder."

5. Consider whether you need one yet. Some commenters argued a non-technical founder can get surprisingly far with a freelancer or no-code tools, at least until there's traction. Others disagreed strongly, saying a tech company needs a technical founder. Both camps agreed on one thing: traction makes every option easier.

The short version

Cofounders are rarely "found." They're people you built something small with, liked working with, and kept building with. So optimise for meeting people who are actively building, near you, and spend real time making things together.

That's why we're building The Build Nation: it shows who's building near you right now and what they've shipped, so you can start a meetup and meet them in person. It's free during the open beta. But whether you use it or not, the advice above holds: build first, meet in person, and let the work do the talking.