2 ms·
I like this punchy summary, it's been in the back of my head in a more wordy fashion for a long time now when it comes to hiring. I used to do technical intervi
by Cthulhu_ 5y ago
I like this punchy summary, it's been in the back of my head in a more wordy fashion for a long time now when it comes to hiring. I used to do technical interviews (nowhere near the scale and diligence of the big players though), and I tended to gloss over a lot of details, that is, there wasn't so much a "scoring checklist", instead I looked for traits like curiosity and enthusiasm. Our technical assessment included working with XML and JSON; early on (early-to-mid 2010's) a lot of people said "I've never worked with JSON before", later on it was "I've never worked with XML before".
Some just gave up before finishing the assignment and didn't show up to the interview at all.
I think the most interesting hire we did from our technical interviews was someone who solved in a modern version of J2EE, years after Spring had become the 'de facto' standard as a response to J2EE itself. But Spring became that thing it swore to destroy, and the J2EE solution looked pretty elegant.