As some of you gentle readers may know, I’ve been a-lookin’ for a new job over the summer and into the fall. A mainstay of the industry now is the dreaded tech interview, which wasn’t really a thing last time a went a-huntin’ close to ten years ago. But now they’re all the rage.
In a way it makes sense, cuz whoever is interviewing you needs some way to evaluate your skills and all that. There’s no way they can judge if you can write advanced, subtle and poetic code, so they settle for a much lower level test: can you regurgitate some basic stuff? Still, it’s not always easy to think on your feet and come up with a good answer on the spot. I haven’t used alot of this stuff in my day-to-day in years. Doing a tech interview is a skill in its own right, a kind of performance like jazz improvisation, and it took me a few times to get good at it.
Along the way I compiled a handy quick reference guide. Basically every time an interviewer asked me a question and I didn’t know the answer, or more commonly just wasn’t able to express it in a clear, structured and smooth manner, I wrote down the question, went home and looked it up, and added to my guide. Then I circled back and studied up for the next interview. Before too long I started getting a fair number of repeat questions, and was able to nail more and more of them.
This is not meant to be any kind of comprehensive tutorial, just enough to remind me to spew forth some talking points. As you can see by the topics covered, I cast a fairly wide net with my skillset in the kind of position I’m going for. Really this is a symptom of the state of the industry these days, the way jobs are balkanized by programming language, more than my own itinerant tendencies. “Are you a java guy or a javascript guy?” Oh please. I know like twenty programming languages. And if I don’t know any particular thing I know how to look it up. It’s also a fairly interesting snapshot of what languages and frameworks an in vogue these days, totally different than 2007.
So here you go.