Well, I think it depends on what the rewards are for getting the job. If the pay, benefits, and accreditation (resume boost) from holding a position at a given company are sufficiently valuable, it is definitely rational to play the game.
Full disclosure; I have never done an interview like this, or tried to land a job at a major 'tech' company, though I do have a degree in engineering.
Re:Rules of thumb for a 1x developer
by scarface74 on Thursday April 30, 2020 @01:46PM
(#23033699)
I think I might have found a hack - a way to work for $large_tech, not to have to move to the west coast, work remotely and not be required to do leetCode - work in the cloud consulting division of either Microsoft or Amazon. I’ll know by the end of May if it works.
This is one of the reasons I haven't applied to work at Amazon, even though I'm sure I could do the work. The signal they're sending by interviewing this way says "We want people who are willing to put up with bullshit".
Re:Rules of thumb for a 1x developer
by freewilly1040 on Thursday April 30, 2020 @02:57PM
(#23034677)
This comment implies leverage that the OP probably doesn't have though. Everyone is picky to the extent that they can be.
Re:Rules of thumb for a 1x developer
by scarface74 on Thursday April 30, 2020 @01:57PM
(#23033858)
I had the same attitude pre-Covid. My local market (Atlanta) has completely tanked. There are still jobs out there, but salaries have imploded and I don’t think they are coming back for a couple of years.
If I didn’t have any other option besides the standard r/cscareerquestions “Learn leetCode and work for a FAANG” , I would.
A sensible knowledge and performance evaluation would involve pair coding on limited scope, immediate, real problems, not BS trivia.
Interviewing is a two-way street.. the signals given-off in the interview process should be taken in as a totality by the interviewee as well. If they see bad signs, they should run in the opposite direction rather than get sucked into a bad environment.