← Back

Engineering

How to find a technical cofounder through people who know both sides

By Boardy · 5 min read · Published

A rough cream stone and a precise black cube on linen.

Start with engineers who already care about the problem you are solving, not engineers looking for any idea. The best technical cofounders join because they believe in the specific problem, not because a platform matched your profiles.

If you’ve already worked out who you want to meet in ChatGPT, open Boardy in ChatGPT and tell me who you’re looking for and why.

Warm introductions through mutual respect beat cofounder matching platforms. Someone who knows both of you can vouch for your execution and their judgment in a way no profile ever will.

A useful introduction comes from someone who understands what each person wants and can explain why the two of you might work well together.

How do I meet a technical cofounder who believes in this problem?

Ask people who know builders in the space you are tackling for introductions to engineers who have already expressed frustration with the same problem.

The question is not "do you know any engineers looking for a cofounder?" The question is "who have you heard complain about this exact problem, or tried to build something adjacent?"

You can tell me what you are working on and the technical background you need. I will look for builders who have already signaled interest in that problem space, through side projects, previous roles, or public writing. Once both sides opt in, I introduce you.

This is not a matching algorithm. This is someone who knows both people explaining why the introduction makes sense, then getting out of the way.

Where do I actually find technical cofounders?

The highest-yield places are communities where engineers talk about hard problems, not communities organized around finding cofounders.

Cofounder matching platforms can work, but the signal is weak. Everyone on those platforms is theoretically open, but very few are compelled by a specific problem. You end up pitching your idea to people evaluating many ideas at once.

If you have already built a small proof of concept or gathered early customer feedback, mention it. Engineers respect founders who have de-risked the idea before asking someone to bet years of their life on it.

How do I vet a technical cofounder when I cannot code?

You cannot evaluate code quality directly, but you can evaluate judgment, communication, and how they think about trade-offs.

What to test How to test it
Technical judgment Describe the product you want to build and ask what they would build first, what they would explicitly skip, and why
Comfort with ambiguity Walk through a scenario where early customer feedback invalidates the original plan. How do they react?
Communication Can they explain a past technical decision to you without jargon, and do they listen when you explain the customer problem?
Collaboration style Work together on something small before committing. A prototype, a pitch deck, or a few customer interviews

Ask someone technical you trust to have a conversation with them. Not a formal interview. A peer conversation about past projects, architecture choices, and how they have handled production failures. You are looking for someone who can give you a read on their experience level and working style.

Avoid engineers who talk down to you for not coding, or who cannot explain why a technical choice matters for the customer. A good technical cofounder translates between technology and customer value constantly.

What equity split makes sense for a technical cofounder?

If you are both joining at the same time and both committing full-time, start with equal equity. Anything else creates resentment before you have written a line of code.

If one of you has already been working on the idea for months, built a prototype, or signed early customers, then a different split may make sense. The key is that both people feel the split is fair and that the conversation happens early.

Use vesting. Four years with a one-year cliff is standard. This protects both of you if the partnership does not work out in the first year.

Do not defer the equity conversation. If you cannot have a direct conversation about equity and expectations now, you will not survive the much harder conversations that come later.

When a technical cofounder is not the right answer

Not every early-stage product needs a cofounder. If the technical scope is narrow and well-defined, you may be better off hiring a founding engineer once you have customer revenue or funding.

A technical cofounder is probably wrong if:

The difference between a cofounder and a founding engineer is ownership. A cofounder shapes the product and the company. A founding engineer executes within a direction you set. Both are valuable, but they are not interchangeable.

If you need help deciding which you actually need, or you want an introduction to someone who has made this hire before, tell me what you are building and I can connect you with people who have been in your exact position.

How long does it actually take to find a technical cofounder?

Plan for three to six months of active outreach, conversations, and relationship building. The right cofounder is not found in a week.

Most technical cofounders come from second- or third-degree connections, not the first round of outreach. Someone you meet introduces you to someone else, who then introduces you to the person you end up working with.

Use that time to make progress on the non-technical side. Talk to customers, refine your positioning, build a no-code prototype if you can. Engineers are more likely to say yes when they see that you are capable of making progress without them, not stuck waiting for someone to arrive and save the idea.

If six months pass and you have had dozens of conversations but no traction, revisit whether you need a cofounder at all, or whether the idea needs more validation before someone will bet on it.

Common questions

How do I find a technical cofounder?

Start with warm introductions from people who know both you and the engineer. Ask for intros to builders who have already expressed interest in the problem you are solving, not engineers generically looking for any idea.

Where do technical cofounders actually come from?

Most come through second- or third-degree connections, not cofounder matching platforms. Focus on domain-specific communities where engineers discuss the hard problems you are tackling.

How do I vet a technical cofounder if I cannot code?

Test their judgment and communication. Ask what they would build first and why, work on a small project together, and have a trusted technical person talk with them about past projects and trade-offs.

What equity should a technical cofounder get?

If both joining at the same time and committing full-time, start with equal equity. Use four-year vesting with a one-year cliff. Have the conversation early and directly.

If you can describe the problem you are solving and the technical background you need, I will look for builders who have already signaled interest in that space and introduce you once both sides opt in.

Message me