Speaking of Instacart, I scheduled an interview with them via interviewing.io, which I was told was a "technical chat," designed to get to know a little about me, and to answer any questions I might have. I had qualified for the interview by scoring well enough on phone screens on interviewing.io, so, this technical chat was supposed to be followed by a real, actual coding interview.

Guess what? It wasn't. They rejected me as soon as I de-anonymized to allow them to see my resume.

> Possibly I'm just bitter because of the time I spent 4 hours on a take-home only for the company to ghost me (name-and-shame: Instacart).

Arthena, a Y Combinator funded company, did this to me. It truly was a waste of time.

Take home interviews should be paid, like 200$ and not require more than 4 hrs.

They should really be paid at the comp rate of the position you are hiring for (which is... a lot more than $50/hour for the Bay Area employers who have given me take-home interview problems).

Agreed. I am quite disillusioned by take home exams / online hackerrank style tests.

You got lucky. Arthena is a mess. Super disorganized and doesn't treat their people well.

So I've heard. I only went through with it because I have a good rapport with one of their employees who recently left for those reasons.

Worst for me was for Rakuten when they asked to basically implement a complete ETL pipeline to populate a mini-datawarehouse. It was easily more than a week's worth of 2 hours per day work that was supposed to be done within a week and worse, they didn't even bother to provide feedback.

The worst experience I've had with a take home problem was when the interviewer did not even run the program I submitted. As I explained the solution it became clear that the interviewer had not even looked at or run the program. It would have been easy, it was in Python.

To top it off the interviewer then sprung a surprise leetcode problem on me that had to work and was required to be written in a language ill-suited to the task. I bombed it and the interview ended. No one ever even ran my submitted program.

If you think that's bad. I did my code submission tested the crap out of it. Then found out that the person "couldn't run it". We had a back and forth conversation about it. I even created a docker test bed with the right environment.

mvn clean package worked.

Turns out the guy was running mvn exec:java.

>"Take home" questions are heavily biased in favor of the employer because they're not required to put anything on the line.

Not to mention it doesn't test the collaboration aspects of real work. Imagine doing your job but you're not allowed to talk to your teammates in case of a blocker. How are we doing our jobs here?

But when it comes down to actually starting them, I will always pass if they come before any interviewing round. You don't yet have a stake in the process.

And maybe excludes short of time people taking care of kids? Maybe more often women

The "easy" fix for this is to pay the candidate for the time spent on the take-home.

That has the down side of some potentially sticky legal issues. For instance, people on visas can't do paid work for any company other than the one sponsoring them. It introduces a small annoyance at tax time, as well.

You could ask them to name an institution for you to donate money to. It would at least be something to make the world better :)

This is actually not a bad idea. As a candidate, it still gives me the assurance that they aren't just throwing out these tests to 1000 applicants.