Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Is it now common to ask for “full” applications as part of interviewing?

news.ycombinator.com

Post reply on HN
Print view View original

1–10 of 77 posts

Ask HN: Is it now common to ask for “full” applications as part of interviewing?

#1

Post by Futurebot »

Three companies (out of ten or so) I've interviewed with recently have all asked for something similar to the following:

- code

- integration with a third-party API

- installation of a number of third-party libraries (and the reading of their documentation)

- complete documentation for the code

- a test suite

- deployment instructions

The companies in question vary in their industry, tech stack, and focus.

Most of the time, take home coding challenges consist of a fairly well-understood problem and are basically souped up versions of fizzbuzz to gauge a) basic ability and b) abstraction/organizational skills c) style

Is this more common now? The interview process has become more stringent over the past 10-15 years in my experience, but this is the first time I'm being asked for things this complete and specific.

(As an aside: are we finally near the point where companies should consider paying developers to interview if they're going to be asked to spend the day coding, writing tests, and writing documentation? I.e., do free work)

Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?

#2

Post by Bahamut »

This is why I oftentimes dislike take home projects for interviews - they're extremely time consuming, or are biased towards those who can cobble things together quickly. I can do that too, but it's not without stress or time spent, and I know I would be competing against others probably willing to sink more time.

Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?

#3

Post by falcolas »

It's not yet ubiquitous, but it isn't uncommon either.

I had application go through such a coding test in lieu of a "biased interview process", but wouldn't pay. They also had integration with two third party services, and for a Go programming position they also wanted a REST interface implemented on RoR.

It's a great test for "passion", however; if your definition of "passion" is "unpaid overtime".

Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?

#6

Post by giobox »

It's been a while since I last interviewed, but I've wanted something like this for interviewing applicants at my own workplace. It strikes me as fairer to all parties, especially compared to whiteboard coding exercises.

I've heard of some companies doing exactly what you suggest - paying an appropriate amount to cover the few hours spent on the interview project.

I get that some will criticise this saying it takes up your free time, but I'd argue the common practice of memorising algorithm solutions for interviews is often an equally unproductive use of the interviewee's own time.

Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?

#7

Post by _dark_matter_ »

There was some discussion of this recently on r/cscareerquestions [0]. The general consensus there was this is too much, though a few people had seen it. Myself, I would have to really really love the company to consider doing it.

[0] https://www.reddit.com/r/cscareerquestions/comments/6bvmpf/a...

Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?

#9

Post by swalsh »

These tests infuriate me. I was given one once, thought I did well, received feedback from the recruiter that the employer "was unimpressed". I pressed for details (I did spend something like 2 hours on it after all!) and received none.

Struck me as extremely rude.

Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?

#10

Post by alaskamiller »

3 years ago, when I was hiring college-level hacker kids we would just ask the to hack out a web app (with or without our API). This was when dev boot camps were taking off and asking them to just build something was actually a much better understanding of them than white board tests.
Post reply on HN