In your last interview, were you asked a question you thought was either too tough, too personal, too ambiguous, etc.? Did you think you ‘nailed it’ or did you come away confused about the purpose of the question, your response, or whether the interviewer was messing with you?
From the article:
“…candidates often struggled with the question: “Tell me about your most significant technical accomplishment, the project that you’re most proud of.” Max Brown, ex-Tesla recruiter.
This doesn’t sound too bad, does it? I can think of a few examples here, but is it the kind of thing the interviewer is looking for. Brown says that “most people’s first instinct is to pick the project or achievement that sounds the most substantial on paper – but that’s not always the one that illustrates their actual technical ability” and that “it’s usually better to shine the spotlight on a smaller project where you can truly speak to all of the technical aspects. In many cases, the biggest, most impressive-sounding initiative you participated in was largely the result of a team effort.” Hmm, really. Well, here’s what I would say, and these were my first thoughts when reading the article last night …How would you answer an interview question about your 'most significant technical accomplishment'? Click To Tweet
My most ‘significant technical accomplishment’ would probably be one of my first positive experiences using computers. Back in the early- to mid-80’s my Dad bought me a ZX81, and then a ZX Spectrum. Before we bought a cassette player to record and load games I had to type each and every game I wanted to play. Copied from magazines or books, this could take a couple of hours, required squinting intensely at code which, as I’m sure you’re aware, would be rendered useless if you got just one comma or semi-colon in the wrong place. I learned the hard way to pay attention, keep the finer detail in mind when trying to rush to finish before bedtime, etc. I also learned to fix the broken published code. I learned what form the code should take, how to reference other bits of code. I learned how to trust myself and my ‘intuition’ when the code was wrong, so I could fix it before continuing.
From this I learned to write my own games, albeit very basic, but it was still all mine, from concept to (working) completion. I remember a worm race … six or eight worms race from one side of the screen to the other with random generator controlling how fast each went. Whichever got to the other side of the screen won, and I got the whole family to watch and choose a worm! Quality family time, eh? It’s from here that much of everything I do now stems … my interest in computers and computing, developments in AI and VR, gaming (although less and less now, but I’m getting back to it through my kids), the Internet, self motivation and confidence, advances in wearable computing, etc.
If in doubt, here’s another perspective for your next interivew .. “never stop learning”.
— McGregor Boyall (@McGregorBoyall) October 26, 2017
What would you choose as your ‘significant [technical] accomplishment’?