Technical Co-Founder... Is it worth it?

[computerhxr]

Does anyone know what a technical co-founder is?

I'm trying to decide if it's worth doing. I tried doing some research but most of the online articles are about finding one, or explaining why you don't need one.

I couldn't find any salary reports, but it's looking like it's probably part-time and probably doesn't pay much. I'm thinking that I could do more than one at a time, and still continue what I'm already doing.

Initially, I have three or four opportunities. I'm thinking that I would round-robin the workload then move onto something else. I'm sure they will need on-going work in some form but again, I don't really have any idea what a technical co-founder is or does. Maybe I'll make it a hobby on the side and start co-foundering these on the regular?

Is there anyone here with experience that could shed some light on this for me? Pros and Cons?

 

[redbaron]

Pros:
- low responsibility
- low risk
- some potential for high reward

Cons:
- probably not high reward in actuality
- possibly unpaid
- the title is jargon designed to sound good (even though it doesn't), when it's probably more accurately summarised as 'Technically Not a Co-Founder'

Can't hurt to try I suppose?
​

 

[INTPINTP]

Technical Co-Founder - I take it you are a programmer of some sort.

This likely means that the person (the other cofounder) is a marketer of some sort. They have skills or an idea they'd like to implement, but they don't have the technical skills to make it a reality.

If you're serious about doing it, check their background. See if they've had success in the past, and see what they can bring to the table. Some salesmen type personalities blow hot air, and some are truly successful. Gotta sort out the two.