How to Find a Technical Co-Founder (and Keep One)

Look at the problem from the engineer’s side for a minute. Any competent developer in London, Berlin or Austin gets recruiter messages every week, has a salary, and probably has a side project or two. Then a stranger offers equity in “an app idea” in exchange for building the whole thing. From that seat, it reads as a request for unpaid work with extra risk attached.

Finding a technical co-founder starts with fixing that pitch. The question is not “who will build this for me?” It is “why would someone with good options spend years on this with me?”

What engineers check before they say yes

Good technical co-founders are evaluating you as hard as you are evaluating them. Most of them look for the same short list.

• Evidence the problem is real: interview notes, a smoke test, a signed pilot
• A non-technical co-founder who owns something hard, such as sales or a regulated domain
• Clarity on time: who goes full-time, when, and on what money
• An honest equity conversation instead of a take-it-or-leave-it offer
• Room to make technical decisions without being overruled on a whim
• A realistic first milestone, not a roadmap of forty features

The first item does most of the work. Twenty documented customer interviews, or three companies willing to pilot, change the conversation from “trust me” to “look at this”. If you do not have that yet, our guide on how to validate a business idea is the place to start.

Where to look

Your own network comes first. Former colleagues you have actually shipped work with are lower risk than any stranger, because you already know how they behave under pressure.

University entrepreneurship centres are next. Many run team-matching events, and master’s students or PhD candidates in computer science are often open to venture work, especially if a grant can pay a salary for the first year. For Germany, the EXIST Business Start-up Grant does exactly that for university spin-offs.

Other places where founders and engineers meet:

• Hackathons, where 48 hours shows you more about someone than five coffees.
• Open-source projects close to your problem, whose contributors have already shown interest.
• Technology-specific meetups rather than generic founder mixers.
• Co-founder matching platforms, including Y Combinator’s free one. Quality varies, the effort is low.

Generic startup networking nights, meanwhile, tend to be full of non-technical founders hunting for exactly the same person you are.

What to write in the first message

Cold outreach to engineers works when it is short and specific. Three to five sentences: who you are and what you have done in this market, the problem and the evidence you have so far, what you are looking for, and a low-commitment ask such as a 30-minute call.

Skip the vision paragraph. Skip “disrupt”. Mention one concrete thing that would interest an engineer: an unusual data source, a hard technical problem, a customer waiting for a pilot. Then send it to people whose work you have actually looked at, and say what caught your eye. Ten such messages beat two hundred copy-pasted ones.

Run a trial project before splitting equity

Co-founding is tighter than most jobs and harder to unwind than many marriages. Even so, plenty of founders decide after three coffees. The better route is a shared trial with a clear goal.

Pick something small that a customer can touch within four to eight weeks: a clickable prototype five target users can test, or a thin slice of the core workflow. Agree up front whether the trial is paid or how the work is treated if you part ways.

Then watch how, not just what. Does the other person ask when something is unclear? Raise delays early? Disagree without drama? Those habits will decide the company two years from now. Compare the trial with the alternative too: building the same MVP with contractors is laid out in our breakdown of MVP development cost, and a co-founder will be building everything after the MVP as well.

Equity, vesting and who owns the code

Talking about equity early feels awkward. Talking about it after the product has value is worse.

There is no formula for the split. The most widespread convention for protecting it is four-year vesting with a one-year cliff. Leave in the first year and you keep nothing. After that, shares vest monthly or quarterly. Investors generally expect this, because it stops a founder who left after six months from owning a third of the company forever.

Mechanics differ by country. US founders typically receive restricted stock and file an 83(b) election with the IRS within 30 days so that tax is assessed on the low value at grant rather than on later vesting. UK founders usually handle it through leaver provisions in a shareholders’ agreement. Founding a German GmbH or UG, obligations to transfer shares back must be notarised, a point covered in our comparison of UG vs GmbH.

Code ownership deserves the same attention. Anything your co-founder writes before the company exists belongs to them until they assign it. Have both founders sign an IP assignment to the company at incorporation, covering everything built for the venture so far. Investors will ask for it during due diligence, and code from a previous employer’s project should never sneak in.

Red flags on both sides

Be wary of candidates who want to fix the tech stack before discussing the problem, or who promise a complete product in two weeks.

Be wary of yourself too. If you mainly want someone because they would be cheap, you are looking for a contractor, not a co-founder. Hiring a freelancer or building a no-code MVP would be the more honest choice.

Be wary, finally, of agreements that only exist verbally. What two people agreed over a beer about equity and roles gets remembered differently two years later. Write the key points down with a date and both signatures, even if the formal paperwork is months away.

If nobody turns up

Sometimes the search takes longer than your runway. Interim options exist: hire a freelancer for the MVP while you keep searching, or work with a venture studio that contributes engineering in exchange for equity. OnlineBuilders partners with selected founders this way and offers a free initial technical consultation, which can help you work out what kind of technical partner you actually need.

Next step: write one page on what you bring besides the idea, with evidence. If the page is thin, gather evidence first. If it is not, message three people from your network today who build software or know someone who does.

Questions people ask

How much equity should a technical co-founder get?

There is no formula. It depends on what each person contributes and how much time they commit. Someone joining full-time to build the product will rarely accept a token stake, and vesting keeps a generous split fair if either of you leaves early.

What is a standard founder vesting schedule?

Four years with a one-year cliff is the most common convention: nothing vests in the first twelve months, then shares vest monthly or quarterly. In the US, founders who receive restricted stock usually file an 83(b) election with the IRS within 30 days of the grant.

Should I hire a CTO instead of finding a co-founder?

A hired CTO needs a salary you probably do not have yet, and carries less of the risk. For a company whose product is software, a co-founder is usually the better fit. If technology is just a tool in your business, an agency or freelancer may be enough.

How long should a trial project last?

Four to eight weeks with one small, measurable goal is a good frame. Long enough to see how someone handles ambiguity and disagreement, short enough that walking away is painless.