This sounds like a good startup idea: A certification agency where they put you through the works, measuring your ability to write code, solve various challenges, complete complex projects, etc. Then they can issue a certificate to those that pass their examinations. Maybe in addition, they can offer training in various topics, include periodic assignments during those training periods, then have several days of mons…
Ask HN: Is it now common to ask for “full” applications as part of interviewing?
31–40 of 77 posts
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#32I hope this remains the case, as 1) they are an enormous time suck for the applicant, and 2) demonstrate abilities that a qualified applicant could become proficient at quickly. Qualification for a position requiring these abilities can be assessed in a way that is not so one-sided against the applicant.
Related: https://alwaystrending.io/articles/tech-interview-torture-ch...
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#33Ideally, when I'm given such a test I should be able to predict my success at completing it well enough to know whether it is worth my time. There could, of course, be unforeseen problems, but I should be able to judge the likelihood that spending the time to complete the exercise will get me the job. This means that cultural expectations are expressed up front. Do you expect the job applicant to adhere to your company code style guide or expect unit tests? I'd assume the latter is a frequent expectation but it doesn't hurt to mention; practices vary greatly from company to company so a reminder could be useful. Or maybe you write a lot of functional JavaScript on your team, and want to know if a candidate is familiar with that style. If you reject a candidate because they didn't match your preferred style but didn't ask for that, you're likely wasting my time and yours.
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#34It'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".
I actually don't mind the 45 minute automated screens that are outsourced to a code screening vendor -- my experience is that when the in-person interviewers see the results of that they are able to jump into more meaty questions instead of FizzBuzz. It's a net improvement for everyone's time.
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#35Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#36Ask a developer to write some actual code to prove that they can do the job they're being hired to do -> developers complain about having to demonstrate that they can do the job they're about to be hired to do.
There's a legitimate question here about how extensive of a project is necessary to demonstrate that you can, in fact, write code effectively. But this is basically what we've been clamoring for for years, companies abandoning pressure cooker interview room gotcha-questions on whiteboards.
The work sample test is one of the most effective ways of evaluating a candidate's fitness. What do you expect an prospective employer to do to determine if you can do the job, if not write some code?
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#37I can't imagine paying someone to interview though. Both parties are spending time (and money) on the interview already and if you don't want the job enough to put in a day getting it, to me that's a signal that you wouldn't be very interested in the problems we're working on.
I do sympathize though and agree that interviews still suck (for both sides).
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#38This sounds like a good startup idea: A certification agency where they put you through the works, measuring your ability to write code, solve various challenges, complete complex projects, etc. Then they can issue a certificate to those that pass their examinations. Maybe in addition, they can offer training in various topics, include periodic assignments during those training periods, then have several days of mons…
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#39I finished it in a day and a half; decided to use Meteor since I never used it before and figured it'd be a good time to dabble in it.
It was by far the most enjoyable part of the application process. And I think its the best indication of a developer's ability. Real-word application of the knowledge that you will probably be using 90% of the time (as opposed to theory and logic puzzles).
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#40I've stopped interviewing with companies that do this. Take home interview "challenges" take up a lot of time and resources. Most of the ones I've gotten have been prototypes/MVP type deals. + You're asking me to spend almost a week of my time, for free + I have similar examples on my Github + I'm not usually allowed to share the solution Sorry, but if you can't look at my significant github profile and figure out if…
Not everyone has a "significant" github profile. Actually the minority of people has such a thing. So many reasons for not having one. Current employer's policy, having a family, having non-IT hobbies, etc pp. Also just having such a profile doesn't necessary proof that you can solve the company's problems, because just looking at solutions of arbitrary problems doesn't give you any information about the constraints of the problem, how you solved them and it also doesn't put your solution to this problem next to solution of the guy sitting one desk away that solved the same problem in the same amount of time under the same conditions.
(removed a stupid passive aggressive statement here, sorry folks)