The best place to find a technical co-founder is among people who have already seen you work, such as former colleagues and warm introductions. Then widen the search to founder communities, hackathons and accelerator co-founder matching programs. Before you split equity, build something real together for a few weeks, put vesting in writing, and keep a plan B moving.
Expect it to take longer than you hope. Good engineers are busy, well paid and pitched often. And if you are not yet sure you need a co-founder at all, compare a technical co-founder with a fractional CTO before you start.
Step 1: Decide what kind of technical co-founder you need
“Technical co-founder” covers very different people, and the profile changes where you look and what you can offer. Most fall into one of three types:
- The builder. Writes most of the code for the first year or two. Needs broad, hands-on skills across web, mobile, backend and cloud, plus the discipline to ship small.
- The technical leader. Has run teams before and will build the first version, but their real value is hiring and leading engineers. Rarer, and usually expects more equity and a salary sooner.
- The specialist. Deep expertise in whatever makes your product possible, such as machine learning research, hardware, security or payments infrastructure. Essential for deep tech, usually unnecessary otherwise.
For most early software startups, you want a builder with good judgment who can grow into a leader. Before you search, write one paragraph describing the work you expect this person to own in the first 12 months. If you cannot write it, you are not ready to search.
Step 2: Make your startup worth joining
Strong engineers hear “I have an idea, I just need someone to build it” all the time, and many say no without a second meeting. An idea alone asks them to carry most of the risk. What changes their mind is evidence that you will carry your half.
Before your first conversation, have these ready:
- The problem and the customer, in two sentences.
- Evidence of demand: customer interviews, a waitlist, letters of intent, pre-sales or a manual version of the service already running.
- Proof you can do the non-technical half: sales, partnerships, operations, fundraising.
- Runway, or a credible plan to raise it, so they know how long they would go without a salary.
- An honest equity offer you are willing to commit to on paper.
- A one-page co-founder brief: problem, evidence, role, first-year plan and terms.
That brief is your main search tool. You will send it to everyone who might make an introduction, and it saves every candidate an hour of guessing.
Step 3: Where to look for a technical co-founder
Search roughly in this order. The further down the table, the less you know about the person, and the more the trial in step 4 has to tell you.
| Where to look | Why it works | Watch out for |
|---|---|---|
| Former colleagues | You have seen each other work under pressure | They may not want startup risk |
| Warm introductions | Someone you trust vouches for them | Vague asks get vague intros |
| Founder communities and events | Full of people who want to start something | Many are pitching their own idea |
| Hackathons and build weekends | You see how people build and decide | A weekend shows speed, not staying power |
| Accelerator matching programs | Startup-minded people who are actively looking | You start as strangers |
| Open-source and engineering communities | A public track record of real work | Show up to contribute, not to recruit |
| Engineers leaving startups | Used to risk, often between roles | Ask why they left |
The most productive move is the least glamorous one. List 30 people who might know a strong engineer, send each a short, specific ask with your brief attached, and follow up. “Who is the best engineer you have worked with who has talked about starting something?” gets far better answers than “Do you know any developers?”
In communities and at hackathons, lead with curiosity about other people's work rather than your pitch. People usually join as co-founders because of the problem and the person, and neither shows in a single coffee.
Step 4: Work on a real project together before you commit
Never split equity on the strength of a few good conversations. Work together on something real first, ideally for four to eight weeks. This is the most important step, and the one founders are most tempted to skip.
Good trial projects are small, real and useful even if you part ways:
- A clickable prototype or a thin first version of the core user journey.
- A technical spike on the riskiest part of the product, such as a tricky integration or an AI feature.
- A customer experiment you run together: a landing page, a round of interviews, a manual pilot.
While you work, watch how they operate. Do they ship something usable when they said they would, and tell you early when they will not? Do they talk to customers or only to the code? How do you disagree, and how quickly do you resolve it? And are they actually available? Someone who can only give you Sunday evenings is a contributor, not a co-founder yet.
If you are not technical, get a second opinion on their work from a senior engineer you trust. The techniques for interviewing developers when you are not technical apply here too. Sign a short agreement that whatever is built during the trial belongs to the company, and consider paying a modest fee if they are giving up paid work to do it.
Use the trial to settle the questions that break partnerships later:
- How many hours a week can each of us commit, and from when?
- How long can each of us go without a salary?
- What are we aiming for: a venture-scale company, a profitable smaller business, or an early sale?
- Who has the final say on product, on technology and on money?
- Where will we work, and does that matter to either of us?
- What happens if one of us wants to leave in year one? In year three?
Step 5: Agree on equity, vesting and roles in writing
Have the equity conversation during the trial, before months of goodwill make it awkward. Three things need settling.
Vesting
Vesting means each founder earns their shares over time. The common standard is four years with a one-year cliff: nothing vests in the first year, a quarter vests at the one-year mark, and the rest vests monthly or quarterly after that. Someone who leaves in month five usually walks away with no vested shares. That protects everyone who stays, including your co-founder if you are the one who leaves. Insist on vesting for every founder, yourself included.
The split
No formula settles this, whatever online calculators suggest. What reasonably moves the split: who is full-time and from when, who takes the bigger pay cut, who brings the customers, the money or the core technology, and how much existed before the other person joined. Founders who start together full-time often split equally or close to it. Someone joining after the product, funding or traction exists usually receives less. In my experience the range runs from a stake in the low double digits for a late joiner to an equal split for someone there from day one.
Roles and decisions
Write down titles, who owns which decisions and what happens on deadlock. Make sure everything created for the company, including the trial work, is assigned to the company. Rules on equity, vesting and IP vary by country, so have a startup lawyer draft or review the documents. This is general guidance, not legal or tax advice.
Red flags in a potential co-founder
- Wants founder equity with no date to go full-time. Keeping a day job during the trial is normal. Keeping it indefinitely while holding a founder's stake is not.
- Refuses vesting. There is no good reason for a co-founder to want their full stake on day one.
- Wants to own the code personally, or builds in personal accounts and resists moving them into the company's name.
- Starts by rebuilding everything in an unusual stack, or wants months of architecture work before anyone talks to a customer.
- Dismisses the business side. “Sales is easy” and “if we build it, they will come” are both warning signs.
- Goes quiet. Missed check-ins and vague updates during a trial do not improve after you sign.
- Is really a vendor. An agency or freelancer offering to build in exchange for founder equity is a supplier paid in your most expensive currency. Read why equity-for-development deals tend to go badly before agreeing to one.
Turn the list on yourself as well. If you want a co-founder's commitment with an employee's lack of say, you are hiring, not co-founding, and good candidates will notice quickly.
What to do if you can't find a technical co-founder
Plenty of good companies start without one. If your search has stalled, these are the realistic alternatives, and they combine well:
| Option | Best when | Main trade-off |
|---|---|---|
| Fractional CTO | You have some budget and need to build now | Costs cash; part-time attention |
| No-code prototype | You need to prove demand before building properly | Limits on complex logic and scale |
| Small round to hire | Investors will back you before there is a product | Dilution, and you still need to hire well |
A fractional CTO gives you senior technical leadership, and sometimes the build itself, for a monthly fee instead of a founder's stake. That is the gap I fill for founders, covering both the CTO seat and the engineering; my fractional CTO services page explains the model. It also makes a later co-founder search easier, because you are recruiting into a live product.
A no-code prototype lets you test demand with real users before anyone writes custom code. It will not carry a complex product forever, but traction from a scrappy prototype is one of the best recruiting tools you can have. See when no-code makes sense and when it stops working.
A small round from angels or a pre-seed investor who backs you on the problem and your track record lets you pay a strong engineer instead of asking for equity-only commitment. You will still need technical judgment in the room to hire your first developer well.
For the other routes, including agencies and freelancers, see how to build an MVP without a technical co-founder.
Where to start this week
- Write your one-page co-founder brief.
- List 30 people who might know a strong engineer, and send each a specific ask.
- Book one founder event or hackathon in the next month.
- Set a deadline for the search, such as 90 days, and decide now which plan B starts if you hit it. Better still, start it in parallel.
- When a promising candidate appears, propose a scoped trial project and raise equity and vesting during it.
The founders I have seen land great technical partners are not the ones with the cleverest idea. They show up with evidence, treat the search like a sales process, and make it easy for the right person to say yes.
Frequently asked questions
How long does it take to find a technical co-founder?
There is no reliable average, and it depends heavily on your network and how much evidence you can show. In my experience, an active search often runs anywhere from a few months to a year, and some founders never find the right person. Treat that uncertainty as a reason to keep building while you search, so a long hunt does not freeze your product or your learning.
Should a technical co-founder get a salary?
Before funding, many co-founders take little or no salary and are paid mainly in equity, which is why personal runway matters when you evaluate someone. After a raise, founders often pay themselves modest salaries, usually below market and similar to each other. If a candidate needs a full market salary from day one, they may fit better as an early employee with a smaller equity grant than as a co-founder.
Do co-founder matching programs actually work?
They can, especially if your own network has few engineers in it. Treat a match as a first meeting, not a decision. Check the person's past work and references, talk about goals, hours and money early, and do a short project together before any equity discussion. The weakness of any matching program is that you start as strangers, so the trial period matters even more than it would with a former colleague.
What should a founders' agreement include?
A founders' agreement usually covers each founder's equity and vesting, roles and decision rights, assignment of IP to the company, what happens if someone leaves or stops contributing, and how deadlocks and disputes are resolved. Some founders put these terms into the company's shareholder documents instead of a separate agreement. Rules vary by country, so have a startup lawyer draft or review it; this is general information, not legal advice.