News for hackers. Stuff that matters.
Re:How to win the coding interview by kayman on Tuesday May 31, 2016 @12:23AM (#11804557)
I'm tired of companies asking me to code at their interviews.

I have 10 years experience with references. I have code that I've built, deployed to production still running today. I have cultivated my own clients, gathered requirements and built something that delivers business value.

Instead of a coding interview, I'll make a counter offer. Why not hire me on a 1 week contract to come and do some real world work. Work that is small enough to be done in 1 week and big enough to deliver some value.

At the end of the week, you pay me wages and if you're not happy, you can not extend another week.

Isn't this a much better way to evaluate a good candidate?

Re:How to win the coding interview by EpicEng on Tuesday May 31, 2016 @01:04AM (#11804695)
>Instead of a coding interview, I'll make a counter offer. Why not hire me on a 1 week contract to come and do some real world work. Work that is small enough to be done in 1 week and big enough to deliver some value.

Except now I have to jump through hoops with HR (let's just assume they'd be OK with this, which they almost certainly won't), get the contract in place, work with IT to get your environment set up, and bring you up to speed (so really I may get one full day of actual work)... just to realize that I don't want to hire you. Oh, and did I find you through a recruiter? Now I have to pay them a cut. Do I now get to run this little bureaucratic maze for all N candidates I'm looking at? You have become a very expensive interview across at least three departments and you're probably not worth it.

Sorry, but no. I do ask for some whiteboard coding, but it can be done in any language (or pseudo code) and I'm really only trying to tease out your thought process. For a junior or mid level position, yes; I am also trying to figure out if you can write a line of code. I'm also not sure how you're going to be able to get away from your current job for an entire week (I have literally never interviewed a candidate who wasn't fresh out of college who was unemployed at the time).

I agree that it can be a pain, but there aren't always better ways to measure your ability to take a problem and turn the solution into an algorithm.

Re:How to win the coding interview by hiou on Tuesday May 31, 2016 @11:16AM (#11807000)
Just so you know, in the past I used to actually bother to jump through the hoops like a trained circus performer for the apparent gift of employment from some place that actually needed me a lot more than I needed them. Then I would get all the way to the end of the interview and then tell them I would never take the position because of it. I used to hope this might stop the silliness.

Then I just stopped taking interviews with that nonsense altogether and found places to work that I actually wanted to be and that, more importantly, had mutual respect for one another as opposed to being treated like someone who was supposed to be grateful for working at some run of the mill office job. One where we were all supposed to pretend we were given some great gift of fixing someones crappy log file code that broke production. Or adding some api endpoints for a new model.

These jobs aren't all that great and all this nonsense is I'm sure keeping a lot of capable people out of the industry making slightly less money while being treated like human beings and equals.

Re:How to win the coding interview by EpicEng on Tuesday May 31, 2016 @04:04PM (#11809725)
I don't understand how asking you to write some pseudo code on a whiteboard is "(not) treating you like a human being". Honestly, if you're so willing to waste both of our time just to make some silly point then I wouldn't want to work with you to begin with. Extremely childish behavior.
Re:How to win the coding interview by LnxPrgr3 on Tuesday May 31, 2016 @02:18AM (#11804967)
I for one actually appreciate coding interviews. Besides, I know my resume isn't a bunch of stuff I made up yesterday, but how are you supposed to know that? I do wish most were done differently though.

A few months ago, I interviewed with a company--the first rounds were remote, and we used an online tool so the interviewer could watch me work problems in an environment with a "compile and run" button, which was great!

Imagine my disappointment, then, when I got to the in-person interview, sat down in a nice conference room with a computer attached to a giant TV and a wireless keyboard, and was handed a pencil and a pad of paper on which to code.

That's clearly something I need more practice with--but why? It's yet another thing I have to be good at to get work, that doesn't make me better at doing the work I get.

Re:How to win the coding interview by BurningFrog on Tuesday May 31, 2016 @02:08AM (#11804927)
I did a 2 week stint like this for a small company once, and the setup took maybe 10 minutes.

In a bigger organization it's probably more involved, but if you set out to make it a standard way you interview some developers, I think it's perfectly doable.

I agree that improvising it when a developer asks for it, which is what I think you're describing, would be harder.

Re:How to win the coding interview by LnxPrgr3 on Tuesday May 31, 2016 @02:45AM (#11805076)
My first development job worked like that--a one-month trial that got turned permanent something like 2 weeks in, at a tiny company hiring at a slow rate.

I'm glad it got me my first gig, but I'm not sure I recommend it. IME, any position that actually gets applicants gets a flood of hopelessly unqualified candidates. (Think: will fail FizzBuzz, even almost a decade after the blog post that started it.)

Re:How to win the coding interview by mhotchen on Tuesday May 31, 2016 @03:55AM (#11805311)
My first dev job was like this as well, also in a tiny company hiring at a slow rate (I was the only person hired in my time there, and also the only employee). I think that this sort of thing worked for the company I was employed at because the work wasn't very technically challenging so I was able to get on with things quickly and it became more about cultural fit.

It's interesting that the parent is suggesting this for when you have a lot of experience rather than when you have none.

Given the number of people I've interviewed over the years who have 10 years experience and look very strong on their CV, but still struggle with our basic "coding challenge" (on par with FizzBuzz but more aligned with what our company was doing), even before we get to the real interviewing (with another alarmingly high dropout at this point as well), I can't see hiring for a trial being an effective strategy. We would be sinking way too much cost and effort in to it.

It may also result in poor hiring choices because one person's ticket/feature/whatever may have hidden challenges, and another person's might be easier than initially assumed. There's now more randomness involved in what's an already too random process.

Maybe interviews should be a bit less involved, and companies should be more willing to take advantage of the probation period (and employees too, I've seen a handful pass their probation and regret it).

Re:How to win the coding interview by BurningFrog on Tuesday May 31, 2016 @03:42AM (#11805260)
Yeah, I think it's for unusual people in unusual situations.
Re:How to win the coding interview by chief1ic on Tuesday May 31, 2016 @01:57AM (#11804891)
The fact that you need to involve three different departments just to hire someone for a week is a key part of why hiring is so broken these days.
Re:How to win the coding interview by EpicEng on Tuesday May 31, 2016 @02:13AM (#11804943)
How so? HR needs to be in the loop unless I want to take on payroll, contracts, etc. IT needs to be in the loop unless I want to spend my time setting up equipment, which certainly isn't the best use of it. I am most valuable when I am leading my team and doing engineering. Not every company is some five man outfit, and successful five man outfits have to grow up at some point. There are many things to consider when bringing someone on, even a contractor.
Re:How to win the coding interview by phasmantistes on Tuesday May 31, 2016 @03:24AM (#11805209)
Some companies have trade secrets. Do you think Google is really going to let you come in and poke at the Search stack for a week just to see if you're hireable?

This isn't about the number of departments. This is about companies needing to make very real tradeoffs between maintaining their current speed/security/stability and investigating future talent.

Re:How to win the coding interview by voidr on Tuesday May 31, 2016 @05:26AM (#11805576)
I'm a contractor with a decade's worth of experience, I automatically turn down places that ask me to do implement a linked list on a whiteboard, I do appreciate tests where I get an IDE and have to solve a simple problem, because after a certain level it's mainly about how you solve problems and how well you can explain what you are doing.
Re:How to win the coding interview by thomasahle on Tuesday May 31, 2016 @05:31AM (#11805592)
Can it be any IDE?
Re:How to win the coding interview by Clubber on Tuesday May 31, 2016 @12:32PM (#11807534)
>Except now I have to jump through hoops with HR (let's just assume they'd be OK with this, which they almost certainly won't), get the contract in place, work with IT to get your environment set up, and bring you up to speed (so really I may get one full day of actual work)... just to realize that I don't want to hire you.

There are two major reveals in that sentence. One, HR rules your hiring practice and therefore you and your department, and you just advise them. Two, your company is so soul-suckingly bureaucratic, I couldn't imagine a good, creative, problem solving developer would ever want to work there. Both are red flags.

Re:How to win the coding interview by EpicEng on Tuesday May 31, 2016 @04:15PM (#11809830)
>Both are red flags

No they're not; they describe 98% (made up number) of the industry, and I don't think that "soul-suckingly bureaucracy" is an inevitable outcome of implementing reasonable processes.

We have IP that we have to protect. We have a company to protect (hence the HR involvement). Sure, you may be lucky enough to wing it in your little five man operation and get by, but you had better hope you don't run into a problem employee if you're not covering your ass. The sort of company you describe can be a ton of fun to work at, but you're also probably failing in a ton of areas and you don't even realize it yet. It's a mistake to think that your hipster SV perspective is the way that the world should work.

Re:How to win the coding interview by Clubber on Wednesday June 08, 2016 @06:04PM (#11866068)
You are close minded. Instead of insulting people who dare to criticize your silly interview, maybe you should listen to them. Another red flag. You seem to think you are in a buyer's market. What does your company offer that is so compelling someone would put up with that silliness? Let me guess, market rates. I hope you at least inform applicants that you expect them to code on a whiteboard so you aren't wasting their time.
Re:How to win the coding interview by ma2rten on Tuesday May 31, 2016 @02:01AM (#11804905)
I think kayman talking about interviewing to work as an independent contractor because he said: "I have cultivated my own clients, ...".
Re:How to win the coding interview by kayman on Tuesday May 31, 2016 @09:29PM (#11811542)
Yes. I mean instead of asking me to do work for free. Why not I provide a small paid sample of my work. A risk both of us can take and live with.

If you don't like the work, we can part ways knowing we are not the right fit.

Re:How to win the coding interview by gregmac on Tuesday May 31, 2016 @02:15AM (#11804952)
> I'm tired of companies asking me to code at their interviews. I have 10 years experience

I just saw some code a candidate wrote (offline) who also had nearly this much experience in C#, and who apparently explicitly called out using C#6 and being a C#/.NET expert etc, etc.

Their code was written like it was 10 years old. Used array allocation (rather than collections). Time calculations like Convert.ToDouble(Convert.ToInt32(hourStr)/60)+Convet.ToInt32(minStr). Giant for loops where a simple LINQ query would do. It also failed to solve the problem.

10 years but hasn't learned anything new doesn't count for 10 years experience, in my opinion. That's why even "experienced" developers get coding questions.

(Btw, If the candidate hadn't explicitly called out their supposed expertise their use of old coding style could be overlooked; but since they had this on their resume, it either meant they were completely clueless about it, or simply lying. Either way, not a good start.)

Re:How to win the coding interview by yoklov on Tuesday May 31, 2016 @09:59AM (#11806516)
Going to second the other comment, when you're rushed for time, you don't end up with "beautiful" code (But you should at least solve the problem).

I know none of the code I've ever wrote for a job interview was very good. Often it's total shit, hell, it often has a while (true) loop that I break out of later. (usually I ask if they'd like me to clean it up after I get it working properly).

If your interview is designed around trying to see stylistic choices such as these (yes, the distinction between writing a loop and using linq is style), you should refocus it to be about figuring out the candidate's thought process.

Re:How to win the coding interview by gregmac on Tuesday May 31, 2016 @11:15AM (#11806990)
There actually are performance differences between linq and typical for loops (basically anytime you can use deferred execution), but sure, I'll agree it's mostly style.

However, if you claim to be an expert in modern C#, you should write modern C#. To use my example, surely between string parsing, time calculations, collection handling and loops there is SOMETHING in there you use on a daily basis and can demonstrate your claimed ability write in a modern way.

I picked a small example, I don't actually know if we're moving forward with the candidate or not (I looked at the code but I've otherwise not been involved in the interviewing). For what it's worth, we have gone forward (and even hired) people that did poorly on the coding test, because through talking to them, they clearly know what they're talking about, and they could explain why they did badly.

However, I've seen many times where someone can't sufficiently explain what they can do or accurately describe things they know about, can't write code in a coding test (even if allowed to finish without time limit), and don't have any open source profile (eg, code published on github).

I don't expect everyone to be able to write SQL JOIN statements, but I do expect people that are "database experts" to be able to. If you claim to have an "expert level understanding of network protocols" you had better be able to explain to me the difference between TCP and UDP (and no, "UDP is more secure, TCP is faster" -- a real answer I got once, from someone with 15 years experience -- is not a good answer, even if it wasn't backwards).

How do you hire someone like that? It could be just me and/or my team: none of us can communicate with this person sufficiently, while they'd be okay with another team... but that in itself is probably reason to be a bad hire for us (and them).

Re:How to win the coding interview by cosmolev on Tuesday May 31, 2016 @07:04AM (#11805834)
Disclaimer: I've never written any C# code, I write Java code.

"Convert.ToDouble(Convert.ToInt32(hourStr)/60)+Convet.ToInt32(minStr)" - while nobody writes code in this way in production this is exactly the way of coding endorsed by Codility-like programming challenges when you have 30 minutes to come up with a solution.

Re:How to win the coding interview by winsome on Tuesday May 31, 2016 @09:56AM (#11806500)
Maybe for someone with no experience in the desired language and minimal access to docs, but for someone that professes a knowledge of C# 6 they ought to at least know about the `TimeSpan` class.

For anyone with the knowledge the person claimed to have, that code should boil down to something more like TimeSpan.Parse($"{hourStr}:{minStr}").TotalMinutes;

Re:How to win the coding interview by amorphid on Tuesday May 31, 2016 @12:33AM (#11804580)
Some reasons against a 1 week working interview:

* It can take up to a week just to get someone ramped up with access to things in many environments (setting up accounts, configuring dev environment, etc.) It's not free to create and disable a dev's access.

* Most places I've seen aren't set up to ramp someone up in a week. I think Pivotal Labs gives people a try for 3 week contracts, and they have a culture of ramping up new hires via pair programming in XP environment.

* You'd only be productive in an environment where you are already familiar with the tools they are using. If they're using Erlang, and you're coming from Java, you simply couldn't do much with Erlang in a week.

* Many places can't/won't put you to work without you passing a background check.

* Candidates who already have a job aren't likely to be in a position to take a week off to work for someone else.

Re:How to win the coding interview by jacalata on Tuesday May 31, 2016 @04:47AM (#11805465)
Pivotal Labs definitely doesn't require a 3 week contract before hiring, and it never even came up as a theoretical option when I interviewed with them and got an offer last year.
Re:How to win the coding interview by amorphid on Tuesday May 31, 2016 @08:35AM (#11806159)
Gotcha. Maybe the one example I am remembering is a special case, or that person simply didn't work out after three weeks.
Re:How to win the coding interview by dimino on Tuesday May 31, 2016 @12:40AM (#11804603)
You make a good point, but if I'm getting to pick my ideal work environment though, it's one where I can get ramped up and contributing meaningfully in a week.
Re:How to win the coding interview by EpicEng on Tuesday May 31, 2016 @01:14AM (#11804736)
If I'm working in my ideal work environment, the problem we are trying to solve is too complex to understand fully within a week.
Re:How to win the coding interview by dimino on Tuesday May 31, 2016 @01:52AM (#11804879)
Different strokes, I suppose.

Also "understand fully" isn't "can contribute to a sub-problem meaningfully".

Re:How to win the coding interview by gedrap on Tuesday May 31, 2016 @03:17AM (#11805185)
>>> I have 10 years experience with references. I have code that I've built, deployed to production still running today. I have cultivated my own clients, gathered requirements and built something that delivers business value.

I don't really agree with this statement.

The truth is that there are a lot of folks with 10+ years of experience who wouldn't even pass as junior devs at many places. I've seen people with 10+ years of experience rolling out their own web frameworks (and definitely not good ones) every year or two, developers who have never written a single unit test (they don't see the point of it; also the software there was the most bug ridden product I have ever seen, surprise surprise). Their employers were not technical at all so were relatively happy with the results.

You wouldn't marry a person after knowing them for a day, just because someone said that he/she is a lovely person, would you? Same here with hiring.

But hiring is a 2-way street. If you completely disagree with the hiring procedure at a company, then you are probably not a good fit, and that's fine :)

Re:How to win the coding interview by BinaryIdiot on Tuesday May 31, 2016 @04:36AM (#11805427)
> The truth is that there are a lot of folks with 10+ years of experience who wouldn't even pass as junior devs at many places.

Sure but this really has nothing to do with the parent's post. The parent said they have references and the experience and code in production. All of this is verifiable short of, say, DoD contract work.

I doubt you have worked with folks with 10+ years of experience who wouldn't pass as junior developers who also had references and verifiable code running in a production environment (and if you did I would imagine that's a fluke negative hire).

> But hiring is a 2-way street. If you completely disagree with the hiring procedure at a company, then you are probably not a good fit, and that's fine :)

Considering almost every technology company hires the same way and the employees typically have the "I went through it so you have to do" attitude you're not really going to find another company that has a "better" hiring procedure. Your response is more facetious than realistic. If you want to be a developer you don't have much choice than to go through the system that has been studied to death and known to be flawed.

Re:How to win the coding interview by MustardTiger on Tuesday May 31, 2016 @10:46AM (#11806798)
>Sure but this really has nothing to do with the parent's post. The parent said they have references and the experience and code in production. All of this is verifiable short of, say, DoD contract work.

It has everything to do with it. References are completely useless unless you happen to be lucky enough to know one of their references well. A random stranger saying "Bob knows X" is just as useless as Bob telling me he knows X. The references opinion is likely worthless, I can't bet my business on it.

And how are we supposed to verify the quality of this in production code, much less its existence?

>I doubt you have worked with folks with 10+ years of experience who wouldn't pass as junior developers who also had references and verifiable code running in a production environment (and if you did I would imagine that's a fluke negative hire).

That's easily 95%+ people with 10 years experience. Everyone has references, that is not something that is hard to acquire or meaningful in any way. Wordpress is running in production all over, I sure as hell wouldn't want to hire any of the people involved in it.

Re:How to win the coding interview by BinaryIdiot on Tuesday May 31, 2016 @02:03PM (#11808589)
References are all about verifiability otherwise it's just a random person saying something about another person; without context a reference is useless. You need to find a way to verify them which I'll admit is hard but without that they're completely useless.

Open source is usually the best indicator here as they can literally point you to code they worked on.

> Everyone has references, that is not something that is hard to acquire or meaningful in any way.

A literal reference without context isn't useful. That's why, in my original text I caveated it with verifiable code running in a production environment.

> Wordpress is running in production all over, I sure as hell wouldn't want to hire any of the people involved in it.

Ouch. It's not the greatest code but they made something, it worked and it's been scaled all over the place. Seems like they could have some solid people involved in it in my opinion.

Re:How to win the coding interview by MustardTiger on Tuesday May 31, 2016 @09:51PM (#11811608)
>You need to find a way to verify them

Such as?

>That's why, in my original text I caveated it with verifiable code running in a production environment.

Again, how do you verify that? Much less the quality of that code?

>It's not the greatest code but they made something, it worked and it's been scaled all over the place

The bar for hiring here is not that low. "I wrote some horrible buggy crap that is full of security holes and has cost millions of dollars" isn't a good sales pitch.

>Seems like they could have some solid people involved in it in my opinion.

The code says otherwise.

Re:How to win the coding interview by richforrester on Tuesday May 31, 2016 @12:50AM (#11804646)
Yes. Unless you're not the only person we're looking at hiring. We're not going to pay 10 people for a week and hire just one. We'd rather we get a sample by seeing you do some work on a whiteboard, and make some cuts right then and there.

In other words: yes, that's a better way for you to prove yourself. No, we don't have the resources for this approach.

Re:How to win the coding interview by enraged_camel on Tuesday May 31, 2016 @01:10AM (#11804722)
You don't want to pay 10 people for a week. You want to pay one person at a time over a 10 week stretch. That way, you can evaluate each candidate independently and hire the best one. This is undoubtedly a better approach than doing a bunch of coding interviews, so you should have a strong incentive to make sure you have the resources for it. After all, you want to minimize the risk of hiring mediocre people and maximize the chances of hiring really good people, right? The latter will pay for themselves tenfold.
Re:How to win the coding interview by EpicEng on Tuesday May 31, 2016 @01:34AM (#11804811)
I don't know where you work, but I have never had the luxury of 2.5+ months to get a position filled if we can help it (and it's silly to assume that the work required behind the scenes to get this all working would result in no gaps between candidates, so more than 2.5 months).

I also don't typically have the luxury of having great candidates in front of me who will wait multiple weeks to get into some weird one week eval (and they usually have a job already, so how are they going to get away for a week?). This is a time consuming and expensive proposition which would require buy in at multiple levels from multiple departments and would probably end up not working out so well.

Re:How to win the coding interview by p4wnc6 on Tuesday May 31, 2016 @11:06AM (#11806925)
I've never worked in any company that was able to fill any position faster than 2.5 months. Everyone clamored that we needed to fill positions fast, but then endless, nauseating political debates about minutiae on resumes and tiny flaws during in-person interviews took over, and it would just drag on.

I once was taken almost completely away from my engineering duties for a period of a whole month to help almost full time with what was a "critical" position that needed to be filled "now". A year and half later, when I decided to leave that company, they still had not hired for that position, and had an endless list of why every candidates didn't make the cut (and we had interviewed some excellent candidates who got thumbs up from all of the technical staff who had interviewed them).

It's different everywhere, but in general for a competent tech worker with about 3+ years of experience, I'd say you're looking at at least 6 months to find someone, probably closer to a year, not because there fails to be a supply of good candidates, but because that's just the time penalty for internal politics.

While this particular anecdote happened at an established firm, I experienced nearly the exact same thing in start-ups as well, literally the same political bullshit excuses used to reject otherwise great candidates even when we were "desperate" to hire someone.

Re:How to win the coding interview by richforrester on Tuesday May 31, 2016 @02:42AM (#11805066)
Thank you, this was almost exactly what I was going to respond with. My only addition:

"Alternatively, we can write/review some code on a whiteboard."

Re:How to win the coding interview by enraged_camel on Tuesday May 31, 2016 @03:18AM (#11805187)
It's well documented that whiteboard exercises are terrible for evaluating candidates. A lot of people, developers especially, don't perform well under pressure (stress reduces cognitive ability). Not only that, but you will also alienate a great many experienced candidates.

If you are OK with all that, fine I guess. But I thought it was widely agreed upon that the software industry needs better hiring practices.

Re:How to win the coding interview by efaref on Tuesday May 31, 2016 @06:07AM (#11805683)
If by "well documented" you mean "lots of people have whinged about it at great length", then I guess you're right. It's also a "tried and tested" method, too, so it's got that going for it.

I think if you approach them correctly (like the author suggests), then actually they're fine for their intended use. (Not perfect, but this is the real world, nothing's perfect).

If you can't cope with scrawling some pseudocode on a whiteboard because that's "too much pressure" then you're going to really struggle when a deadline looms and we "absolutely must get this code out to the customer by Friday because a $50M contract is on the line."

Re:How to win the coding interview by vonmoltke on Tuesday May 31, 2016 @10:30AM (#11806700)
> If you can't cope with scrawling some pseudocode on a whiteboard because that's "too much pressure" then you're going to really struggle when a deadline looms and we "absolutely must get this code out to the customer by Friday because a $50M contract is on the line."

First, "scrawling some pseudocode on a whiteboard" and "we absolutely must get this code out to the customer by Friday because a $50M contract is on the line" are not the same thing and it is fallacious to use performance on one to infer performance on the other. "Stress" is not some universal feeling that differs from situation to situation only in amount. It has types, which different people handle differently.

Second, related to my response to a sibling comment, if "we absolutely must get this code out to the customer by Friday because a $50M contract is on the line" has a high enough probability of occurring that it is worthwhile to screen candidates for ability to handle this, your company is fundamentally broken and you are trying to use your hiring to compensate for the real problems.

Re:How to win the coding interview by xentronium on Tuesday May 31, 2016 @07:06AM (#11805838)
> If by "well documented" you mean "lots of people have whinged about it at great length", then I guess you're right. It's also a "tried and tested" method, too, so it's got that going for it.

You are wrong. Just because it's most used currently doesn't mean it's better. And it is actually well documented.

@tokenadult posted this numerous times: https://news.ycombinator.com/item?id=4879803

Re:How to win the coding interview by EpicEng on Tuesday May 31, 2016 @04:08PM (#11809765)
What do you mean by "well documented" exactly? Are you referring to the numerous blog posts where people in the industry complain about it? I wouldn't call that extremely convincing.

I understand that some people get stage fright, but I'm not expecting them to come up with a perfect solution; I'm only trying to get an idea of how they think (and whether or not they can actually write code). If they can't do this sort of thing in front of a small group then how are they going to perform in group meetings? Are they just going to sit quietly in the corner the entire time?

I can't have that either, and I need some sort of measuring stick. I'd rather lose a good candidate than take on a bad one.

Re:How to win the coding interview by TheCoelacanth on Tuesday May 31, 2016 @10:43AM (#11806779)
Admittedly, whiteboard exercises are not good, but what better alternative is there that will not take an order of magnitude more time?
Re:How to win the coding interview by ori_b on Tuesday May 31, 2016 @09:02AM (#11806261)
> A lot of people, developers especially, don't perform well under pressure (stress reduces cognitive ability).

A lot of places value people who work well under pressure. (A bad push taking down all the server's I'd stressful)

Re:How to win the coding interview by vonmoltke on Tuesday May 31, 2016 @10:20AM (#11806646)
Meaning a lot of places have shitty processes and architecture and try to compensate by hiring people that fit their broken system. Case in point: having an architecture so fragile that a bad push is capable of taking down all your servers.
Re:How to win the coding interview by sokoloff on Tuesday May 31, 2016 @12:40PM (#11807624)
Trivial to have a breaking DB change or a software push where the only part of the app that works is the little part that tells the load balancer, "yep, I'm alive and healthy; send some traffic my way".

There are probably way more successful (100-million to couple billion dollar revenue) companies that can be brought offline with a bad push than can't.

Re:How to win the coding interview by ori_b on Tuesday May 31, 2016 @01:36PM (#11808294)
Or a load balancer push that ignores the 'yep, I'm alive and healthy' bit and sends traffic anyways.
Re:How to win the coding interview by EpicEng on Tuesday May 31, 2016 @04:10PM (#11809788)
Oh please. Even the best systems will have issues, and there will always be high pressure situations, regardless of the competency of management. It shouldn't be a way of life, but it's simply not practical to expect easy sailing at all times.
Re:How to win the coding interview by ffn on Tuesday May 31, 2016 @01:40AM (#11804834)
> evaluate the candidate

But candidate evaluation is not an objective business, one company's perfect candidate might be complete trash at another firm. A company's interview process then is necessarily a reflection that company's character, culture, and attitude just as much as it is a process to find potential employees.

For example, your suggested hiring process of doing essentially an extended homework assignment might be great for a firm who doesn't care about "hiring the best", "building the elite team" or whatever, and instead wants to just assemble a ragtag team of misfits who trust and work well with each other to get things done.

Meanwhile, the Silicon Valley standard Googlesque hiring practice of using timed tree-inverting-list-o(log n)-optimized-talk-through-what-you-are-doing-(oh-90%-of-our-devs-use-your-oss-but-you-dont-remember-red-black-trees-so-fuck-off) algorithm questions to pinpoint the most academically smart candidate is perfect for companies who want to hire the "smartest programmer" to create a culture of intelligence oneupmanship to drive "innovation".

And unless one happens to be in a situation where one absolute needs a job right away, a candidate could really glean a lot about a potential company's direction and culture through just how they conduct their interview, and decide if this is, indeed, a place where one could do one's best for the company and continue with the application or apply elsewhere.

Re:How to win the coding interview by dmoy on Tuesday May 31, 2016 @02:44AM (#11805073)
90% of devs there don't use his software, and we have no idea why his application was denied :/
Re:How to win the coding interview by MustardTiger on Tuesday May 31, 2016 @10:48AM (#11806806)
>(oh-90%-of-our-devs-use-your-oss-but-you-dont-remember-red-black-trees-so-fuck-off)

I use tons of open source software written by people I would never consider hiring. "You use something I wrote therefore I am good" is not a reasonable assumption.

Re:How to win the coding interview by nilkn on Tuesday May 31, 2016 @01:00AM (#11804685)
Out of curiosity, am I supposed to take an entire week of PTO in order to undergo such an interview process while currently employed? Because I can't really think of a single company I'd be willing to do that for.
Re:How to win the coding interview by modeless on Tuesday May 31, 2016 @01:01AM (#11804687)
That's great of you to offer as a candidate. However, from the interviewer's side, I can't ask candidates to do this. The people I want to hire are already busy. They don't have a whole week to devote to my interview process. Not even if I pay them for it.
Re:How to win the coding interview by ori_b on Tuesday May 31, 2016 @09:17AM (#11806321)
I have better things to do than spend a few months of PTO interviewing with multiple companies. This won't fly with me, and I doubt it will fly with many people that are currently employed.
Re:How to win the coding interview by redcap on Tuesday May 31, 2016 @12:44AM (#11804618)
What I've seen suggested elsewhere is having publicly viewable code on github or the like - that would effectively be your coding resume and evidence of your ability.
Re:How to win the coding interview by andyjdavis on Tuesday May 31, 2016 @12:56AM (#11804671)
True but it is not that hard for someone to fake that if they really want to. That said, faking history in github likely takes enough technical ability that the person could probably do a decent job programming if they use their powers for good.
Re:How to win the coding interview by zeemonkee3 on Tuesday May 31, 2016 @02:06AM (#11804919)
Just ask them simple questions about their code. "Why did you use a class here? What does this function do?". Or even what motivated them to do the project or what the hardest challenges were. It should be pretty clear whether they're the real deal or not.
Re:How to win the coding interview by pmiller2 on Tuesday May 31, 2016 @01:37AM (#11804822)
I wouldn't be surprised if there's a pre-baked script out there that clones a repo and rewrites all the commits with a different author and committer.
Re:How to win the coding interview by DigitalSea on Tuesday May 31, 2016 @02:27AM (#11805007)
I have done what you have proposed and it worked for my latest job (2 years and counting). I flat out refused a coding interview. I openly said, in my experience as a developer, great candidates fall through the cracks because they fail under a controlled environment which does not reflect the real world. They actually agreed with me.

I came in and did a one week trial, I brought in my own computer, they gave me access to a repository and a task list, told me to do what I could in the week and ask questions. Arguably, the experience was great. I was able to not only see if I wanted to work for this company, but what the people are like and what kind of problems I would be solving. It was a great way for the company to see if I got along with their team and if they liked me as a person.

Being a developer is half knowing how to code and the rest is whether or not you are a match personality wise for the company. You might be smart, but can you get along with others and work in different situations? A palindrome function or FizzBuzz during a coding interview can't tell you everything about a developer.

You know what else is great? I came onboard as a senior developer, after a year, I was running my own team of 2 other developers. Then something greater happened, I managed to change the way the company hires developers. We do the initial screening which is just a chat to see if their skillset matches the role, then we reduce the list down and bring them in to pair program with someone.

It works so well. Also what is cool is that the two developers we have brought on since I started were hired after great work performances during their week trial/interview.

Re:How to win the coding interview by kriro on Tuesday May 31, 2016 @03:05AM (#11805141)
Let me add a somewhat unrelated side note since you have some say in the new hiring process which is awesome btw. and the company sounds like they "get it"...

Bring your own device should always be understood as a security tradeoff. Especially if it's someone who is auditioning for a job (I'm sure you're aware of that but can't hurt to point it out).

Re:How to win the coding interview by tigershark on Tuesday May 31, 2016 @04:28AM (#11805404)
It's actually illegal in all the contracts that I ever had to work for someone else while you are employed for a company. And even if it was legal I would never lose a week salary for some fancy interview that takes a week, plus all the time that it takes to test the other n-people to have an answer.
Re:How to win the coding interview by arethuza on Tuesday May 31, 2016 @05:48AM (#11805628)
Having a contract saying that you shouldn't do something doesn't make it illegal it just means you are violating the terms of the contract. Which if you are leaving anyway might not be that big a worry.

Also, particularly with employment contracts, just because something is in the contract doesn't necessarily mean it is enforceable.

Re:How to win the coding interview by iSnow on Tuesday May 31, 2016 @05:03AM (#11805514)
> I would never lose a week salary for some fancy interview that takes a week

I'd actually love to do that. The company I work for currently presented itself in a very professional light and all the questions I had were answered promptly and professionally. No red flags.

Only when I started work, I noticed immediately their code base contained unfixed bugs, tests were not up to date and the databases (so called data-warehouses) were a mess. Unfortunately, the only real good developer was on the interview and answered my questions.

During a one-week stint, I'd have discovered enough bad practices that I would have declined the job.

Re:How to win the coding interview by rimantas on Tuesday May 31, 2016 @10:04AM (#11806546)
And after ten stints like this you'd find out that there is no place without a problem.
Re:How to win the coding interview by ionforce on Tuesday May 31, 2016 @08:52AM (#11806230)
How did you have the bandwidth to work there for a week?
Re:How to win the coding interview by Bahamut on Tuesday May 31, 2016 @01:27AM (#11804791)
Most good candidates wouldn't put up with that situation (1 week contracting) - also, years of experience can vary drastically. I recently interviewed a candidate with over 15 years of experience, predominantly in the backend, yet he didn't really have much experience scaling systems. He checked out in all ways until we drilled down into scaling issues.
Re:How to win the coding interview by agentultra on Tuesday May 31, 2016 @10:29AM (#11806694)
> I'm tired of companies asking me to code at their interviews.

I get that. I am too.

I'm around 13+ years of experience. I have contributions to major open source projects, have given talks at a few conferences, write about my experiences on a blog... it doesn't matter. I've ran into a few interviewers who take a few minutes before the interview to skim my blog. Once I ran into someone who actually read a few posts and saw a talk I've given (always a boon).

If you really want to get a sense of how I think and what my code looks like it's out there in the open. Few people will bother to look.

Thankfully I've done enough interviews that there are some patterns I can share. Here's my unofficial guide to acing programming interviews:

1. Be honest. Don't put something on your resume because you think it will make you sound good. Yes the first screen is just keyword bingo... but at some point you might make it to a technical interview with someone who hates it when people do this and will make a point of asking you obscure questions about the ANSI C standard. If you've written a few small C programs or done a few tutorials you don't know C -- you've just used it. We tend to over-estimate our abilities which is why interviewers don't trust resumes. But if you want to get a job doing more C don't be afraid to put that out there.

2. Whiteboard coding is stupid. Instead learn logic and predicate calculus. Learn to take a written or oral description of a problem and work out what the constants are and write out an invariant or two. Use pseudo-code. Pretend you are a caricature of a white-haired professor teaching a class... write out the problem, go on tangents, explain your reasoning in steps. Write pseudo-code only if pressed.

3. Coding. Long before you start interviewing start a repository. Pick the language you're strongest in and work out the following problems: a function to detect a palindrome, a function to detect an anagram, a function to find the Nth number of the fibonacci sequence, a function to generate the list of numbers of the fibonacci sequence, and fizzbuzz. Try to come up with more than one solution to each problem. Re-type them out. Commit them to memory by rote practice. Work out problems on coding practice sites and add the most popular, boring ones to your repository. As you interview add questions you come across to your repository. Practice the most common ones. Commit them to memory. This is probably one of the most inane practices in hiring but it's also one of the easiest to overcome. 90% of interview coding problems are regurgitated Google searches for interview coding problems.

4. Prepare a list of questions to ask the interviewer before hand. At some point they're going to ask you if you have any questions for them. Grill them hard. What makes them excited about their job? What's the hardest problem they've had to overcome? What is their greatest failure? What did they do about it after? What is the most common problem they expect you to encounter in this role? Etc, etc. Know who you're talking to -- save this for the technical interviewer whom you'll likely be working alongside/for.

Before you know it you'll be done. You might get an email or a phone call letting you know whether you made it to the next round or whatever. You may not make it.

The important thing to remember: It's not personal, it's not pervasive, and it's not permanent. Remember that every person you encounter is living a life and story that is every bit as complex and deep as yours. There are a number of possible circumstances affecting your position that you have very little control over: it's not your fault if you don't ace every interview as you likely won't despite how hard you try. If you're persistent you'll eventually find something.

Happy hacking.

Re:How to win the coding interview by judahmeek on Tuesday May 31, 2016 @06:56PM (#11810927)
Some really solid advice.
Re:How to win the coding interview by jimbokun on Tuesday May 31, 2016 @12:25AM (#11804562)
Sure, but some developers with a job already might prefer the interview.
Re:How to win the coding interview by gimpster on Tuesday May 31, 2016 @01:41PM (#11808349)
This reminds me of "smart and gets things done". Your idea is to test whether people can get things done. An interview can test how smart they are. Both are important.

I've seen web developers with years of experience delivering successful projects who turned out to be terrible programmers. In this situation, it is nearly always because they're not smart enough or because they have an anti-intellectual outlook on life ("I found this on stack overflow, it works, I don't understand it in depth but it's good enough for me" or "why would I know that, I never needed it") or often both. They were ok churning out 4 month projects one after the other or maintaining some business web site for years, but when you have them working on difficult and complex problems, their abilities turn out to be lacking and the brilliant kid with much less experience turns out to be much more useful.

Re:How to win the coding interview by grey-area on Tuesday May 31, 2016 @01:57AM (#11804894)
From the perspective of a hiring company, say they have 5 final candidates. Suggesting a 1 week placement will not be practical either for most of the candidates (who still have their old job) or for the company (who has real work to do and not 5 weeks of on-boarding). Also to compare candidates they need them trying the same thing, not 5 different things.

I think a few hours discussing code is a small sacrifice for a fairer, more equitable interview process.

Re:How to win the coding interview by kriro on Tuesday May 31, 2016 @02:59AM (#11805121)
This is a decent solution if you are a freelancer or between jobs or family free and able to relocate short term (you could do it remote but job interviews if you actually work on premise should also be on premise to some extend). If you're currently holding another job it's pretty tough as you'd essentially have to take a week of vacation time or do all the work remote.
Re:How to win the coding interview by BinaryIdiot on Tuesday May 31, 2016 @04:30AM (#11805411)
While I agree with your sentiment entirely I think you idea is faulty. Too much up-front cost for the employer and high risk for the employee if you need that job. I would like to see a short homework assignment which is then used to work with the interviewee. At least in some form (idea needs refinement).
Re:How to win the coding interview by allsystemsgo on Tuesday May 31, 2016 @11:28AM (#11807085)
Couldn't agree more. It's getting ridiculous.
Re:How to win the coding interview by krisgenre on Tuesday May 31, 2016 @12:32AM (#11804578)
This is the perfect and ideal process but unfortunately hard to scale.
Re:How to win the coding interview by andersonmvd on Tuesday May 31, 2016 @12:35AM (#11804587)
Regarding scaling: should we really hire developers as we scale servers? I don't think so.
Re:How to win the coding interview by EpicEng on Tuesday May 31, 2016 @01:37AM (#11804818)
Forget scale; I don't think it's practical for even one candidate.