6 ms·
I generally went with a question my friend told me, "what was the last non-work, non-school program you wrote?". The theory being that a person who has used pr
by protomyth 12y ago
I generally went with a question my friend told me, "what was the last non-work, non-school program you wrote?". The theory being that a person who has used programming for something personal was probably a better candidate since they saw personal value in their profession.
- prezjordan 12y agoIf I know the candidate has side projects (listed on their website, github, etc.) I'll ask about them. If not, I don't even touch this question.
- whyaduck 12y agoIn a good week I work 50 hours. In a bad week, 80 or 90 (or more). In my spare time I have family commitments, play guitar, draw, paint, hike, ride my mountain bike, and travel. Ask me that question and I'll probably find a way to wind up politely and leave.
- 16bytes 12y agoI love this question and use it as part of my interview deck. It is only part of the deck, however. This question is a great positive indicator, but a terrible negative indicator. That is to say, a person who works on a lot of stuff in their spare time is very likely to be someone I'd like to hire. The reverse isn't true, which is why there are other questions in the deck. I realize that there are great developers who don't have a well populated github profile and dozens of side projects. If I had a candidate that had trouble with the question, I'd expect them to say so. I'm a pretty reasonable person. I would not expect them to try and exit the interview early with little to no indication why.
- greenleafjacob 12y agoWhat if you have side projects that make money, i.e. are "work"? Is that discounted by "non-work, non-school" or by non-work do you mean "not your day job"?
- gknoy 12y agoI imagine many would be hesitant to mention such experience, but I think it would be a great thing to hear about in an interview. If you're interviewing an parallel universe's patio11-equivalent, and they say, "I have been running FlashCardCreator.com since 2001...", and goes on to explain neat things about what she's learned from it, it sounds like that should be a big green flag. Not only is such a person likely to have lots of cross-domain insight, but they clearly have the mojo to deliver working code. If you're worried that they might decide that their work-outside-yours is going to cannibalize their time, they probably have an answer for why you don't need to worry much about that. (After all, they __did__ apply.) I would be surprised if you had to worry about them leaving any more than you would any other developer.
- 16bytes 12y agoIt's a completely open-ended question and I word it differently depending on how the interview is going. You can demonstrate passion for technology even if what you talked about was a one-off utility that you wrote for your job. I want to see if your eyes light up when you talk about it.
- protomyth 12y agoI phrase it so it is the "not your day job" version. In the more general sense a better phrasing is "something that wasn't required of you by others". Since I wrapped it in other questions, I got the idea across. If it made money, cool. Just so there was no one saying "you need to do this".
- odonnellryan 12y agoThat's fine, but if you work that much are you interviewing at places as well? I couldn't imagine working that often and not enjoying it.
- ColinWright 12y agoI'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.
- 12y ago
- deleted 12y ago[deleted]
- pc86 12y ago> Ask me that question and I'll probably find a way to wind up politely and leave. I'm always confused when I see this sentiment. I only ever see it on HN, and only when someone feels they've been asked a question below their station or that is inherently insulting.
- whyaduck 12y agoNeither - just an indicator that we may not be a good match and I'll act accordingly. I have a limited amount of time, and when I'm searching I'm pretty ruthless about controlling the number of interviews I take.
- pc86 12y agoYes, but it's not like you're going to spend that time saved doing an interview with someone else. I mean you've got the time scheduled, I just think it's rude of either party to cut it short because you're not 100% in love with every aspect of the job (or candidate). The interview is a process, go through it and collect your thoughts and assumptions at the end.
- protomyth 12y agoSo, you've never once did any program for your own benefit? Sent in a patch for some project? Programmed something because you thought it would be neat or scratched an itch? I know plenty of carpenters who put in long hours but have used their skills to build a chair or table for themselves. I've never used this as an only question, but I have got better results from people who have used their skills to solve some problem for themselves, but that isn't unique to programming.
- overgard 12y agoI used to think this way, but one of the best programmers I work with basically refuses to even touch a computer outside of work. And yet he's extremely good at what he does, and you can figure that out within like 15 seconds of talking to him about a hard problem. As far as heuristics go I don't think this is a good one.
- napoleond 12y agoYour friend is an exception. I've met a few, too, but the majority of top-tier programmers I know program outside of work. I'm not talking about "hackathons" and shit like that, or github profiles--usually just personal projects for practical or amusement (often both) purposes. Heuristics are, unfortunately, quite valuable in hiring scenarios, especially for start-ups. It's also just much more fun to work with people who love programming, and an easy way to tell (even if it's susceptible to a few false negatives like your friend) is to find out if they program in their own time.
- grogers 12y agoIt probably depends on where you work. Most of my colleagues are amazing developers, but very very few of them actually do side projects at home. Most of us wish we had more time, and would like to do this or that as a side project - but there isn't enough time in each day to do everything you want to do. The only exception to this was a guy who did amazing work on side projects, but the work he did for his paying job suffered significantly...
- overgard 12y ago>It's also just much more fun to work with people who love programming, and an easy way to tell (even if it's susceptible to a few false negatives like your friend) is to find out if they program in their own time. The thing is though, you can love programming and find that 40 hours a week of it is more than enough. I think what you'd find with this heuristic is that it tends to favor young people. It's a lot easier to be enthusiastic about some side project when you're 20 than when you're 40 and have a lot of responsibilities.
- izacus 12y agoI usually just shorten that to "what was the best program you wrote?". I've found that there were alot of people and fresh students which put alot of quality work in their school / work projects and those are worth hearing about too.
- rogy 12y agoi HATE this question but its becoming more and more commonplace. I work hard, programming 40-70 hours a week, I solve all sorts of in work problems with ideas that I've come up with to make my daily work life easier. I barely touch a computer outside of the office. Does that make me a bad candidate for all programming jobs now?
- napoleond 12y agoThe question is a litmus test for whether or not you're passionate about programming. That may sound unfair ("Why do I need to be passionate about this? It's just a job...") but the field we work in is constantly changing and the only way anyone has a hope in hell of staying abreast is if they really love it. So if you manage to keep tabs on the industry through your colleagues and you're excited about what you're working on at work, then the personal projects are much less important, but you need to demonstrate that.
- jakobegger 12y agoIt's not. If you have kids there's just no time to start a personal project next to a full time job. Having a side project just tells your employer you have a lot of spare time.
- wvenable 12y agoOn the other hand, you can code dozens of personal projects every week and be terrible at programming. When I had the time for many personal projects, I was a much less capable developer than I am now. I run circles around that guy now. So I'm not sure why the person without personal projects needs to demonstrate that they're keeping tabs on the industry any more than someone who does. Seems like you want to ensure X by testing for Y and mistaking correlation with causation.
- sray 12y ago> So if you manage to keep tabs on the industry through your colleagues and you're excited about what you're working on at work, then the personal projects are much less important, but you need to demonstrate that. I disagree. If passion is an important quality to you, then, as the interviewer, you need to ask questions that reveal whether or not the candidate has that quality. It's absurd to ask about personal projects as a proxy for asking "are you passionate about programming" and then to expect the candidate to guess your true intentions and answer accordingly.
- Balgair 12y agoProgramming is like any other job, in that programming is a tool that you use. I like this question, as it determines what the candidate uses the tools of their trade for. The answer may be that you do not program in your free time, and that may be just what the interviewer is looking for: someone that knows programing is a tool for making money, nothing more. Conversely, they may not like the answer, as it does not show the person thinks that programming is a tool to be used in the same way as a lawnmower; to more easily achieve an objective. In the end, the question, response, and counter response reveal a lot about the people and the situation. I'll add, in the end, the only thing that you, as an interviewer, should be concerned with is: how will this person make me money? Programming ethos, passion, and skill all add to this, but culture fit, propensity to post to HN at work, and family constraints all fit into this seemingly simple question of how to make dollars.
- deleted 12y ago[deleted]
- Bahamut 12y agoI have worked with many excellent developers who don't program in their spare time - you cannot rely terribly highly on the answer to this question.
- Tactic 12y agoIn my personal experience I have found that the people that put stock in this sort of question believe in the "coder" mystique and that someone eating and breathing coding is somehow more competent than someone that treats computer programming as a professional career. It is not uncommon for people to feel this about a number of professions such as chefs, bakers, graphic artists, etc. However, in my experience I prefer to judge an applicant on professional credentials rather than their free time because while it may tell me quite a bit about them it tells me little about their capabilities that I couldn't find out in better ways.