[apwheele]

I expect `python hello_world.py`, but if people are confused I just nudge them to what I expect. It is not meant to be a trick question.

If people do not have local setup, I just have them write out in text editor and walk through the steps. Maybe not 75% fail rate, but more like 50% of people fail this step in the tech round.

[sceptic123]

Isn't your experience highlighting what the article is suggesting though? That needing to do this during an interview is what causes these failures rather than an inability to actually perform the requested task.

It seems like the suggestion is to put them somewhere private to perform the task rather than asking them to do it in a public setting.

[apwheele]

The rub is the take home assignments are not good either.

I do personally let people pass the tech if they have good open source work (a good tech blog, legit python repo's, not just trivial homework stuff they did in school). So few of people have that though.

[abeppu]

But the thing in the study cited in the post was putting people alone in a room for the same task with the same time limit -- _not_ take home assignments.

What if this is just a (labor-saving) tweak to on-site live coding interviews. You've already reserved the room. The status quo is that a member of technical staff is in the room with the candidate for the duration of their interview. The low-cost alteration is, after you explain the task and make sure it's clear, you leave them alone in there for the remainder of the period. Perhaps the interviewer gets a few small work tasks done while waiting outside.

I think the only unfortunate thing is that when you're in the room trying to talk to them about their solution as they write it, sometimes you can have a helpful discussion, which may involve probing or leading questions, which sometimes give you some signal -- but these also make it much more difficult to compare across candidates, so perhaps we should be ok letting go of that opportunity.

[savorypiano]

Just to clarify, do these 50% regularly develop using python, and did they understand the question?

It seems unavoidable to know how to run a script if you've done it within say a month. Now not remembering the if __name__ == __main__ thing is more forgivable.

[apwheele]

These are 100% people who claim to be senior ICs with years of developer experience in python. The resume thing that list being expert in dozens of libraries, etc.

It is even less tricky than you are thinking. I literally just want them to know you need to put in a `hw.py` file `print("hello world")`, and then run from the command line `python hw.py`.

The reasons for failure are myriad (I suppose you could say it is they do not understand, but I legit try, regularly spend 10-20 minutes on just this for the ones who have problems, I am not being tricky). A few are people who do not know file systems (save their `.py` file in a wrong location), a few I think just do work in environments like served jupyter notebooks so don't have any relevant software dev experience (don't know how to execute python directly or write code in a .py file), some I am pretty sure are just liars on their expertise (have a few that just leave interview when asked this question).

[savorypiano]

Not aimed at your comment per se, but I'm having trouble reconciling these stories where a vast majority of applicants fail a simple test (or other Fizzbuzz type tests) with stories of how difficult interviews are these days with Leetcode hards, etc. Maybe the populations are not mixing.