Let me elaborate a little.
My dreams are none of an interviewer's bloody business. I'm here to work not share the things that give me hope in my darkest moments or the aspirations that shaped my adulthood. I find this question very creepy and extremely unprofessional.
I could maybe figure out a "lesser dream" to share, but then what's the point of this question? To find out the most intimate thing that I'd be willing to share?
Where I see myself in ten years is a meaningless question to ask after I've had, what, fifteen minutes of exposure to a company's culture? Maybe I'm the kind of person who sees themselves in management over ten years, but you've got such an amazing working culture that you could convince the most ambitious career builder to stick to engineering instead. Or vice-versa. Or do you really want to hire the kind of people who get an idea in their head, and then do it, even if it takes them ten years and it's really, really, really bad idea?
I've heard all sorts of ways to justify these things. That it's a way to see if a candidate can relate to you and evaluate their empathy -- if anything, this will say more about an interviewer's biases than about anything else. To see if a candidate can communicate about abstract matters -- as if there are not countless questions about ethics, aesthetics and epistemology in our profession that you need to start prying into personal things. That it's a way to see if they're "career-oriented", whatever that means, as if someone who writes amazing code but wouldn't hustle for a promotion is a bad hire.
So far, it hasn't turned out to be a bad idea.
Yup - that's all it is. And you're going to have a certain envelope of negatives (usually far worse than this) in any environment.
So while it does make the flag a bit bless verdant... to call it a "red flag" seems to be a bit of a stretch.
(And as for the substance: agreed, and a capable interviewee should know how to work around those questions and similarly silly ones, like "what's your greatest weakness?". It's a two-way street. And while it's not a positive datapoint, it's hardly a KO-criterion. (viridescent? aquamarine? turquoise? :) )
If you don't have any work-safe dreams, you might want to see a psychiatrist. Again, though, you've misinterpreted the question - They're looking for you to express your spark of passion. It doesn't even have to be for the job. People like people who can talk about something passionately.
That's the charitable reading. The adversarial reading is that they're looking for the emotional buttons to push to maximize your output while minimizing their investment in you.
There's so much zero sum game thinking here when it comes to job relations ...
To me these are two entirely different classes of questions. The first is open ended and meaningless, while the second is directly connected to your career and thus highly relevant for both you and the company. I know where I want to be in 10 years career wise and thus I want to know if this job can help me get there. Equally the company probably knows where it wants to be in 10 years and as such wants to know if you can help it get there.
and
> I'm not looking for a particular answer just an honest one.
are contradictory one to another.
That type of culture is unbearable to those that don’t perfectly fit your monoculture.
My opinion is uninteresting people are just fine for coworkers, you're interviewing for an employee, not a drinking buddy.
A big part of the hiring process, at least at big companies, is taking a pile of 100 resumes and reducing it to a pile of 10 resumes, because there's no way you're interviewing 100 candidates. So 90% are eliminated before ever meeting, and bias is huge there.
But the bias starts even before that. The pipeline itself is biased. There are more men than women, more whites than non-whites (proportional to society as a whole). This is a problem that needs to be addressed at the society level, not the interview level, but it affects the interview level, because candidates who are "different" lead to unconscious bias.
For older technical people... well, I'm one of them. I'm 53, which means a lot of my social group is the same age. I freely job-hop and don't struggle to find work. I've never felt that my age was a bias against me. What I do see, and I see this a lot, is people my age who worked at the same company for 10-20 years and then lost their job, for whatever reason (usually reorgs or dying companies). Their skill set has become largely about intra-company specialization rather than broad industry skills. I watched my spouse go through this. She lost her job of 13 years in a buyout, and it took her six months to find something else. She had gotten deep in a narrow business field (international e-commerce analyst), and there just weren't many jobs for her, even in our busy town. We didn't want to move to the Bay area or New York, and while she could do generic business analysis or project management, without industry-specific skills, she's not much better than someone barely past entry level. Eventually she found a job that suited her long-built skills, but it took a while. And this story is common as dirt, it's happened to a lot of my friends.
That's how age bias works. It's not discrimination, it's just being unprepared for the job market after too many years in one place. Keep your skills up to date and switch jobs regularly, and age is just a number.
So when you talk about monoculturing and bias at the interview point... nah, that's not the problem point. The problems of bias prevent the interview from happening in the first place.
Hey, I ask a lot of these questions in consulting. What I’m looking for is to tell if a) you can communicate a point clearly b) if you can talk generally about your career and are growth oriented.
If you said that field evolves rapidly bit above that would be a good answer. If you span it as a joke “surely writing angular 25, the last web framework ever” even better.
I wouldn’t ask the dreams question, but the coolest question is loaded with coolest, I would say “tell me about a previous project you enjoyed working on” and see if you have had a good project you are passionate about.
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?
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.)
- Anyone who skips those questions are rejected outright. If you're not willing to put in a little time you're not interested enough to be considered. You'd be surprised how many people skip these questions.
- If you've done something crazy cool or interesting it's a plus but if not it isn't a negative.
- Can you communicate something that's a bit abstract?
- Relevant jokes are usually seen as a plus.
Yep, same here.
> Anyone who skips those questions are rejected outright.
Any company using these questions is rejected outright. I'm looking for someone who is willing to give me money for code, not a wife.
Please don't take this the wrong way but "presenting" in this way at an interview is not helping you.
It's different from being a good talker, which can be entertaining, but isn't really two-way.
Talk about something that you can sound excited/relatable talking about. Friends, family, volunteer work, that all works.
Recently, I've been applying for web developer positions and am coming across applications with these sorts of questions:
- What's the coolest thing you've done both in life and at work?
- What are your dreams?
- Where do you see yourself in 10 years?
I certainly do have answers for these questions, but I can't tell if they're the ones that employers want to hear. And are these things for other random people to know?
There are things I've done that I think are cool, but that doesn't necessarily mean that most people will think they are cool. Honestly, there really isn't anything about my life that is conventionally cool, even by the standards of the nerdiest nerds. Should my life have been more unique and exciting by this point?
The same can basically be said of my dreams, although I do not aspire for big dreams. I haven't made enough money yet to even think about anything more grandiose than simply living comfortably. Do my dreams need to be more exciting? Should I be shooting the moon? I feel like any honest answer I give to the question will sound disappointing to any startup.
Should I see myself anywhere in particular in 10 years? Beyond making more money and taking on more responsibilities in my career, where should I be in 10 years? My field evolves so rapidly that I can't honestly predict that far ahead, let alone 5 years into the future. But maybe I'm not cut out for what I do if I can't see that far ahead?
I could very well be what's wrong in the picture, but it seems to me like we are culturally intolerant of "normal" people who have a skill and want to make a living. Everyone needs to have dreams, grand aspirations, and a little clairvoyance. I tend to have pretty high confidence, but seeing this kind of language when applying for jobs does stir up that feeling of imposterhood in me.