A Question of Code

{{ show.title }}Trailer Bonus Episode {{ selectedEpisode.number }}
{{ selectedEpisode.title }}
|
{{ displaySpeed }}x
{{ selectedEpisode.title }}
By {{ selectedEpisode.author }}
Broadcast by

Summary

Questions are our stock-in-trade, and we've got some great ones that you should try to ask in any job interview.

Show Notes

Let's set the scene. You've landed an interview for your dream job in tech. You've crushed it on the technical evaluation and wowed them at the whiteboard; everything's going your way. At that point, somewhere towards the end of the face-to-face segment, you'll be hit with the following challenge: do you have any questions for _us_?

We _love_ questions here at A Question of Code (surprise, surprise), so of course we've got some advice for that inevitable scenario. There are some great questions to ask prospective employers, and some more risky ones too. So what should you ask your interviewers when you're being interviewed? Is it a good idea to "get all up in their face"? And how can you turn the situation to your own advantage? Find out all this and more in this week's questionable instalment of A Question of Code.

Mentioned in this episode:

What is A Question of Code?

A newbie coder and a seasoned veteran discuss the questions that always come up when someone begins learning to code.

Ed is looking at getting a career in programming and has been learning to code for just over a year. During this time he’s been building up a stack of questions that keep coming up from other newbie coders. Luckily, he’s got someone he can ask for help: Tom. Tom’s a seasoned coder, having worked in the industry for a few years now and has all the answers Ed needs, or does he?