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:
⚡️ How much time do you spending coding in a coding job?
⚡️ How long should you spend on a take home coding challenge?
⚡️ Tabs or spaces?
30: What do you get from going to a tech meetup?
29: What's wrong with developer culture?
28: How do you stay motivated?
27: How do you deal with crazy bugs?
26: What is functional programming?
25: Do you need to be good at maths to become a programmer?
24: Should you write about what you've learnt?
23: How do you write a good CV?
22: Why should you write tests?
⚡️ What does it mean to be a full stack developer?
⚡️ How closely should you match a job description before applying?
21: How do you get started with open source?
20: What's it like to attend a tech conference? (Live at Future Sync)
19: What's it like being a remote developer?
18: What's the interview process for a tech job?
17: How do you find a mentor?
16: When should you specialise?
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