sown
Joined 18 years ago
Joined 18 years ago
We've all been conditioned to expect this. Then, here comes along someone with a different question where if you answer it differently, you probably don't get the job.
In my mind, I'm going to ask, "Is this a serious question? Are we just filling time?"
> Are you ready to be CEO of Google on Monday?" If they say yes, then I'll probably entertain myself by asking how they'd run the company while mentally moving on to the next candidate.
This question...it just seems so loaded and I have to disagree. I can get a 'no' vote (which is enough to end the interview process) because I give a silly answer to an uncertainly question.
If I say, "I want to build apps for non-profits" is that going to sink me during a QA interview? What if I say, "I want to enable non-profits with tech?" during a product or project manager interview? To me, both of those things are heavily intersected. But it seems like I can get stopped right there. God forbid if someone says they want to be a stay-at-home parent.
I'm going to cold read you and tell you what you want to hear.
I feel this question is less-than-helpful because it doesn't really extract any extra information yet is approached with a different angle to make the question intentionally tricky and make good candidates fail.
You say this like I've not thought about it or tried it myself. :)
It's difficult since I don't know what I don't know. I stumble around trying to figure out what I need to figure out and come to realize that I don't know what goes where.
It's also difficult because of sheer time. I spend 13-14 hours going to work, being at work, or coming home from work. Whatever suggestion you have I've probably thought about or tried, so do be considerate if you decide to reply. ;)
Not sure I understand.
Anyways, I've been around engineering teams for a while now and here's what I mean: there's always some principal engineer or fellow (in the terms of a title) that is greatly esteemed and admired because of decades of progressively larger and larger feature creation and system architecture/leadership.
If all I ever do is fix bugs -- forever in my career -- it means I'm not going to build anything and I don't get to be on the team that gets the people to the stars because that team is reserved for aforementioned team of people who have built a lot.
I probably shouldn't be a programmer anymore since all I'm good for is fixing bugs.
But guess who gets the glory? :(
At the very least you now learned about them. I want you to read this: http://mikerowe.com/2015/08/otw-rejection/
And let me relate to you: I get turned down for jobs all the time. It is not because of capricious reasons that I wish were the case, but it's because of me not knowing something. Yes, it's maddening because they throw out good candidates along with the bad to minimize risk to them. The same facts happen to me and you, but try to have the perspective on them be as positive as you can.
You might want to try comparing how many people show up vs how many people register. Then you'd know.