How to find a technical cofounder when you don't write code

This guide is for founders who don't write code and need someone who does.

Why do good engineers say no to most pitches?

Start with what they'd give up. The median software developer in the US earned $135,980 a year in May 2025, according to the Bureau of Labor Statistics. An engineer good enough to build your company probably has a job like that.

Then there's the volume. In a 2020 Hacker News thread, one reply described "an under-supply of engineers and an over-supply of business people wanting to found." When someone asked there in 2023 why it's so hard to find a technical cofounder, engineers replied that they have ideas of their own. One wrote that "it can be difficult to find people to work on others' ideas for free." Another said that in past talks, "it was unclear what they would be contributing."

So the pitch most engineers hear is an idea and a request to build it. That's an easy no.

What makes a non-technical founder worth joining?

Proof that you've already done the work only you can do. For a 2013 guest post on Andrew Chen's blog, Elizabeth Yin surveyed 104 developers (in her words, "not particularly scientific") and found they rated idea validation as extremely important. Her advice: "You are selling traction." CRV, a venture firm, said the same this year: technical founders are drawn to partners "who've already demonstrated skin in the game."

What counts as proof:

• Customers. People with the problem whom you've interviewed, a waiting list, letters of intent, pre-orders. Anything that shows people want it before it exists.
• Distribution. A way to reach buyers that an engineer doesn't have, such as years in the industry or a partner who has agreed to pilot it.
• Work already done. A clickable mockup, a no-code version, a spreadsheet that customers use every week. Aaron Stannard, an engineer, wrote that "a demo is also a great way to get a tech co-founder to buy in."

Ben Lang put the general point well in Next Play: "Very productive people attract other very productive people."

Write down what you have in a few sentences before you approach anyone. For example:

I sold scheduling software to dental clinics for seven years. I've interviewed 40 practice managers about missed appointments, and 12 clinics now use a no-code reminder tool I set up. Four have said they'd pay for a proper version. I need someone to build and own the real product. I'm full-time on this from March.

That tells an engineer what you bring and what would be theirs to own.

Where do engineers actually spend time?

Most engineers who'd make good cofounders are employed and not browsing startup listings, so go where they already are. We build Foundinity, so it comes first.

Foundinity

You state what you need in a cofounder, and answer an assessment about how you work: commitment, working style, ambition, personality, goals, values, alongside your skills and interests. If you need someone who builds, that's part of what you state. A multi-trait algorithm built on established psychological compatibility models ranks the people you see, and every match shows where the two of you align and where you differ. When you match, a 10-day clock starts, and you can book the intro call in the app. Profiles are visible only to compatible members, and an "exploring" status lets an engineer with a job look around without announcing it. It's free to get started, with 5 likes a week and up to 3 active matches; Plus is $5 a week or $15 a month. More on how it works.

Former colleagues

In a 2026 Censuswide survey of 500 people for Starling Bank, 26% said they met their cofounder at a former workplace (startups.co.uk). Go through every engineer you've worked with and ask each the same two questions: would you consider this, and who's the best engineer you've worked with? When an engineer asked on Hacker News where to meet business cofounders, one reply began: "There's one way and one way only: former coworkers."

Hackathons and Startup Weekend

Startup Weekend gives people 54 hours to pitch ideas, form teams and build something. Steve Blank, in an interview with First Round Review, tells prospective cofounders to "date first", starting with a hack weekend or similar intense project. You don't need to code to be useful at one: run the customer calls and put the prototype in front of real users. The engineers on your team will remember who did that. Devpost and Major League Hacking list hackathons.

Open source and developer communities

Most developers build things outside their jobs. Of the 25,391 people who answered a question about tools for side projects in Stack Overflow's 2025 survey, only 2.7% said they used none. More than 180 million developers use GitHub (Octoverse 2025), and its user search lets you search by location and language, for example `language:python location:berlin`. Look for someone who has built something close to your problem, and write to them about their project before you mention yours. Forums and chat groups around a framework work the same way.

University computer science departments and alumni groups

Another 25% of the Starling respondents met their cofounder at school or university. Your alumni network includes engineers who now have years of experience. Near a university, look at computer science societies and the entrepreneurship centre's events. Some run cofounder mixers: in April 2026, Tufts' Derby Entrepreneurship Center held one for students from several Boston schools, where each person wore a sticker saying Asker, Hacker or Hustler (Tufts).

Local developer meetups

Meetups for a language or framework, such as a Python user group, bring the same engineers back month after month. Go several times before you mention your company, and ask people what they're working on. As one reply in that 2023 Hacker News thread put it, trust "arrives on foot."

How do you pitch an engineer?

Treat the first talk as a conversation. Stannard's advice to founders was "Don't pitch! Ask questions", because engineers want a say in what gets built. Bring these:

• The problem and your evidence, in two or three sentences.
• The hard technical part. Say what makes this difficult to build. In Stannard's words: "Give me (and other technical types) something big we can chew on." He also suggests a test: if an off-the-shelf product already does it, you may not need a technical cofounder. We cover that choice in technical cofounder or hire developers.
• What you'll own. Sales, customers, fundraising, operations. Be specific, so they never have to wonder what you'd contribute.
• Your hours and timeline. When you're full-time, and when you'd hope they could be.
• The risks. Lang suggests a short memo on what could go wrong and how you'd address each one.

A first message can be short:

I read your write-up on offline calendar sync. I'm working on appointment reminders for dental clinics: 12 clinics use a no-code version, and the hard part is reliable sync with three practice-management systems. Would you have 30 minutes to tell me where you think it would break?

Leave titles and terms out of these conversations. They come later, once you've both decided you want to work together.

How do you judge technical ability when you can't read code?

You can't review the code yourself, so you need other evidence. Three checks get you most of the way.

Look at what they've shipped

Ask for things you can open: a live product, an app in a store, a public repository other people use. Then ask them to walk you through one. What was hard? What broke after launch, and how did they find out? People who built something answer with specifics, and the good ones can explain it in plain words. Ask for two people who worked with them, and call both.

Ask an engineer you trust

A friend, a former colleague or a paid adviser can read their code and talk with them for an hour. CRV gives the same advice in its guide for non-technical founders: have an experienced engineer you trust review a candidate's past work before you commit. If you know no engineers at all, finding one to advise you is the first step.

Build something small together

Pick one feature that real users will touch and give it about two weeks. Gloria Lin, who wrote up her own search in The Founder Dating Playbook, worked with candidates in blocks of about two weeks. Watch whether they ship, whether they tell you early when something will slip, whether they push back when the scope is too big, and whether they explain trade-offs in words you understand.

Then run a longer trial

If the small build goes well, agree a longer trial before either of you commits. Blank suggests a trial period of about 30 days after a first project together. The founders of Whalesync ran six weeks with weekly check-ins and agreed the goals and length before they started.

Do your half where they can see it. The engineer is deciding about you too, and the best evidence you can give is customers who keep coming back because of work you did. For questions to work through during the trial, see questions to ask a potential cofounder; for the whole process, our guide on how to find a cofounder.