What are red flags that signal you should walk away from a startup job?
quora.com
quora.com
When you're not treated fairly, that's clearly a red flag. But many people see coworkers treated poorly while they themselves aren't, grab a beer after work and talk about it, commiserate etc. but don't consider the possibility that maybe they themselves are next.
Sick Systems: How to Keep Someone With You Forever: http://issendai.livejournal.com/572510.html
Even worse, he enjoyed it, thoroughly. Such people should never ever be allowed to get anywhere near a position of power over other people.
They were still in "stealth mode" at this time, taking some earlier work the researcher had spent time on and hardening it for general commercial sale. This was the first red flag I should have seen, instead of taking the time to reboot the product and start it over for a modern market, the development team was spending a year doing bug fixes and cleaning up broken research code.
Not long after starting I went with the CTO to a trade show for market research and meet and greets with some industry partners. He booked us a lavish 4-star hotel and during a week-long trip maybe spent 2 hours at the show. He couldn't get out of there fast enough and instead wanted to rent a conference room outside the city and spend the week brainstorming product ideas. Remember, he had directed the dev team to not develop a new product but to merely fix and update his old code. He then described some new ideas that I recognized as being more or less exactly like a competing product. I asked him to describe how we would differentiate it from that product. Instead he claimed it was a totally different idea. Red flags #2, #3 and 4
And it went on a for a while, intense conflicts between the CTO and the dev manager put development work into a holding pattern, lack of a good sales strategy, and so on.
Eventually there was complete turnover at the C-level and the investors brought in a new team, they asked me to stay on while they rebooted the company so I did, and we did better, almost turned it around. But by that time we were stuck with a huge legacy codebase dwindling investment dollars and a host of other problems that we could never seem to shake.
Despite being a bad experience, I learned more from that failed company than I've learned in the other 15 years of work. Observing so many failure modes happening all at once, and seeing how a pro-team might go about a turn-around has taught me an entire business school's worth of street smarts.
I'd almost recommend riding a company down like that to people serious about startups so they can learn the same things, but to be honest, I wouldn't wish it on my worst enemy.
I met a CTO of a company in Toronto who told me how his predecessor had set up MySQL all wrong. I pressed him for details, and it was not setup any differently to how I would have. This was not in the context of an interview, but it left a very lasting negative impression.
When you've got both portions, everything is awesome. I'd worth with a guy for years, and never had a problem with them. If I was working with some code they wrote and didn't get what was going on, I'd ask them, they'd explain, it'd make sense, and everything would be fine.
Then they'd leave, and I'd no longer have access to the portion of the program in their head, and the code they'd left behind would become worthless crap. The structuring was all wrong, the choice of variable names idiotic, the corner cases they handled seemed trivial and the ones left unhandled, crucial.
Maybe there's something wrong with everyone I used to work with (as I tended to think the first time or two this happened), maybe if we were better and writing documentation this wouldn't happen. But it is very, very easy to be given a codebase from a former employee -- a perfectly fine codebase written by a perfectly competent employee -- and conclude they are an idiot, because you're missing the portion that's in their head.
link:http://www.dc.uba.ar/materias/plp/cursos/material/programmin...
Any employer who trashes a former employee to you, will trash you to the next guy who comes along.
First comment about employers treating a coworker badly. It's a good general rule, if someone does something nasty to someone else, stick around and they'll do it to you too.
Having learnt that lesson the hard way, I whole-heartedly agree. Our "gut" is the equivalent of a supercomputer against the hand-held, battery-powered rational part of our minds. And it is there for a reason. If your "gut" screams at you to just run, you should at least seriously consider walking away. Every time I failed to do so, I came to regret it.
Could your experience here be confirmation bias? You remember the cases where you felt you should run but didn't and it went wrong, and forget those where you felt you should run but didn't and everything was just fine?
The other side is that if you leave, it's very hard to say what would have happened otherwise. You may feel you've dodged a bullet when there was in reality no gun.
It's the reason why you might get the feeling someone is lying to you without being able to name every single piece of body language that told you why.
The truth is nothing is perfect, the reason these discussions don't go anywhere is because you're going to insist on finding the imperfections and then try to exploit that to win.
That is your right, but I explained both what it is, and why it's often correct.
I'm just too old to let myself get pulled into one of these discussions, sorry.
The ways in which we respond to things instinctively is a topic I find both fascinating and incredibly important. Personally I think there is enough evidence to suggest we should be highly wary of ways in which we think that we don't carefully analyse. If I'm wrong I could be ignoring a very powerful way of quickly responding to things. I think that people who rely on gut instinct are putting themselves at risk of making worse decisions on important issues, or trusting others that operate in the same way.
I'm not going to keep poking, because there's no joy in talking to someone that doesn't want to respond, and certainly no joy in talking to someone who thinks that a discussion or debate is either something to be won or something where neither person should expect to come out with a different opinion.
"Gut feeling" is often boils down to a "compressed" rapid response, based on all of our previous experience, without having to go through all the reasoning and debating that we usually do.
It makes sense that quick reactions can be good if they're responding to things we have done many, many times before. It also makes sense that quick reactions can be very poor if they're responding to things that we've not done much.
Especially level 2's last bullet point (keep your eyes and ears open), which reminds me of this:
http://steveblank.com/2009/12/21/the-elves-leave-middle-eart...
What.
The problem with this is that we have no data on people who had a gut feeling that something was not right but were wrong about that gut feeling. People would tend to talk about times when "I should have listened to my gut about this" but rarely would tend to talk about when their gut was wrong and they were worried for nothing. (And I can think of several personal examples of this type of thing.).
Once again, there will be exceptions and people where such an approach isn't ideal.
Plus, what is the downside risk of being overly cautious since that has to be factored in.
If the gut is based on things that you have observed in the past, or your personal experiences, then it is also possible that you will jump the gun by being overly sensitive and matching a pattern incorrectly. [1] In that case you could be wrong. I guess what I am saying is "it's not that simple" as trite advice typically makes it sound.
"minimize potential loss" also means "avoid potential gain".
[1] This actually happened to me and although this is just a single example which I highlight and where I choose to ignore the gut and plug on, in my particular case I am glad that I had done so. (Was with a relationship..).
I don't have that problem so much anymore. When my gut tells me something is wrong, I usually also have a conscious logical reason. It takes a lot of self-awareness, though.
Never used.
That happened to me once
Unfortunately, there are a lot of deceptive people in business, so avoiding them entirely is not always possible. If you're forced to deal with them, my best advice is to be on guard. Be aware of what you have at steak if they turn on you and only work with them as much as required.
2) If you ask the MD what their turnover is and they cannot answer the question coherently.
(true story).
Doctors can assuredly have fun in responsible ways, and you know what? I want my doctor to be a happy person who enjoys their livelihood, because if they aren't happy... well...
The working poor are an explicit example of what becomes of you, should you find yourself lashed to unsavory tasks as a life sentence. Very obviously no fun. What little fun there may be, is incidental. Asking that question is sort of tone deaf. Like asking:
Well what about the cow in the barn? Is she on board
with becoming a hamburger after she's done giving us
all that milk? We'd better ask.
One has to assume that no one aspires to a life of working poverty. It just sort of happens to you, like a cruel prank. Possibly as a direct result of lawyers having fun.Sometimes it takes discipline to continue when things aren't fun in pursuit of a goal that is noble (or fun).
For the working poor well night school or improving ones skills - yes I know that's not always easy but life is what you make it.