You find a technical co-founder by having something concrete to show, going to where developers already spend time, and working together on a real milestone for a few weeks before anyone talks about equity. Developers get pitched constantly; what they rarely get is a partner who has already done the work they can do.
1. Bring more than an idea
If you are non-technical, your first job is to prove you can execute: a clickable prototype, ten customer interviews written up, a landing page with signups, or a spreadsheet version of the product. If you are technical and looking for another engineer, ship the smallest working slice yourself. Either way, a candidate should be able to see the thing in two minutes.
2. Write a one-page brief
Developers respond to clarity. One page:
- The problem, and who has it (with evidence you talked to them).
- What exists today and what is missing.
- What you bring: domain knowledge, distribution, design, money, time.
- What you need: the stack, the time commitment, the first milestone.
- How you propose to split things: equal or near-equal, vesting over four years with a one-year cliff.
Publish it. Hiding the equity conversation until later is the fastest way to lose good people.
3. Go where developers are
Post the brief in stack communities that match the product (a fintech product in the Python or Go hubs, a mobile app in Flutter or Swift). On DEVAE, the find-teammates page and the co-founder matching flow exist for exactly this; hackathons and local meetups are the offline equivalents. Avoid "looking for a CTO" posts on general job boards; they attract the wrong applicants.
4. Work together before you commit
Agree a two-to-four-week trial on a real milestone: the onboarding flow, the data model, the first integration. Meet in a live room twice a week so you see how each other works under mild pressure. You are testing four things: does the work get done, do they tell you when it will not, do you agree on what "good enough" means, and do you enjoy the conversation. Any "no" is a no.
5. Write it down
When it works, formalise it: equity split, vesting, cliff, roles, what happens if someone leaves. A standard founders' agreement template is fine to start; a lawyer is worth it before you raise money. Handshake deals end companies.
Red flags on both sides
- A founder who will not share equity "until the product proves itself."
- A developer who wants to rewrite everything before shipping anything.
- Either person unavailable for the trial period but "fully committed after."
Realistic expectations
Most people talk to five to fifteen candidates and run two or three trials before finding a fit. Budget three months. It is slower than hiring and it should be: you are choosing someone for years.
A worked example
A product manager in Denver has interviewed forty independent restaurant owners about inventory waste and built a spreadsheet tool six of them use weekly. She writes the one-page brief, proposes a 50/50 split with four-year vesting, and posts it in the Python and Next.js hubs and on the find-teammates board. Eight developers respond; she runs short calls with five and trials with two. One disappears after the first week. The other ships the data model and a supplier import in three weeks, tells her honestly when the OCR idea will not work, and pushes back on scope in a way she finds useful. They sign a founders' agreement in month three.
Questions people ask
**Should I offer a salary instead of equity?** If you can pay, you are hiring, not co-founding; that is fine, but call it what it is. Co-founders take risk together, which is what equity represents.
**What if the developer wants a larger share because they build everything?** Talk about it directly and early. Contributions differ in kind, not in worth; if you cannot agree on a split within a few conversations, you will not agree on harder things later.
**Can a co-founder be part-time at first?** Often yes, with a written date for going full-time tied to a milestone or funding. Open-ended part-time arrangements usually drift apart.
