I'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…
What if it's a coding challenge that is purposely timeboxed to 4-6 hours? At my previous job, we asked applicants to write a piece of software that would model the org chart for any given employee, enumerating their hierarchical relationships as well as their peer relationships. We may have thrown in an additional complexity or two, but we also removed a lot of requirements (no i/o or database, no user interface; we…
Ask HN: Is it now common to ask for “full” applications as part of interviewing?
41–50 of 77 posts
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#42Companies are NOT trying to get free work out of you. If they wanted to hook to a third-party API, it would be easier to use the API sample code. They are trying to save themselves hundreds of dollars in staff salaries and lost productivity, to interview a person who can't function in a realistic programming environment.
These are EXACTLY the sort of companies you should apply to if you really want a job.
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#43I'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…
What if it's a coding challenge that is purposely timeboxed to 4-6 hours? At my previous job, we asked applicants to write a piece of software that would model the org chart for any given employee, enumerating their hierarchical relationships as well as their peer relationships. We may have thrown in an additional complexity or two, but we also removed a lot of requirements (no i/o or database, no user interface; we…
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#44As some other commenters mention, and I feel the same way: if a company asks you to do this, they're asking for too much and I think it's fair to tell them that that is an unacceptable amount of work for an interview. I can kind of see this as fair only if you are going in as a more experienced dev but with no work examples, but in that case, it's simple enough to contact references to verify previous work and positi…
Usually these positions, and this field in general, pay well so I would think that people would want to go the extra mile to get the job. Also, you need to remember that employers take a risk with every hire. The cost of hiring and onboarding (and firing, too) are not insignificant.
If I was involved in the hiring process and someone expected to get paid as a contractor for their time spent as part of the interview process, I would not be calling that person back. If, however, a person expressed their displeasure at the amount of time it would take to complete the request given their current workload and schedule, I would probably be willing to work with them and try to figure out some middle ground that would serve both sides reasonably well. Of course, you also always have the ability to tell them that you think it's too much to request as part of the interview process and do not wish to continue the interview process as it would be a waste of everyone's time.
Given the hiring risk(s) and costs associated with it, I think it's extremely distasteful to seek to be paid as part of that process.
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#45Now if they are requiring you to spend more than 2 to 4 hours on a project, that is unacceptable imo unless the hiring company is willing to pay contract rates for the time.
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#46What I mean is some recruiter will say "we would like you to complete a coding challenge it shouldn't take any more than 2 hours to complete.' Then the feed back will come back that "the team was disappointed that you didn't implement features x, y and z."
The whole homework/project/coding challenge requirement has really become disrespectful in my opinion. Extremely vague requirements, arbitrary or unrealistic time constraints and then you are judged but not allowed to participate in any discussion about the code you produced.
And perhaps the height of absurdity is recruiters asking via email if you will complete a coding assignment. This is even before speaking to a human being to see if there might even be a fit.
The hiring process just seems to be becoming more broken all the time. Just refuse and say "No."
I think companies might really benefit from smoke testing their own hiring process in some blind fashion.
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#47This biases the companies towards their sample application at everybody in their funnel, even if they have far too many applicants, are not that motivated to fill the position, or potentially if they don't actually have an open position at all! This wastes a great deal of candidates' time without any real chance of an offer.
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#48This 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.
Doesn't that kind of go towards the "who wants it more" mentality? What's wrong with that? Maybe you and someone else are equally good coders, or maybe one of you is clearly better. Either way, the only thing the company should care about with a salaried position is the finished product, not whether or not someone put more hours into it. I think people all too frequently discount effort and desire when interviewing. People focus on who has some very specific skill set and experience rather than "does this person really want to work here in this position"? Or "is this the type of person we want to work with"?
You can work hard. You can work smart. You can be successful doing either, generally speaking. Do both, and you will usually be more successful than most others.
Plus, if it was a position that you really wanted, I would think/hope that it would be something that you would find yourself spending more time than expected, on. I know I would if I was in that position. If I didn't really care about the position or the company, I would not try overly hard, and I assume that would show. Which is yet another reason I think companies probably should do more of this if anything, not less.
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#49This 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…
Whilst I appreciate the tongue in cheek nature of this post, if merely having a degree was the answer, these types of application would not exist.
A Lawyer needs to pass a BAR exam in the state in which they expect to work, then maintain that certification (annual training requirements, etc).
Software throws around the term "engineer" a bit willy nilly, but if you look to other engineering disciplines there is a distinct certification meaning to Engineer as a title:
1. You have graduated with an ABET-accredited degree
2. You have passed the NCEES Fundamentals of Engineering exam
3. You have apprenticed for the necessary Engineer-In-Training period
4. You have passed your discipline's NCEES Professional Engineer exam
5. You maintain your Professional Engineer certification (annual training requirements, etc)
That certainly sounds like a good baseline. NCEES has a Software Engineering Professional Engineering exam today and can certify Professional Engineers in Software. If I never again had to do another whiteboard interview or take home programming assignment, I'd start working on my PE tomorrow.
What stops the Software Industry from recognizing distinctions such as a accredited degrees and PE certifications?
The software industry doesn't want to stop talented software developers from entering the market without a need for degrees and certifications, because that drives down labor costs. But that doesn't have to stop the industry from at least acknowledging the existence of degreed and/or certified engineers and eliminating some of the BS.
Re: Ask HN: Is it now common to ask for “full” applications as part of interviewing?
#50I'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…
What if it's a coding challenge that is purposely timeboxed to 4-6 hours? At my previous job, we asked applicants to write a piece of software that would model the org chart for any given employee, enumerating their hierarchical relationships as well as their peer relationships. We may have thrown in an additional complexity or two, but we also removed a lot of requirements (no i/o or database, no user interface; we…