How much time does it typically take (or should take) to complete a 'homework' project?
> 4. two phone screens with engineers > 5. onsite interview with 6 engineers
This seems very 'camel is a horse by committee' to me.
Reminds me a bit (know it's different) of dating where someone wants you to meet their family for approval. I immediately pass on those dates (and will add I am happily married to a woman who did not do that).
I wonder about situations where it takes so many inputs to make a decision to me that speaks a great deal about the decision making process being faulty.
Fwiw when I graduated college years ago I was rejected by a company (friend of the family no less) who said they couldn't hire me because 'yes you are smart but you don't know this business' (true I knew zero). So I started a company like theirs myself and now many years later they are gone and my company (which I sold) still survives. (Will add this was years before the internet and common practice for people who knew nothing to go into businesses they knew about).
Now yes I do understand programming is not the same but my point still stands why so many chefs in the kitchen? Does anyone ever go back and track the people who were rejected what happened to them?
I was still in college at the time but I maybe spent 5-10 hours over the course of a week or so. I do remember it took a very long time for them to respond after I had sent it in though. I believe the project was to implement a basic web crawler in Go.
> Now yes I do understand programming is not the same but my point still stands why so many chefs in the kitchen?
After the homework problem I think that's where they were defining the process as they went. They seemed to be growing quite a bit at the time (IIRC when I was onsite they had just rented two more floors of office space) and I had bounced between a few contacts that were brand new to the company. The real struggle is that I never knew how many more steps were to come, and I'm not sure they knew either.
Though after the onsite they e-mailed me almost immediately to setup the call with Ben so I think everything had gone well up to that point. I don't think the call with Ben went poorly so my best guess is that they went with someone that had experience rather than a new grad.
FWIW I'm not actually bitter about this. I just found it to be an interesting snapshot of a particularly chaotic point in the company's history.
Almost never, in my experience. Several times I came second in the running and never heard from them again. Contacting them myself didn't work either. Typical shop would rather look thru another hundred randos than revisit one decent candidate.
We also don't give them our actual problems as homework tasks. We'll occasionally talk about our real problems with candidates in interviews, but we're very clear about it when we do.
It's not a perfect system. Some candidates will choose to spend longer on the task so that in the follow-up interview they'll have the opportunity to talk about stuff that really shows off their strengths, so their effective hourly compensation for doing it would be quite low. The task is explicitly flexible like this, and we've also hired people who spent _half_ the par time on it (e.g. life circumstances making spare hours hard to come by) and didn't implement much at all, but then were able to confidently answer our questions about the bits they didn't actually implement.
Even if we were to only hire 1 out of every 15 people who get far enough through the pipeline to do the homework task (I don't recall the actual numbers) it costs us _nothing_ to compensate people for their time compared to, e.g., what it would cost us to make a bad hire. So it seems like an obvious thing to do even if only to stop candidates from having to wonder "am I getting screwed here?"
That said it is completely unethical to make people do real work as part of an interview process. We collectively should name and shame any firm that does that.
This is not true.
I've can think of one employer my entire career that had conditions regarding work outside of my normal work hours.
Granted, if you worked for your competetors and they found out about it you could be fired due to trade secrets or conflicts of interest. I only remember one employer I had where I signed something with binding agreements related to other work (and, as it happens, that was perhaps the worst employer I ever had).
I know some employers in some regions do this, but it is a far cry from affecting "nearly every worker in the US". In fact, I am not aware of any of my friends in tech positions currently being under such an agreement (that is, an agreement requiring pre-approval for outside work). In fact I believe it is illegal under many circumstances in some states for an employer to require it (but don't rely on me for that, conditions/laws change, and I have had no reason to look into it recently). I do remember discussions about it in the not too distant past, however.
The language you're looking for in the contract is 'preponderance of time'.
Agilent is not great either. They interviewed me for 6 month and implemented some of my ideas. (In fact, I got the job, out of 500 applicants, but then they axed the job and hired nobody)
[0] https://www.irs.gov/businesses/small-businesses-self-employe...
The visa process may be flawed, but putting the blame on the employer is... weird.
Some people don't like take-homes that replicate scenarios/projects because they think it's too close to real work and want to be paid instead!
There's no pleasing everyone with interviewing processes.
If you feel that a request is unethical and it's not what you want in a company, well... you - as a candidate - can terminate the interviewing process.
Then it's no different to the rest of the candidate's time spent interviewing - it's cost of doing business that no one expects to be remunerated for.
The other benefit is that you then keep a benchmark of deliverables by having each candidate complete the same task (you have to change tasks over time as the details of the project get leaked/discussed).
I like these because they are not games. If you want something done, you'd ask an employee to do it. So just ask someone to do something you need done.
In our case at least by the time it was something that was part of an interview, it had already been implemented on the business side. Our projects were usually 2 hours tops?
The idea that this is unethical is wild.
We also do paid internships and have folks actually work on stuff that way -> do a good job, pretty good line up for a full time position.
Why would a place like google even use an interviewees code without careful copyright assignment and work for hire protections (ie, you need to pay someone in USA generally to own their code).
I've found some potential hires are randomly paranoid - and if they start giving you lots of hypothetical disaster / ripoff scenarios early, not worth the hire?
A 6-person company in New York did that to me. I reviewed the interview project I did for them and their latest product update. I had to ask them a week after the interview if they used my code in production and if so - this is how many hours I worked on it and a fair rate. The CEO emailed me threatening legal action and then called me 10 minutes later apologizing and venmo'd me the amount I stated it was worth.
If your interview process works for you that is great.
But I could totally see why potential hires are paranoid if you are giving them a situation to be paranoid about. I hope you are being super clear with your process and giving assurance you aren't using their code. If it was me, I would show them the code our team wrote at the same time they submit their project and use that as part of the follow up interview.
I felt this was good. I got paid and it was a fun challenge. It also obviously wasn't "actual work," but even if it was, I was getting paid, so why not?
I don't think it would have been out of the question to say I was too busy to dedicate 8 hours either, but in my case I had the time.
Overall it was an excellent experience.
I see nothing unethical in it.
3 years later the feature has still not made it to production. I hate that every time it would have made my working day easier :)
It's good because it will determine if they're a good fit for the team and gauge how much they have to offer.
The real issue was how chaotic the process was. I had started out talking to an engineer that had picked up my application, but was handed off to recruiter only after the homework portion was done (said recruiter even mentioned that they had just been hired). The two technical phone screens also were two discrete steps (i.e. the second was only scheduled after the success of the first).
That was really the issue: neither I nor them knew how many more steps there were. It wasn't helped by having long periods of radio silence between each step either. But it was painfully obvious that they were scrambling to figure out how to scale their processes, so much so that it still stands out to me 6+ years later.
I more wanted to emphasize my view as a bystander at a very hectic point of their growth, not actually complain about the experience. It was an interesting experience to me, not a negative one.
I have no hard feelings about it and I'm sure things got sorted out. I certainly have no negative views of any individual I dealt with.
They we going through some pretty crazy growth at the time so I forgave a lot of disorganization in the interview process. Unfortunately I didn't end up getting the role but I'm glad to have had that experience; it was definitely an interesting point in DigitalOcean's history.