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:
49: What is a build pipeline?
48: Agency or product?
47: How do you build a blog?
46: How do you apply to speak at a conference? (with Tony Edwards)
45: Should you take a bootcamp?
44: What is the difference between a framework and a library?
43: Yearly Themes: 2020
42: What does a developer do all day?
41: How long does it take to get a job in tech?
40: Can you trust recruiters?
39: Do you have impostor syndrome?
38: If it's not broken should you fix it?
⚡️ Help us, listeners. You're our only hope
37: When are you ready for a coding job?
36: How do you keep track of your knowledge?
35: Do you git it? (What is version control?)
34: How do you learn a new programming language?
33: How much tooling is too much tooling?
32: How do you prepare for a new job?
31: Should you pivot?
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
The Unbelivable Truth - Series 1 - 26 including specials and pilot
Lex Fridman Podcast