I remember failing an interview once because they wanted me to know all sorts of obscure c++ tricks. The kind of stuff that most people skipped over when they read about it because it has almost no use case. Had travelled 200 miles for that interview too.
No idea who they wanted… someone who had a photographic memory to memorise a textbook, maybe?
We tend to give practical tests when interviewing… ‘go away and write this thing’. We’re not testing whether they write it, or how they found the solution… google is there to be used… but the questions they ask about the (deliberately) interpertable spec and what the code looks like.
People are generally looking to hire themselves. So if someone memorized the amazon coding question handbook, they expect that anyone applying to work at MidCo have done the same. Same with people who consider themselves “enthusiasts”. At my old job, it reached the point that we had to schedule interviews around one of the major project leads going on travel because, otherwise, he would be insanely obnoxious as he insisted they should know everything about whatever C++ standard proposal he read last night.
And that obviously also has issues regarding diversity since a lot of the same “I am the best person so everyone should be like me” mentality folk tend to want to hire people with a similar background to them…
That’s what happens when a company asks their “Rockstar” developer to write them a few interview questions. Whatever thing they just learned recently they would delve into in great depth. I just learned about binary packing! Guess what’s going to be on the test.
A lot of good developers don’t even pseudocode all that well on the whiteboard.
Of course you also end up with a lot of people that have hearsay knowledge. How would you optimize this communication stack? Oh I’d go web sockets and then switch over to UDP after the connection initializes. They have a conversation with you about how “they” did it at their last company and it solved all the problems. Then 3 months into the project you find out that they have no idea how to pull it off and they were just repeating what they heard in a scrum.
I remember failing an interview once because they wanted me to know all sorts of obscure c++ tricks. The kind of stuff that most people skipped over when they read about it because it has almost no use case. Had travelled 200 miles for that interview too.
No idea who they wanted… someone who had a photographic memory to memorise a textbook, maybe?
We tend to give practical tests when interviewing… ‘go away and write this thing’. We’re not testing whether they write it, or how they found the solution… google is there to be used… but the questions they ask about the (deliberately) interpertable spec and what the code looks like.
People are generally looking to hire themselves. So if someone memorized the amazon coding question handbook, they expect that anyone applying to work at MidCo have done the same. Same with people who consider themselves “enthusiasts”. At my old job, it reached the point that we had to schedule interviews around one of the major project leads going on travel because, otherwise, he would be insanely obnoxious as he insisted they should know everything about whatever C++ standard proposal he read last night.
And that obviously also has issues regarding diversity since a lot of the same “I am the best person so everyone should be like me” mentality folk tend to want to hire people with a similar background to them…
That’s what happens when a company asks their “Rockstar” developer to write them a few interview questions. Whatever thing they just learned recently they would delve into in great depth. I just learned about binary packing! Guess what’s going to be on the test.
A lot of good developers don’t even pseudocode all that well on the whiteboard.
Of course you also end up with a lot of people that have hearsay knowledge. How would you optimize this communication stack? Oh I’d go web sockets and then switch over to UDP after the connection initializes. They have a conversation with you about how “they” did it at their last company and it solved all the problems. Then 3 months into the project you find out that they have no idea how to pull it off and they were just repeating what they heard in a scrum.