Episode 412: Sam Gavis-Hughson on Technical Interviews
Sam Gavis-Hughson if BytebyByte discusses technical interviews. Felienne spoke with Gavis-Hughson about how to prepare for the dreaded ‘whiteboard interview’ and how to get better at doing interviews. They also discussed the interviewer side of things: how to conduct these interviews yourself and how to improve that.
Related Links
SE Radio theme: “Broken Reality” by Kevin MacLeod (incompetech.com — Licensed under Creative Commons: By Attribution 3.0)
Podcast: Play in new window | Download
Subscribe: Apple Podcasts | RSS
Tags: IEEE Computer Society, IEEE CS, Interviews, on-boarding, podcast, recruitment, SE-Radio
I enjoyed this one a lot. Great questions and follow ups by Felliene (?) the interviewer.
Episode 412 focuses on what you should ask potential job candidates. You miss Episode 412 focuses on what you should ask potential job candidates. You missed some other good things to do: (1) ask the candidate what he or she is expert on, (2) ask to see some of the code they have written, and (3) asked to see examples of interfaces they might have designed. If you see their code, you can see how clear it is, how reusable it is, and a lot of other good information about the maintainability of their code. And if he or she must design user interfaces, you want to see if they have skills in that area. Many programmers do not know how to design a useful user face, and without it, people can’t or won’t use a program they wrote ed some other good things to do: (1) ask the candidate what he or she is expert on, (2) ask to see some of the code they have written, and (3) asked to see examples of user interfaces they might have designed. If you see their code, you can see how clear it is, how reusable it is, and a lot of other good information about the maintainability of their code. And if he or she must design user interfaces, you want to see if they have skills in that area. Many programmers do not know how to design a useful user face, and without it, people can’t or won’t use a program they wrote