As part of the application, I was instructed to provide 2-3 paragraphs on each of half a dozen questions that covered various aspects of software engineering. The in person interview asked a predefined set of questions about the material that I had provided. That part was more of a "demonstrate that you have the mastery of the material claimed in the written portion and that it wasn't produced by someone else or some other source". This also tested communication skills.
No weight was given to GitHub contributions, hacker rank, leetecode rank or whatnot. There was no whiteboard.
While this isn't a fabulous job at a tech company, it is one where good engineers can and do find themselves at without needing to have the proper shibboleth to get into one of those tech companies.
For another job application that was more of a sysadmin/programmer bend, a simple backup script was the assignment (took about 1h to get all of the edge cases). A portion of the interview was a demonstration and review of the code (in which I had to answer questions about the code that I had written).
While mock interviews can be helpful in the communication skills department and reducing anxiety, there are many other ways to test the person rather than use a proxy such as contributions to a public repository or foo rank websites... and also without resorting to whiteboard for various algorithmic tricks that you either know or don't know.
If people at Google were interviewed by juggling raquetballs, there would be books, courses, etc. on how to juggle better. People are willing to pay for this prep because they want to work at Google. Eventually most everyone interviewing at Google would be very well prepared to juggle.
Obviously if the process was a 100% fair assessment of knowledge and potential and people do better than you then good for them.
As someone who gives a lot of interviews, I'd love a better way to assess a candidates ability that is less gameable, but we haven't found one yet.
Other companies are much more specific in their interviews...you actually get a specific JD with expected skills that you hope will form the basis of your interview, and not all JDs require you to be a distributed systems/algorithm wiz.
This is exactly the concept of an IQ test, right down to the stack ranking.
They're pretty well understood by now, and they take less than a day, which compares pretty favorably to "months".
- Preparation not required.
- Preparation not beneficial.
And it shouldn't be surprising that they achieve that well. Consider these scatterplots comparing students who took the SAT without preparation to students who prepped: https://infoproc.blogspot.com/2012/02/test-preparation-and-s... .
As further described at the same link, research quite consistently shows that the effect of preparation on SAT scores is small, and...
> One of the most remarkable aspects of this line of research has been the lack of impact it has had on the public consciousness.
Again, this shouldn't surprise you, because it is a design goal of the SATs not to show an effect of preparation on scores, and they do their own research to ensure that preparation in fact does not have much of an effect.
Normies and free thinkers just take a pass.
However, golden wingless dragons seem to do just fine.