Date Published: 28 September, 2019

playing cards

Face Value

I'd recently been on a job hunt (now fulfilled), and I was contacted through stackoverflow by a recruiter that had located my stackoverflow Developer's Story and was impressed. He'd asked me to complete a coding challenge which I passed with flying colors. I was then invited to participate in a technical interview with one of their team leaders and a developer - this is where the trouble began.

The first problem was that recruiter had informed me that this interview was to go over my code sample and take a deeper dig into my background; so I wasn't expecting a full-blown technical interview and therefore had failed to do any preparation.

The second problem is that I'd never taken part in a "real" technical interview and as such as I wasn't sure what to expect. I had, of course, read articles in the past about technical interviews, but it had been quite some time. It would have behooved me to reread some articles to have a better idea of what to expect.

So problems one and two are closely related and boil down to a lack of preparation and experience. It is my insight garnered from the third strike that I would like to share with you today: take all interview questions at face value.

Read More

About Todd

Full stack application developer. Life-long learner. Pragmatic programmer. Believer in clean coding. Proponent for extensible and reusable code. Hobbies include (very) amateur photography, collecting old jazz records and going to live music performances.

North Central Ohio, US

Obligatory Disclaimer

All opinions are my own, probably wrong, and subject to change without notice.

© 2017-2019 Todd Eidson. All content is licensed under the Creative Commons Attribution-ShareAlike 4.0 International License.

Hosted on linode