How is joining as a cofounder different from a startup job?

A startup job pays salary for defined execution and gives you a small fraction of a percent in options, if any. Joining as a cofounder means equity in the tens of percent, real decision rights on product and technical direction, and near-zero salary for the first year or more while the risk that the company fails entirely sits on you too. It's a fundamentally different bet, not a better-paid version of the same job.

How do I evaluate a founder before committing to build with them?

Treat it like evaluating a cofounder, not accepting a job offer. Ask what they've already validated with real customers, not just their pitch. Ask how they think about disagreement and decision rights. Talk to anyone who's worked with them before if you can. A founder who can't answer 'what have you learned from actual customers' is asking you to bet on conviction alone.

Should I ask for a salary too, not just equity?

Some do, especially past the earliest pre-funding stage, and it's a reasonable ask once there's revenue or funding to support it. In the earliest pre-revenue stage, most genuine cofounder arrangements are equity-heavy and salary-light on both sides, if only one side is taking salary and the other equity, that's closer to an employee relationship than a cofounder one, worth naming explicitly.

Blog Podcast

Joining an early-stage startup as a developer, as a cofounder

Joining as a cofounder means equity measured in tens of percent, a real say in product and technical direction, and accepting near-zero salary and real failure risk, in exchange for owning a meaningful piece of something you help build from nothing. That's a different trade than a startup job listing, which pays a salary for defined execution. If you want the first, look at founders directly (not job boards) and evaluate them the way you'd evaluate a cofounder, not an employer.

By Curtis ThomasLast updated 2026-08-05

Cofounder or employee: know which one you're choosing

A job board lists roles at companies that already exist. What you're looking for here is different: founders, often solo, with a business problem they understand well and no one yet to build the product with them. See what actually distinguishes a cofounder from an early hire if the line isn't clear yet, equity, decision rights, and risk all move together, and it's worth being explicit with a founder about which one you're both agreeing to.

What to look for in a founder before committing

Evidence of real customer conversations, not just a pitch. A founder who can describe specific, concrete customer pain in detail understands the problem; one who can only describe the solution might not yet.
Clarity on what they need from you specifically, versus a vague "someone technical." A founder who has thought about product direction, not just "build what I say," is more likely to treat you as a partner.
How they talk about risk and runway. Someone who's thought through the first 6-12 months (savings, other income, what happens if funding doesn't come) is more likely to still be building in a year.

Where to actually find founders looking for a technical cofounder

Skip job boards for this search, they select for the wrong relationship. Browse Trusted Cofounder's public directory, filterable by role and city, or go straight to the business cofounders looking for a technical partner page, since that's the pairing you're the other half of. Read their "Looking for" description directly rather than a polished pitch page, it's usually a more honest signal of where they actually are.

Before you write any real code

Agree on equity and vesting explicitly, in writing, before either of you commits meaningful time. See how cofounder equity is typically split and structured in Finland. This protects you as much as the founder, if the arrangement isn't working after a few months, a documented vesting schedule means walking away doesn't cost either side more than it should.