5 ms·
I certainly hope that they don't ever assume that experienced candidates don't need a programming test. There is a particular kind of dysfunctional candidate w
by btilly 11y ago
I certainly hope that they don't ever assume that experienced candidates don't need a programming test.
There is a particular kind of dysfunctional candidate who once was a programmer, graduated to being a lead programmer, and then became an architect. As an architect they stop programming, and their programming becomes rusty. Once that happens, the feasibility of their proposed "architectures" becomes steadily less practical.
You can detect them by their first getting offended that they would be asked to program during an interview, and then failing to actually write working code.
By contrast people who really do program have no objection to being asked to program in an interview. To the contrary being asked to actually program is seen as a positive sign that they won't have co-workers to deal with who can't actually program. (This is an unfortunate experience that most programmers try not to repeat.)
- collyw 11y agoI have declined some programming tests, when the employer wants yet another three hour challenge to build a mini app. That leaves not much time for actually thinking about a problem and rushing out a crappy solution. Not the way I like to write software. I have code online I can show them and talk to them about, and extend if they want to see me actually code. Bashing out code is usually the simplest part in writing a software solution to a problem.
- btilly 11y agoThere is a difference between "demonstrate that you can program" and "waste X hours on busywork".
- jkot 11y agoI write lot of code, but I refuse to do coding at interview. For me its sign of dysfunctional company. But I do not mind to do pair coding, and fix an actual bug. There are more reasons, in short it takes me couple of hours/days to warm up and grasp the problem. And secondly I refuse to waste my time, on half arsed throw-away code, with zero results.
- krat0sprakhar 11y ago> And secondly I refuse to waste my time, on half arsed throw-away code, with zero results. That's a very wierd thing to say. Does that mean that each and every side-project that you do ends up being substantive? If writing few lines of code gets you a job at a good company where you can spend your time working on exciting problems how is that wasteful? I do program a lot too, and I typically don't mind writing code in an interview. The only thing that sets me off are stupid level-order binary-tree traversal questions which test nothing but rote-memorization skills.
- jkot 11y agoMost of my code is thrown away. But I like to finish stuff, so there is a chance I spend next weekend finishing/polishing the interview questions. It is great for career, but has to be managed. Also my job is to design database structures, and there is no such thing as simple problem. Even binary tree needs thousands LOC for tests, concurrent access, writes...
- sjg007 11y agoI mean you should know how the basic data structures work. Not necessarily for a web dev job but for a software engineering job. Data structure interview questions are a good small concrete problem to reason about. But they completely ignore the other 80% of the job which is design, soft skills, estimates, timelines, code reviews etc...
- krat0sprakhar 11y ago> I mean you should know how the basic data structures work Oh I'm not discounting that. I'm just saying that off the bat binary-tree traversal don't really test my understanding of the data structure. Recently in an interview I was asked a problem which eventually required using a binary-search-tree to improve the running time. This, I believe, is the right way to test but it requires the employer to spend more time designing interview questions rather than relying on a problem bank[0]. (which is a strong filter for good companies in itself) > But they completely ignore the other 80% of the job which is design, soft skills, estimates, timelines, code reviews etc... This is true but this is really really hard to test. In the interviews that I've been giving, I've indeed been asked design questions. I assume soft skills are implicitly tested while speaking to the interviewer (to some extent, at least). But other factors, AFAIK are very hard to test. Also, I would argue that a candidate doesn't need to know everything coming in. Estimates, timelines etc can be learnt on the job. IMO, if somehow employers could find a way to reasonably trust that the code I have on my Github is indeed written by me then I think that should be strong indicator of my competence. Evaluating candidates who don't have any code in the open is a different matter altogether to which I have no solution. [0] - http://leetcode.com http://leetcode.com
- thinkdevcode 11y agoGee, that's the path I followed. Now as a chief architect, I guess I can't code anymore. Good to know!
- to3m 11y agoImplication is not commutative.
- thinkdevcode 11y agoThe OP wrote a blanket statement stating if you follow this specific path you become "rusty" and ultimately end up not being able to code. He then states this becomes an issue when architecting solutions. To me this is clearly non-sense as someone who's followed this path (and know others who have as well). Being an architect allows me to see the big picture and move the organization in the right direction (as we see it), while still being able to get into the trenches with my developers when something arises or help is needed. Granted, this is different for large enterprises but for startups/small/mid sized businesses, yes, us architects still get our hands dirty (or else we're irrelevant).
- btilly 11y agoNo, that was not what I said. I said that there is a specific kind of bad candidate to watch out for who generally HAS followed that specific path. I DID NOT say that ALL people who follow that path will become that kind of bad candidate. Or even most. Just enough that you can't afford to say, "This guy has been programming for 15+ years, is an architect, and sounds smart. I'll skip the programming test."
- btilly 11y agoIt is about your skill set, not your title. I have met architects who were unbelievable coders. And ones who were nightmares. But every good architect that I know was also a good programmer. They might or might not actually spend much time programming, but they clearly could do it. My understanding of the reason is that a good architect needs to be able to mentally connect every level from abstract architecture down to actual code. If you can't, then you'll eventually absorb ideas that sound good but don't really work in practice. (A random example that I dealt with was someone who didn't understand the latency added by sequential RPC round trips. And that the latency gets worse if you're making the mistake of using XML as your on the wire format...) And the failure of said ideas can always be attributed to programmers having screwed up your brilliant architecture. For the record, this observation about architects is not original to me. I spent a year at Google, and in interview training we were clearly told that Google does not have a position for a non-coding architect. This is not to say that Google does not have positions for architects. http://research.google.com/pubs/jeff.html http://research.google.com/pubs/jeff.html certainly wears the architect hat well, and is behind the design of large chunks of fundamental Google infrastructure. See http://static.googleusercontent.com/media/research.google.com/en//people/jeff/stanford-295-talk.pdf http://static.googleusercontent.com/media/research.google.co... for an example of his showing that skillset off. But they have to code. Which Jeff does. A lot.
- danieltillett 11y agoCould this not be solved by telling the candidate what you expect and then telling them that if they can't program to the expected level that they will be fired on the spot. Leave it to them to demonstrate that they can program before or after they are hired. If the candidate can then they will be happy to demonstrate after they start. Everybody is happy.
- ianmartin 11y agoExcept as the candidate, I'm not happy. Companies already hold the balance of power. Pre-threatening me just means I'm not going to leave my current job.
- btilly 11y agoI don't think so. First of all nobody sane would take a job where they are expected to measure up to some unspecified measure or else get fired on the spot. And any competent HR department will tell you that carrying through on the threat will risk the potential for lawsuits. (They want a paper trail showing that the person should be fired.) Secondly it takes a surprising amount of time for an incompetent programmer at an average organization to get discovered. You usually spend a period of time studying how things are set up before anyone expects you to do anything. And by the time you can be evaluated you've certainly used a bunch of other people's time with your questions. It is far more efficient to determine this in the interview process. And thirdly, a creative company can more easily solve the problem by offering a choice of ways to demonstrate competence. See http://www.starfighters.io/ http://www.starfighters.io/ for an alternative to traditional interviews.
- collyw 11y agoPretty much every job I have had has had a three month probation period.
- danieltillett 11y agoThis just means you can be fired for any reason in the first 3 months. You can certainly be fired on the first day.