"one hour coding interviews" are absolutely horseshit.
and not for the reason you think: you wanna give me a "code interview", make it 8 hours.
A full work day.
Sit with me for 8 hours -- and 8 hours i'm *sure* you're getting paid for -- and get the straight dope.
This whole "ascertaining a decade of skill in an hour or less" is just an insult at this point.
@somarasu so I don't know enough to tell if things are ever/always done this way, but I was kind of floored to watch a comedic video where someone "cheated" a remote coding interview by looking up references so the interviewers didn't notice? I was like, I'm pretty sure devs use references in their actual work (though maybe they're Real Men about it unlike my weenie self and use man instead of Stack Overflow), what the hell is the use of a closed-book coding test?? If anything they should hire that guy precisely because he has enough sense to ignore bullshit rules and look things up!
@ljwrites That's not "cheating". I've done many an interview where they stipulate from the jump "you can Google and StackOverflow and whatever" (</paraphrase>)
It's not a matter of where you get your shit, it's how you go about getting shit. That's always been what I've been told, and always been the stipulation of my coding interviews.
*THAT IS*, unless you're sitting in front of a whiteboard sans laptop. Then all of a sudden it's different. For *SOME* reason.
@somarasu oh absolutely, my field isn't even CS but law and I was comfortable giving my students full open-book take-home tests, like they could look up ANYTHING and email their answers within 48 hours. They could paste in their Google search results if they wanted, but since a copy-paste wouldn't be responsive to the actual question I asked their grades would suffer. It was the application that counted, not the information. Much like simply copy-pasted code wouldn't do what the interviewers asked--or if an interviewee did find open-source code that does the same thing, that's even better, they proved they're savvy enough to save the company a bunch of time and energy!
@ljwrites @somarasu I do network operations which is a totally different tech field. Having said that. I would tell people “ I am going to give you a Kobayashi Maru scenario. I want to see how you think and how you think under pressure. In the job I will be your escalation person. Feel free to use me as such during this interview.” Watching how they failed and what kind of questions they asked me during the process told me everything I needed to know.
@sng @ljwrites And that's another thing: i've biblically aced code interviews with zero room for bullshit, only to be told "mmmm well you have no experience leading large teams soooooo we dont think you're the right fit"
IT'S A COMPANY OF 3 PEOPLE. *2* ARE CO-FOUNDERS!!!
THE FUCK DO YOU MEAN???
I mean, I know exactly what they mean: "no Negros in Lead"
Doesnt matter if it's 3 people or 300: it's been this way and always will be, so long as you have majority-White dev teams.
Which you always will.
@sng @ljwrites The NFL had a similar problem for a long time: Black people were considered "not intelligent enough" and "couldnt think quick on their feet enough" to be lead quarterback. So starting quarterback positions would consistently be handed to White men who performed at half the rate.
Which meant half the wins.
Which meant half the fans.
Which meant half the money.
And *THEN* coaches started changing their tune.
But just barely
the mastodon instance at cybre.space is retired
see the end-of-life plan for details: https://cybre.space/~chr/cybre-space-eol