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:
69: Why bother with side projects?
68: Are bootcamps worth doing? (with Kirsty Simmonds)
67: How can developers help fight climate change? (with Natalia Waniczek)
66: How do you get started in data science? (with Tom Sainsbury)
65: Should new developers get involved in open source? (with Jeremy Walker)
64: How do you get started with Pandas? (with Boris Paskhaver)
63: What is i18n? (with Eli Schutze)
62: What is it like to have a mentor? (with Amber Wilson)
60: What is a resilient website? (with Jeremy Keith)
59: How do you prepare to give a presentation?
58: How do you run a remote conference?
57: Why is time so hard to work with?
56: How can you make code habitable?
55: Any tips and tricks for effective home working?
54: Why do people write "bad" code?
53: What are some good things to build?
52: What gear do you use?
51: What is a Minimum Viable Product?
50: What's so special about the command line?
Create your
podcast in
minutes
It is Free
Insight Story: Tech Trends Unpacked
Zero-Shot
Fast Forward by Tomorrow Unlocked: Tech past, tech future
Lex Fridman Podcast
Elliot in the Morning