3 ms·
I'm sure there are many here who would agree with you, but let me offer an alternative viewpoint. You said: > Ask me that question and I'll probably > fin
by ColinWright 12y ago
I'm sure there are many here who would agree with you, but let me offer an alternative viewpoint. You said:
> Ask me that question and I'll probably
> find a way to wind up politely and leave.
The implication is that rather than opening a dialog with someone to (a) find out why they think that question is relevant, and (b) offer reasons why you'd be a good fit despite not working with code outside your job, you'd simply leave?
For me, as a potential employer, that would be a good reason not to want to hire you. It makes you sound like you would not be an easy person to work with. It sounds like if someone came to you with an unreasonable software requirement you would simply shut them down without trying to find a way to deliver something that finds a good balance between what they've asked for, and what can be done.
But perhaps that's not the impression you intended. If not, could you expand further?
- gknoy 12y agoYou have a very good perspective on what an employer would love to hear from someone, regardless of whether they code for fun on the side. However, as an employee, such questions might be highly correlated with past companies that are looking for people who do not have family commitments, or who are willing to do unpaid extra work at home "for fun". As an interviewee, it makes me wonder, even if only fleetingly, "Will I be discriminated against for not being (young+single)?". (Are we even allowed to ask about marital status or age?) Even if such a thing was never your intention, the interviewee might have had prior bad experiences with those who ask such a question, and view cutting the interview short as a way to ensure they don't get mistreated later.
- ColinWright 12y agoIn that case, just as an interviewer looks for indications beyond a single question, so should an interviewee. Cutting an interview short because of one indicator seems short-sighted. Surely better would be to use it as one indicator, and then start looking to see if there are more. But I understand the point point of view, I'm just trying to give some balance, and point out that the black/white attitude this suggests is sometimes a clear indication that you are not cut out for a particular position.
- whyaduck 12y agoMy initial answer may have been a bit short, but it wasn't actually binary; my response would depend on, among other things, how the question was asked, as well as other indicators. As a mid-career professional, however, that question's a sign that I'm probably not going to fit into the "culture". To be honest, I've been through my share of interviews and I only remember getting a similar question once (it was related to technical blogging/participation on tech sites like StackOverflow or similar). In that case they made it clear that it wasn't a necessity but it was definitely nice to have. I went through the first interview and was asked back for another, but I dropped out of the process for unrelated reasons. Regardless, if it makes me not want to work for you, and you don't want to hire me because of my reaction to the question, then my likely response would be win/win, right? :)
- ColinWright 12y agoMaybe, although the other aspects of your response - the reasons why you don't program outside of work - make it clear that I would definitely want to know more, and it's completely plausible that you would be a good fit. But we wouldn't discover that if you simply wound things up and walked out. I find it hard to believe that you are active here and would not be an excellent contributor - the walking out is at odds with that. Then again, maybe you would not be a good fit. My comment is simply that based on just one question you are actively avoiding finding out.