That's a bad one, considering that everyone is supposed to be upbeat and positive in the face of adversity. You can't place blame on management and the environment that was in no way conducive to success because that's not culturally acceptable.
Are we supposed to prepare an answer for that question now as well because the true answer (unrealistic expectations from upper management and insufficient infrastructure) will make you fail the interview? What you could ask is what will make a team fail, and my answer would be autocratic management.
Nope. I don't want a prepared answer. I want an honest answer. Hence throwing them a rough, non-technical question that absolutely will not be on the resume, but has been part of the career of any experienced candidate.
"Autocratic management" isn't a good answer, because it's too general. What did autocratic management do? Were the requirements incomplete? The schedule unrealistic? Beaten by the competition? Depended on unproven technology? Sometimes, everyone does everything right, and a project fails anyway. There's still a reason it failed.
But when I hear a candidate talk about failure in the form of "I was a hero, but my idiot co-workers and malicious bosses ruined everything", I hear them finding someone to blame, rather than a problem that didn't get solved correctly. And that tells me a lot about what working with them will be like, when we have our inevitable failures.
Startuplandia has a way of attracting hucksters, unscrupulous businessmen and crazies with a firm disregard for what is physically possible. I notice that Ubeam was founded in 2011 and they are still around!
I once worked for an outfit where one founder was named party to an investor suit (he had awarded himself stock options after a clinical trial came out favourable) and the other was frankly incompetent and afflicted with cluster B personality disorders. It ended as well as one would have predicted. Failing startups because of founder personality and founder competence issues are unfortunately common, they are not corner cases at all, and for the person coming out of one the incidence is 100 %, but discussing such matters in an interview will torpedo your chances. No honesty for you, it's counterproductive for the jobseeker!
Seriously, Dave, if you were interviewing a candidate that had been working on the gluebot that Carreyrou mentioned in Bad Blood, how would he have to spin the story to get an offer out of you?
Hell, I've talked openly in interviews about the problems with a project that I got fired from, and blamed both management and the customer in no uncertain terms. I fault myself mostly for not walking out on it. I still get job offers when talking about how I got fired by incompetent management of an out-of-control project. But part of that is that my story leads somewhere - it leads to my lessons learned, conditions I will no longer tolerate in a workplace, #1 of which is the bottomless budget.
So I care less about how you screwed up, or who or what you blame, and more about what you learned from the failure. Tell me that, and you win my heart.
Conceptually, Theranos was very exciting. I hope someone actually pulls it off someday. I can understand the attraction for a scientist.
There are tests where it doesn't matter - consider the blood glucose - the variability of capillary samples vs venous samples is well understood and the introduced error sufficiently small compared to reference range.
But Theranos also tried electrolyte panels, and there you have a problem because the concentrations of ions in blood plasma are very different from the concentrations of ions inside cells. Both are tightly controlled in the healthy body. Slightly less than 50 % of blood is cellular matter, and even small amounts of lysis are sufficient to distort the numbers to render them clinically meaningless. You inevitably have lysis in capillary samples. Carreyrou talks about that in his book.
For example, "we made several governance mistakes on a project that meant we didn't have enough time to finish the project. On the next project, I made sure to be clearer with estimates and buffer time, so that the team etc. etc." and "Our management doesn't listen" can describe the same situation.
Again, definitely agree you are in the danger zone so its important to be thoughtful.
[1] https://www.linkedin.com/pulse/employees-dont-leave-companie...
I would wager that at least half of candidates are just good humble team players. Your approach optimises for egotistical braggarts at the expense of normal people.
It's hard for a lot of people to speak well of themselves, which makes the whole interviewing process difficult much of the time. We're trained to a beat-down that gets called humility, but it's not. Asking about successes is a way past that - it's giving them permission to say something good about themselves.
But to be fair, a lot of what I'm after is inflated claims on a resume, which are common as dirt, because people are much more comfortable deceptively bragging on paper than they are in person.
I often have a hard time putting my accomplishments into context (indeed, even seeing them as "accomplishments," because they're simply what I'm supposed to do).
(Incidentally, I hate the word "ownership" in this context. You don't own anything you can't take with you. Try taking work you did for a company with you when you leave.)
A flip-side question is to ask about projects they worked on that failed. Failures rarely appear on resumes, and it can be an uncomfortable topic. But if you can get them going, you can learn a ton about how they handle adversity. Do they make excuses, or find scapegoats? Do they take responsibility? Do they give credit where credit is due for colleagues? Do they recognize the big-picture conditions that affected the situation?