
How to find a technical co-founder if you are not technical
Where to find a technical co-founder, what to bring, how to check their work without reading code, the trial, what to offer, and when to hire instead.
If you're on the business side and can't build the product yourself, a technical co-founder can look like the answer to everything. A common first question is whether this person is good enough at code. That question matters, but it comes later.
Here is how to find a technical co-founder and check them in order: the essentials first, then their work, then something you build together.
Check you need one now
My order for a first-time founder puts the co-founder fifth: love the problem, validate it, build the MVP, get your first customers, then find a co-founder. Plenty of founders get through the first steps alone, with AI tools and some paid help. Do I need a co-founder? covers when going solo works and when it stops working.
If you're further along, or the product itself is the hard part, it's time to look. Either way, the work you do before you look is what makes a good builder take you seriously.
Check the essentials before the technical skills
Before you check whether someone is a good technical co-founder, check three things. If the answer to the second or third is no, stop there.
- Do they complement your skills? This is the easiest one to check. If you're the business side and they're the technical side, they do. Two people who both sell and plan still leave nobody to build.
- Are you excited about working together? If there's no excitement about the idea of working together, there's no point checking whether they're a good technical co-founder or not.
- Do they love the problem you're solving? The problem, not your current solution. If they don't, there's no point continuing the conversation.
Questions to ask a potential co-founder shows how to check all three over three meetings.
What matters most isn't how good they are technically. If they don't have every technical skill the product will need, that's okay. Hard skills can be picked up: a course, a few YouTube videos, and now AI to help. For me, the mindset and the attitude are the most important thing, along with those three essentials.
How to find a technical co-founder: where to look
Use more than one route at once.
- A co-founder matching platform. There are many. Y Combinator's Co-Founder Matching is one of them, and from my experience it's one of the most effective so far. As of November 2026, its page says it's free: you create a profile, it shows you people who fit your preferences, and you invite the ones you want to talk to.
- Engineers you've worked with. Someone you worked alongside for years, at a company where you were both employed, is a good start. You already know you get along and work well together. But don't stop there.
- Introductions. Ask former colleagues which engineer they'd most like to work with again. People recommend the ones they trust.
- Places where people build. Hackathons, build weekends and developer meetups in your problem's field. You see someone work before anyone commits.
How to find a co-founder has the full list of places to look, online and in person, and how to write a profile that gets replies.
What to bring before you ask
Builders on matching platforms are likely to see a lot of ideas from people who can't build them. "Business founder seeks technical co-founder" gets you very little. What gets attention is proof that you've done your half of the work already.
Bring these:
- What you found in customer discovery. How many people with the problem you spoke to, what they do about it today, and who said they'd pay or agreed to try a first version. Customer interview questions for startups covers how to run those conversations, and how to validate a startup idea covers what counts as proof.
- A written description of the first version. What it must do for the first customers, and what can wait. One page is enough.
- What you'll own. Selling, the customer conversations, the money, whatever you bring. A builder wants to know the other half of the company is covered.
Lead with that in your profile and your first message. Then let the conversation be about the problem.
How to check their work if you can't read code
Once someone has passed the essentials, look at what they've built. Ask to see their GitHub, or a portfolio page with the work they've done. Ask about their background too: where they've worked, at which companies, and in what roles.
You don't need a technical person to review it. If you have access to their past work, give it to an AI coding tool, such as Claude Code, OpenAI's Codex or another one, and ask for its view.
Two rules before you paste anything in:
- Only use code that's theirs to share, and ask first. Personal projects, open-source work and anything they've built for you are fine once they say yes. Code they wrote for an employer is usually not theirs to hand over. Don't ask for it, and don't take it if they offer.
- Check what the tool does with what you give it. Some tools may keep what you paste in, depending on your plan and settings. Read them before you start.
Then ask the tool plain questions. Is this organized so another developer could pick it up? Are there tests? How does it handle errors, and anything to do with user data? What would you ask the person who wrote it? Ask it to point to the files behind each answer.
An AI review gives you a second opinion on the code in front of it. It can't tell you whether they wrote it alone, how they work with other people, or whether they'll still be there in a year. And like any AI answer, it can sound sure and still be wrong. So treat what it says as questions to ask them, not a verdict. Ask them to walk you through one project and what they'd do differently now. What an AI co-founder can and can't do goes further into where AI helps and where it doesn't.
Build something together first
Meetings only show you so much. Before you commit, build something together for at least a month. Two weeks is not enough.
Pick something that moves the startup forward: one feature of the first version, put in front of the people you interviewed. Then watch.
- Do they ship something every week, or only talk about it?
- Can they explain what they built in words you understand?
- Do they raise a problem early, or hide it?
- Do they push back when you're wrong?
- Do they come back with something you didn't ask for, like a customer they called or an idea they couldn't drop?
Before the trial starts, agree in writing who owns what gets built. In Ireland, the UK and the US, ownership of code isn't automatic, and if they still have a job, their employer may have a claim on work they do. Intellectual property for startups explains why for each of those countries, and a lawyer where you set up the company should word it.
When the month is up, talk honestly about what worked, and either of you can walk away.
What to offer a technical co-founder
Start from an equal split. Move away from it only for a clear difference between you: one of you full-time and the other not, one bringing months of real work (never just the idea), or one putting in money. Always with vesting, for both of you. Offering a builder a small slice to get them cheaply tends to backfire.
- How to split equity between co-founders works through the split.
- The founder vesting guide shows how vesting works. The exact terms depend on the country where you set up the company, and a lawyer there should draft them.
- Co-founder roles and responsibilities covers agreeing, from day one, who has the final say on product, sales and money.
- What to include in a co-founder agreement lists what to write down and sign.
When a developer or agency is the better choice
You don't always need a co-founder to get the product built. A freelance developer or an agency is often the better choice when:
- you can describe the first version in a written plan,
- the product isn't the hard part, and the risk is whether anyone will pay,
- you're still testing the problem and haven't found anyone who passes the essentials.
Paid help costs money, puts a step between you and every change, and stops caring about the product once the job is done. Keep the brief to the must-haves, pay in short stages, and make sure the contract gives your company the code. Before real customer data goes in, have someone who reads code check how it's stored and who can get at it. How to build an MVP compares the ways to build a first version.
A technical co-founder is the better fit when the product itself is the hard part and will keep changing for a long time, or when customers are paying, asking for more every week, and the freelancer can't keep up.
A made-up example: the escape room booking tool
This is a made-up example, and everything in it is invented, including the numbers. Imagine you spent seven years running bookings at an escape room, and you want to build software that lets independent escape rooms take group bookings and split the payment between players. You can't build it.
First you do your half. You talk to 22 escape room owners. Nine say they chase group payments by hand every weekend, and four agree to try a first version. You write one page on what it must do.
On a matching platform you meet an engineer with ten years at large companies and an impressive GitHub. Over two calls he talks about the tech he'd use and never once about escape rooms. You feel flat after both calls. You stop there, without looking at his code.
A former colleague introduces you to a second engineer. She has fewer years behind her and has never built payments. But she's already been asking escape room owners about no-shows on her own, and you leave the first call wanting to start that evening. With her OK, you give two of her personal projects to an AI coding tool and ask what it would ask the person who wrote them. You take three of its questions into your next call. She answers them plainly and tells you what she'd change in one project now.
You agree in writing who owns what you build, then spend five weeks on the split-payment feature for the four rooms. She ships something every week. In week two she spots that owners take most bookings by phone, and changes the plan before you'd noticed. When the five weeks are up, you both want to keep going. You start from an equal split, both on vesting, and write it into a co-founder agreement.
Payments were the gap in her skills, and she picked them up during the trial. The excitement and her love for the problem were there from the first call.
Ready to Move Faster?
Get actionable feedback and insights on your challenges and goals. 30 minutes focused on helping you move forward.
No sales pitch. No obligations. Just helpful advice.