There's bad interview practices, and then there's abuse.
Are we reading the same post? They want basically two API endpoints, one to receive a POST upload and another to return all the things that were uploaded. You could do this in Django (which they want you to use) in significantly less than 100 lines of code. It seems like an ideal little sandbox.
>...Authentication system that only allows authenticated users to upload photos but all users to view photos -Automated testing -Code coverage does not need to be complete, just generate that some critical functions of the system have tests attached to them. -Write-up on the systems design pattern choices
They are basically saying "make our entire product."
Even if they paid him to make this app it would stop being unethical but it would still be silly.
This "company" is
1) Not a company at all, just 4 cocky and extremely naïve college students who think doing a 3 month internship at Amazon makes you "one of the leading React developers in the world."
2) is asking "interns" to build their entire product before they even consider "hiring" them
3) Has a weird idea what "hiring" means because they won't even bother to pay people they "hire" for 3 months because they think expecting a paycheck in return for labor is "toxic."
What on Earth should we be doing, then?
You should accept that the process is going to cost you, and that there are going to be both false positives and false negatives.Trial periods solve false positives, and you eat the cost of onboarding someone and their 1st 3 months or whatever. It sucks, but make the decision and move on. If you have this happen multiple times, your interview process isn't rigorous enough.
To improve false negatives you need a mix of inputs in your interview process. One way to get this is long/multistaged interview, but you will lose people this way too. Accept that if you are asking an interviewee to do real work (e.g. real world code) independently you should pay them for the time, and know that you'll lose some good candidates if you ask.
The company in question is asking for someone to do actual work that they will use as part of the job interview, and then to work for free for 3 months, "non-negotiable".
You somehow think that is reasonable, and that anyone on HN who complains about it is simply whiny?
The same happened with this post. (Of course I think in this case the behavior is exploitative and abusive. But do notice that not all folks in the thread disagree with the practice. Unfortunately they’re getting downvoted for disagreeing.)
They want an HTTP endpoint that takes a file over POST. Then they want an HTTP endpoint that returns the list of files over GET. They would also like basic things like a way to take an auth token to check if you have permission to upload, some unit testing, etc.
If you think this is anywhere even near to the ballpark of "actual work that they will use in their product", you're insane. This is basically 95% Django boilerplate that an experienced Django dev would be able to type out faster than it takes me to write this comment. To suggest that "write and read a .jpg" is somehow a part of their system that they're outsourcing (rather than the kind of thing you can find written out in dozens of Stack Overflow answers) is absurd.
I don't know about apetresc but I'm vested in that being a good way to assess candidates, and think you're doing the world a disservice discouraging people from it just because you don't like the company/product/offer it's for.
They are looking for an intern.
If a company in San Francisco wants an intern who knows how to build a POST endpoint, believe me, that is not an unrealistic ask.
Interns are not expected nor required to have any experience. You're being entirely unreasonable if you're looking for experienced interns.
If you're friends were so experienced already that they could land an entry level job by 18 then why did they go to college at all?
BTW, in the context of a job posting, "experience," means "professional experience," not "I threw together some shitty code one weekend in high school."
The simple answer is “no”. The HN community is not a monolithic block. You might as well ask if there’s one that would satisfy everyone. The key is to find one that works effectively for your organization.
It was the only time I felt a fair exchange of time and money was tendered and I also felt that it adequately demonstrated my skills to the company and their codebase (and impression of future work) to me.
I didn't get the job but the company will always have my respect.
I faced something similar to the OP and posted the results on Workplace https://workplace.stackexchange.com/questions/88138/working-...
I don't see how objectively criticizing the above practice lands squarely in this ivory tower strawman you're invoking.
(N.B., The linked Reddit post is indicative of abuse, so I’m not talking about that.)
A lot of SW engineers complain after an interview process, especially a rejection, because of some “if only”-hypothetical. “If only they tested my real skills and not whiteboards. If only they saw that I’m a hard worker at work and I just don’t have time for side projects. If only they read my resume and know that I don’t need no stinkin’ coding test.” This is a strong aversion to false-negatives. But it generally seems to be in the company’s interest to over-reject according to some “stupid” rules than to over-hire.
I’m not saying that there are no wrong interview styles, but I think there is a supposition and sensitivity of a problem that isn’t being framed correctly—around applicant satisfaction and not company success. I think if more folks ended up being hiring managers, they’d understand the inherent difficulty in the construction of these supposed silver bullet interview styles.
(PS, I say this as someone who has complained very loudly and publicly about mistreatment at Google interviews.)
I think all 4 forms of interviewing you are suggesting are reasonable and whether or not they are demeaning for the interviewee depends mostly on the attitudes of those involved. If the interviewer is a jerk setting out to dominate the interviewee, and does not even bother to conceal how they think the interview is going, it's going to be a demeaning experience. If the interviewer is polite, empathetic to the interviewee, and probes without hinting at the opinion they are forming, even a terrible candidate should be able to leave without feeling like they were unfairly treated.
- make a quick onboarding of the candidate
- explain the general architecture of the system
- find an issue/story that is "superficial" enough to be taken by someone with zero-experience at that job, but "deep" enough that you can test their experience and knowledge (oh, and that story better not involve anything that might be related to core company IP.)
- do a pair-programming session with the candidate, and be the main driver ALL OF THE TIME (because the candidate does not have any git access, so their development environment is useless)
- evaluate the candidate
You really think that is something for "a couple hours"? Even if it were, do you think it is a good use of the time of the engineer that is going to be allocated to the task?
> Even if it were, do you think it is a good use of the time of the engineer that is going to be allocated to the task?
So what exactly is the alternative? Look, if you can't prioritize hiring, don't be surprised that you aren't able to hire. Yes, the engineers should be able to do this.
What is the alternative? As most of things in life, the answer is "it depends". It depends on the size of the company, the type of candidate they are looking, the industry, and so on.
But let's assume we are talking about the average startup that is neither looking for superstar candidates nor only looking for fresh graduates from Stanford. For those cases, I believe that one simple programming task, that exercises some of the technology required can be used as a screening filter. The task should not take more than 2 hours to reach a working state. If the solution presented by the candidate is satisfactory, then you go to the interview to discuss the solution and how they got to the solution, the things that were easy/hard, and so on. Then you ask about the things that are missing, and the candidate's evaluation on how they would like to tackle.
Is that a satisfactory alternative?
> How many "systems" do you think your run-of-the-mill startup has?
These dont need to be production systems, they can in fact be simple systems used just for interviewing.
So in your alternative, how long does an engineer really spend on interviewing the candidate?
- Check out the code and review the solution.
- Give a pass or "call for interview".
Let's say that is half-hour of work.
Only for the candidates that get called-in, you can have an hour-long interview. Make it two hours if if you want. It will still save the interviewer time, and allow a better use of the time together.
This is not HN being picky about interviews. This is a delusional company making absurd demands for which they are rightly being mocked.
One thing Ive noticed is that asking for the hardest interview they have or can do usually gets them excited to talk with me. Which I like because there is nothing worse than a boring "reverde a linked list" type of interview.
However, it does appear as if the community is pretty united on the idea that asking for free labor like this means you deserve to go get fucked.
The three months without pay thing...that's a little different. I'd tell them no way.
I absolutely would not. They're a company; they can afford to pay me. Me, however, my landlord isn't going to accept "I had to work for free" in lieu of rent.
This argument is so ridiculous, because I enjoy programming it means I don't have a life? Is this an actual argument people make?
"it discriminates against people with lives [outside of programming/tech/work]."
as in
"It should be ok, if you want to, to not spend all your time outside of work doing unpaid work."
Excluding candidates that don't have a github or whatever is a signal you are looking to get employees that you expect to spend their entire lives at work.
If hobbying programming is your strength, own it. Nobody is going to disregard code samples you send them. The context is employers requiring hobby programming.
- Whiteboard coding is too far removed from "real work", not effective at testing general aptitude, and is demeaning.
- Asking to see side projects presupposes an unhealthy amount of focus on work, discriminates against people with lives, and is demeaning.
- Asking for a custom piece of real-world code that matches the company's actual stack is exploitative, should be illegal, and is demeaning.
- Basing everything on answers to 'soft' questions about previous experience discriminates against people who aren't interested in showmanship, leads to too many suits and bros, and is demeaning.
What on Earth should we be doing, then? Everyone on Hacker News is so enlightened and skilled at their job, that any form of verification is demeaning and beneath their dignity. Apparently I should make my hiring decision based on their comment history or something.