3 ms·
Bad signs: - They are too eager to have you. - All of the critical work is being done by contractors. - "This is just a prototype of the software," they say,
by kabdib 11y ago
Bad signs:
- They are too eager to have you.
- All of the critical work is being done by contractors.
- "This is just a prototype of the software," they say, "There's no way we're going to ship this." Double the "run away" factor if the company is doing a hardware product and the runway is less than a year . . . maybe two.
- Your old boss from two years ago calls you up and says, "Interested in rescuing a start-up?"
- jguimont 11y agoHowever rescuing a startup/project is good as a contractor. Did it more than once and it is rewarding in both experience and money.
- JoshTriplett 11y agoAs long as you get paid in money rather than stock, and you cash the checks the minute they arrive.
- Piskvorrr 11y agoThe important par is "as a contractor" (with clearly defined exit conditions). Also, some projects are beyond rescue.
- odonnellryan 11y agoIt depends. I haven't exactly rescued a startup, but worked on several completely failed products to bring them up to "workable" status for a lot of large companies. Usually, if I'm working directly for the company, it is great. They understand the previous team failed and they want to move forward. It might be a little tough to ultimately gain their trust, but confidence goes a long way. If I'm working as a subcontractor for the contractor/team that failed, it won't be fun (in my experience). They are not grateful, they are going to blow budget (their problem, but they make it yours) and they will blame you when the time comes for it. Also, they take forever to pay.