3 ms·
it would be an alarm bell (big one) if none of the founders has a technical background. When you join a new group of people who you have no history with it, the
by DyslexicAtheist 8y ago
it would be an alarm bell (big one) if none of the founders has a technical background. When you join a new group of people who you have no history with it, then it takes some time to build trust (battles fought together under which bonding can occur) and learn their motives.
My fav resource (only discovered it recently here on HN) is this document https://docs.google.com/document/d/1ZJZbv4J6FZ8Dnb0JuMhJxTnwl-dwqx5xl0s65DE3wO8/preview# https://docs.google.com/document/d/1ZJZbv4J6FZ8Dnb0JuMhJxTnw...
it has helped me a great deal to assess a new situation and figure out whether the non-tech founders and decision makers in the firm are actually on the ball doing their part.
Understanding their role (what is their strategy in finding product market fit) is crucial in evaluating "your bosses" performance and ultimately if whether the team and product can make it post MVP.
Just focusing on MVP is a fallacy IMVHO because it lets them isolate you (the engineer) into sticking to your niche within the org. The problems then start once you have the MVP and bosses then realizes they have missed all the steps (because they didn't know and unlike you are still learning the hard way how to do things) and you as a team are actually nowhere. It always ends in tears unless all of you are already at eye-level.
good luck!
- dabockster 8y ago> It always ends in tears Tears is best case scenario. OP should be reviewing his/her paperwork with an attorney at this point. I fully expect the employment documents to have errors or vagueness conveniently located in places that would benefit the business.