Look for: 1.Can you sell? Do you have enough knowledge of the market? You’d be surprised how many “founders” I’ve talked with that haven’t made a simple google

Look for: 1.Can you sell? Do you have enough knowledge of the market? You’d be surprised how many “founders” I’ve talked with that haven’t made a simple google search of the competition and why/how their product is different 2. Runway length. As a technical co-founder I don’t want to be worrying about investor relationship, 4 months of money in the bank or some other items that belong on the CEOs concern. 3. How much work is needed before users can start using it. This is a personal preference but I gravitate towards a project/MVP that can be completed in 3-4 months and after that I’d expect the CEO to start bringing in users. The test for any startup is it’s ability to onboard people and if after that time users are not coming I start considering moving on. Things to avoid: 1. Jerks. The relationship between co-founders is based on a lot of trust and a good chemistry/communication. If I’m unable to connect with the cofounder I’d very likely be very unproductive. 2. Lack of funds. Usually tech cofounder role come at a pay cut and the initial test of the founder in my book is her ability to raise funds 3. No mvp, pitch deck, prototype in excel or whatever. I’m hoping to see that the founder has tried to test in any way possible his idea, let it be by making a mock in figma, no code, a spaghetti of zappier actions, and the results of those tests. When I don’t see this it usually tells me that the founder sees his value as the owner of an idea and expects the technical cofounder to “make it work”. That is a huge red flag for me and will get me running for the hills in no time. Hopefully it doesn’t sound too harsh… I’ve been burned before as a tech cofounder :)