News for hackers. Stuff that matters.
Re:I was asked to crack a program in a job interview by michaelchisari on Wednesday September 17, 2014 @05:40PM (#8332518)
> Real-life tests are THE best thing to send job candidates

I agree, but only if you're allowed to use references/google/etc and given a reasonable amount of time to accomplish it. I've had a "real-life" test where I wasn't allowed to verify or look up information, or where I'm giving a very short time to execute, and I've always thought those were absurd.

The idea that you would ever have to do something like this in a bomb-diffusing type of scenario with no internet and a ticking clock, would only test if you have already solved the problem before, not whether you could investigate a new problem.

Re:I was asked to crack a program in a job interview by icelancer on Wednesday September 17, 2014 @06:45PM (#8332780)
>I agree, but only if you're allowed to use references/google/etc and given a reasonable amount of time to accomplish it. I've had a "real-life" test where I wasn't allowed to verify or look up information, or where I'm giving a very short time to execute, and I've always thought those were absurd.

Employers that do this are ridiculous. As are educators, too. What is this, preparation for when coders are kidnapped by terrorists and forced to recite how to tar/untar stuff on command? (relevant xkcd, of course)

Re:I was asked to crack a program in a job interview by michaelchisari on Wednesday September 17, 2014 @07:08PM (#8332862)
> Employers that do this are ridiculous.

In my experience, they're usually startups or smaller companies that are trying to "copy google" in their hiring practices, but don't fully think out how they're doing it. It's not a good sign.

Re:I was asked to crack a program in a job interview by hueving on Thursday September 18, 2014 @06:01AM (#8334450)
Well Google does it too. Their 'gang bang' interviews are notorious for weeding out people that don't perform well under short term pressure like that. "just write an algorithm for a stack on this whiteboard with a big O complexity analysis and memory usage pattern in 15 minutes while we all stare at you. What? You don't work well like this? Well this is how elite Googlers work all of the time so GTFO"
Re:I was asked to crack a program in a job interview by redstar504 on Thursday September 18, 2014 @05:51PM (#8337841)
To be fair, a lot of people are capable of becoming that type of employee after gaining comfort at the company, and after building relationships with their co-workers. To expect someone to do that in front of strangers while under pressure doesn't necessarily correlate with a programmer who can evolve into such a person.
Re:I was asked to crack a program in a job interview by eyko on Thursday September 18, 2014 @06:36AM (#8334536)
> What is this, preparation for when coders are kidnapped by terrorists and forced to recite how to tar/untar stuff on command?

:-D you never know!

Re:I was asked to crack a program in a job interview by RevRal on Thursday September 18, 2014 @01:22PM (#8336423)
>Employers that do this are ridiculous.

Unless they are trying to hire a mentat.

Re:I was asked to crack a program in a job interview by eyko on Thursday September 18, 2014 @06:45AM (#8334557)
I've been in two interviews where they asked me to code without googling or looking at the reference.

Personally, I think it's as absurd as writing shell scripts on a computer with no `man`, or without being able to refresh your memory with `<command> --help`. Good luck with that!

I was in an interview where they asked me to configure specific firewall rules on a notepad with no access to a terminal, so I couldn't check man iptables for stuff like how to match certain sources/destinations hosts/IPs. And I was not too familiar with the opts (was it --dest, --dst, or -d? and how do calculate the network mask for this range of IPs?). It was also for a junior position so I thought they were taking a piss at me and simply told them so.

Re:I was asked to crack a program in a job interview by jtheory on Thursday September 18, 2014 @03:49AM (#8334169)
It's gets a bit complicated when your job candidates may find your test interesting enough that they post a complete walk-through of the solution online.

The candidate was kind enough to avoid posting the name of the company (to hopefully hide the walk-through from Google queries for "crack me hiring test company name", but an HN discussion might then arise around the walk-through, in which the company would be named, and well, there goes your test.

It's hard to accurately run "take home" tests when hiring because of just this.

Re:I was asked to crack a program in a job interview by Fuxy on Thursday September 18, 2014 @04:47AM (#8334280)
If you're not changing your tests on every interview batch you're doing it wrong.

You're asking a potential candidate to spend hours cracking your program but you can't be bothered to change it for each batch?

I expect any company applying this interview technique to at least put some effort into it and even then it pays off since a batch could contain hundreds of candidates and you only have to build the program once.

Re:I was asked to crack a program in a job interview by chrisbennet on Thursday September 18, 2014 @07:41AM (#8334689)
This ^ "You only get out of it, what you put into it." goes both ways - employers should expect to extend some effort if they expect their candidates to extend some effort.

I strongly suspected that sometimes goals of the person responsible for hiring are not quite aligned with the company they work for. Example:

Company's goal: Hire an exceptional candidate.

Lazy or overworked hiring manager's goal: Reduce the size of the stack of 1000's of resume's I have to go through using any means possible that will make it appear like he/she actually did the work to find the candidate.

"Lemme see, use keyword search to ditch the ones without 'Github' on their resume'. Now ditch the ones who don't have a college degree. Still some resume's left? OK, how about tossing the ones without a CS degree?"

Run a filter with enough conditions and you can get that pile down to nothing pretty fast. If that is still not enough filtering, ask the candidates to do something very time consuming. This a great way to weed out people who are very busy or exceptional at what they do and don't need to jump through your hoops.

Re:I was asked to crack a program in a job interview by lutorm on Thursday September 18, 2014 @03:46PM (#8337207)
The problem is that this makes it difficult to compare evaluations. If you want to have as objective an evaluation of candidates as possible, you need to subject them to exactly the same process.

I'm surprised they didn't make him sign an NDA for it...

Re:I was asked to crack a program in a job interview by aaronharnly on Thursday September 18, 2014 @07:41AM (#8334688)
What do you mean by "batch"? Most companies have rolling hiring.
Re:I was asked to crack a program in a job interview by warrenm on Thursday September 18, 2014 @12:36PM (#8336131)
this is true - but you're [generally] going to have a batch of candidates for any given position
Re:I was asked to crack a program in a job interview by Fuzzwah on Friday September 19, 2014 @11:40AM (#8340970)
Pick a unique keyword for it all and SEO the hell out of a site selling the walk thru.

Make it slightly wrong, or obviously fingerprinted.

Re:I was asked to crack a program in a job interview by kamaal on Wednesday September 17, 2014 @11:10PM (#8333482)
For any person who claims to have years of Unix experience, they can easily do anything they want using man pages. Though I agree with you on the general premise though. One must be allowed to look up information they need to solve a problem.

>>I've had a "real-life" test where I wasn't allowed to verify or look up information, or where I'm giving a very short time to execute, and I've always thought those were absurd.

You certainly haven't worked at major IT services firms here in India. I spent early part of working years (around 2006) coding by purely reading books and discussing things with folks on internal mailing list. Because only managers and levels above were allowed internet access.

>>The idea that you would ever have to do something like this in a bomb-diffusing type of scenario with no internet and a ticking clock, would only test if you have already solved the problem before, not whether you could investigate a new problem.

This is unfortunately true even for coding interviews. Most algorithm questions are impossible to answer unless you have rote memorized the algorithms and their implementations.

Re:I was asked to crack a program in a job interview by mjmahone17 on Thursday September 18, 2014 @12:50AM (#8333751)
If you have to give white-board coding interviews, the goal should be to have a question that's complex, potentially elegant and straightforward.

By complex, I mean the question should be difficult enough that you can't easily hold every parameter, case and step in your head: I want to see how you deal with situations that you have to mentally walk through and issues that you might lose track of.

By potentially elegant, I mean both brute-force and optimal solutions should be able to fit on a small whiteboard, without requiring more than 2-4 variable declarations and no more than a nested for loop (or some sort of recursion). The optimal solution shouldn't require putting together pieces that they aren't really expected to know/use, i.e. no more complex than arrays, maps, strings and ints, and any other "data structures" the candidate ought to know, given their background. For instance, if they claim to be a crypto expert, they should know how to use a black box that gives them private and public keys.

By straightforward I mean, you don't want the candidate to have to have an "aha" moment. If you're asking for them to write a max-flow variant, you'd better be explicit that you don't mind a really brute-force solution, or most of the interview will be spent trying to remember complex algorithms. Is the algorithm one that you can understand by walking through test cases/figuring out what steps you took in your mind to go from input to output? If it takes more than that, you're going to get a few false positives, i.e. "Wow she was great! No one's answered this so fast!" (because she just spent 20 hours doing this on a homework), and many false negatives.

Re:I was asked to crack a program in a job interview by thewarrior on Thursday September 18, 2014 @02:53AM (#8334044)
Do you still work at a major IT services firm ?
Re:I was asked to crack a program in a job interview by davidgerard on Wednesday September 17, 2014 @05:42PM (#8332533)
Yeah, this is an open-book test.

Of course, there's tests like user:B5Geek's, where the candidate gets a PC with a slightly-unplugged network cable and has to realise this fact.

Re:I was asked to crack a program in a job interview by michaelchisari on Wednesday September 17, 2014 @06:00PM (#8332621)
Yeah, but B5Geek's is a pretty entry-level thing. I've encountered whiteboard tests where you have to recreate an algorithm that someone spent their PhD thesis creating. It seems like a good way to find "geniuses", but it just isn't practical.

In a lot of ways, it's a matter of identity crisis for software developers. We're all, industry included, not quite sure whether we're mechanics, carpenters, architects or scientists.

Re:I was asked to crack a program in a job interview by aftbit on Thursday September 18, 2014 @12:03AM (#8333623)
I've taken a whiteboard test that asked me to come up with an algorithm that was difficult for me. I got the job even though my solution was horribly inefficient (and I knew it), and the interviewer later told me that the point wasn't to see what algorithm I knew - it was to see if I acted like an ass when I didn't know stuff.
Re:I was asked to crack a program in a job interview by lostcolony on Thursday September 18, 2014 @08:08AM (#8334760)
Not sure that's a good test either. When tasked to figure out something as part of a job, by a manager one knows and trusts, who takes feedback of "I don't know how to do this but I will investigate it", a person may act one way, whereas being tasked with someone's PhD thesis by a stranger on an interview may lead to a very different response.

I know I am far less tolerant of bullshit interviews than I once was, and would have far fewer qualms vocalizing what I'm thinking - "I don't know. If I saw this in real life I'd check Google, because it reads exactly like the sort of contrived problem used in interviews and thus is well documented, and likely solved quickly by those who have memorized it. I am not one of those. I'll take a stab at it now if you just want to see how I reason through it, but if coming up with an efficient, correct implementation is part of your criteria we can probably save both of us the trouble" - is that considered acting like an ass?

Re:I was asked to crack a program in a job interview by michaelchisari on Thursday September 18, 2014 @02:21AM (#8333974)
> it was to see if I acted like an ass when I didn't know stuff

Surely there's more efficient ways of evaluating that.

Re:I was asked to crack a program in a job interview by vegggdor on Thursday September 18, 2014 @05:38AM (#8334402)
On the plus side, it did take a stab at what algorithms he knew, too.
Re:I was asked to crack a program in a job interview by davidgerard on Wednesday September 17, 2014 @06:05PM (#8332635)
True. Testing for sysadmins is easier: you're after a way of thinking. So a competence test ("can you do what you claimed?") with a freeform "keep notes on your thinking along the way" is quite informative. You still need to interview, of course.

I confess I don't know how I'd apply this to developers. They pass fizzbuzz, OK - what do you do next?

Re:I was asked to crack a program in a job interview by vinceguidry on Wednesday September 17, 2014 @10:50PM (#8333423)
> I confess I don't know how I'd apply this to developers. They pass fizzbuzz, OK - what do you do next?

I know what I would do, just have a 10 minute conversation with them about technology. I can easily figure out just where a person is in regards to their development as a programmer just by listening to them talk about what they're paying attention to in the tech landscape. If they don't blink when I mention Hacker News, I know they're on the right track. Do they know what Go is, or Haskell? Do they have an opinion about Node.js?

These criteria are intended to gauge motivation and enthusiasm in the absence of an impressive track record. If they're capable but not highly motivated, then that's fine so long as you're only hiring them to do stuff inside their comfort zone. We have a Microsoft guy just like that. If they're motivated but not capable, then with coaching they'll be able to do anything. The best way to discover someone's motivation is to get a gander at what they're thinking about when they aren't working.

If you're looking for someone who is motivated and capable, you can eventually find someone like that, but you'll have a hell of a time keeping them. Developers have so many options these days that you need to have at least 3 of: competitive salary, decent perks, fun work environment, a glamorous field; in order to hold on to them for longer than a year.

Most companies are lucky to manage one, if they're very lucky two. Since salary is often the easiest thing to manipulate and honestly the most important to the employee, err on the side of paying too much. It's expensive but not having competent developers is far more expensive.

Re:I was asked to crack a program in a job interview by davidgerard on Thursday September 18, 2014 @02:52AM (#8334040)
Not infallible - I could talk tech near-perfectly (I am a native speaker of BS), but I am most definitely not a coder pretty much at all - but a good start.
Re:I was asked to crack a program in a job interview by clarry on Thursday September 18, 2014 @08:25AM (#8334809)
Also, using HN and its fads as a measure of motivation sounds a little elitist. There are really awesome and motivated coders out there who couldn't care less about politics, mainstream tech media news articles, gadgets, Apple-does-this, Google-does-that, cool new language or JS toy of the week... these coders are likely focused on their code instead.

Programming is a wide field, there's much more to it than the front page discussions on HN can cover.

Of course, if you're looking for a Web developer to make "cool new stuff" for the latest fadgets..

Re:I was asked to crack a program in a job interview by vinceguidry on Thursday September 18, 2014 @10:35AM (#8335391)
You make light of web development, but that's driving the enormous demand for programmers in recent years and all of our salaries. I bumped my pay $20K when I took this job and I'm now asking for $30K more after a year. Most fields calcify after a few years and salaries level off as the managers do their thing. But making "cool new stuff" and the "latest fadgets" is still really hard. It might be the fashion industry, but business is booming.
Re:I was asked to crack a program in a job interview by rqebmm on Thursday September 18, 2014 @01:23AM (#8333852)
Speaking as an iOS developer who's had a hand in hiring, it's the same as the "slightly broken Apache and Tomcat" scenario someone posted for sysadmins. We ship people a slightly broken app with a few common-yet-googleable problems, then ask them to build a tiny thing on top of that and ship it back to us.

The ability to solve common problems acts as a good proxy for experience, If they can't google how to fix a retain cycle or a broken constraint, we know they probably don't know what they're talking about.

The ability to build a good, small system on top of the broken app acts as a good proxy for development talent. If they can't easily set up a dead-simple delegate to do an asynchronous web call, they can't hack as a mobile developer.

Most importantly, if they don't care enough about the job to take two hours to whip up a super-simple app, then we don't have to waste our time interviewing them.

Re:I was asked to crack a program in a job interview by orkoden on Thursday September 18, 2014 @10:38AM (#8335408)
For iOS developers I found that a good test was to download and parse some XML or JSON API of a web service and display the result in a UITableView. . It' surprising how many people can't accomplish this.
Re:I was asked to crack a program in a job interview by rqebmm on Thursday September 18, 2014 @11:00AM (#8335557)
Agreed! That's exactly the "tiny thing" we ask people to build.
Re:I was asked to crack a program in a job interview by michaelchisari on Wednesday September 17, 2014 @06:38PM (#8332753)
For developers that have the academics, but not the experience, I've always said that the industry needs to adopt the apprenticeship programs that other trades have. Where you do a mixture of work for the company, and trade schooling run by the industry to teach you the specific skills you need.

For example, an IBEW apprentice will do a lot of gruntwork on the job site. Pulling wire, for instance. But they'll get exposed to how things are done, to trade industry expectations, and what a project looks like from start to end. Part of the week, they spend in a classroom learning the specifics of their trade. Not just the high level theory, but the nitty gritty, based on real world applications and problems. This apprenticeship lasts from 2-5 years depending.

I don't see why this model wouldn't work really well with programming.

Re:I was asked to crack a program in a job interview by porpoisemonkey on Wednesday September 17, 2014 @06:47PM (#8332787)
Apprenticeship requires a constant stream of mentors. I'm not sure there is an ample supply of professional programmers who would be interested in taking on the responsibility of mentoring in addition to their full-time jobs.
Re:I was asked to crack a program in a job interview by smoe on Thursday September 18, 2014 @09:44PM (#8338623)
It really depends what those professionals are used to. I did an Apprenticeship as Software Developer in Switzerland. That is, 1 year of school followed by 3 years alternating between the company and the school. So once you start at the company you already have a viable amount of knowledge in programming, databases, networking, etc and supposed to be able to work on your own.

You don't get constant mentoring at the company, but can ask one of the developers or fellow apprentices when you're stuck with one of the tasks you get assigned. Or for example, any time a developer had a small task that he felt, I couldn't do by myself, or it was too time critical he just asked me to sit beside him and watch, listen and take notes while he did the work. How it works is different in any company but the outcome should be the same: real world experience on real projects with real clients and their time/budget constraints.

That means, once your finished and a professional yourself, it isn't a question of interest but a completely normal thing to help out the apprentices. Because that's how you got to the point where you are.

Re:I was asked to crack a program in a job interview by aianus on Wednesday September 17, 2014 @07:45PM (#8332939)
What would the programming equivalent of pulling wire be?
Re:I was asked to crack a program in a job interview by michaelchisari on Wednesday September 17, 2014 @07:52PM (#8332954)
Technical support.
Re:I was asked to crack a program in a job interview by click170 on Wednesday September 17, 2014 @09:42PM (#8333221)
This.

We may laugh, but starting in technical support gives you an idea of how your users are using your product, if your documentation is accurate and helpful, what the pain points for people not in the department you are destined for are, and gives you an idea of how the product works.

It also quickly weeds out the people who can't effectively communicate before they get to the programming team.

Re:I was asked to crack a program in a job interview by davidgerard on Thursday September 18, 2014 @02:54AM (#8334048)
We've been rotating the sysadmins through customer service. Not taking calls (our CS calls tend to be long and detailed, and a n00b isn't going to help), but being there for the CS people. It's been marvellously instructive. It also cheers the CS people that someone cares. Now we need to get the devs doing the same.
Re:I was asked to crack a program in a job interview by UrMomReadsHN on Wednesday September 17, 2014 @11:46PM (#8333579)
That exists, its called a co-op. I couldn't graduate without doing x months of co-op.
Re:I was asked to crack a program in a job interview by walshemj on Thursday September 18, 2014 @04:23PM (#8337422)
When did block release training or work experience start getting called co-op given that in various areas of the world a coop co-op means a cooperative like Mondragon.

I have only seen it (co-op) used in the last few years.

Re:I was asked to crack a program in a job interview by UrMomReadsHN on Thursday September 18, 2014 @09:43PM (#8338620)
Well I finished school longer than a few years ago and cooperative education (co-op for short) has been around since the early 20th century.

http://www.ceiainc.org/history

http://en.wikipedia.org/wiki/Cooperative_education

Re:I was asked to crack a program in a job interview by kamaal on Wednesday September 17, 2014 @11:40PM (#8333561)
>>They pass fizzbuzz, OK - what do you do next?

Algorithm tests only measure the number of man hours the candidates spend on career cup daily. Or how good they are rote memorizing things.

There are many ways to check how good a candidate is at doing their actual work. For instance you can take a candidate to a code review and see what kind of inputs they contribute to the discussion. This alone will give you good deal of idea on how well they understand code and quality. There are other ways, like say asking them to write unit test cases for a class- That would give a lot of idea on how they think with regards to breaking and fixing things.

One more way I have after doing basic checks is pair programming, or picking a totally new problem and working with the candidate to see how they think, how they work and how good their communication skills are.

There are many other ways too. Recently I've been given coding assignments for very practical applications, though those turn out to be a little difficult and time consuming. And at times the expectations are very high. Like asking the candidate to complete a whole application in very short times. It can be hectic with your current job, and a family. But generally those are a good indication of how good the candidate will do at their actual work.