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:
89: Top Tips review: pragmatic learning
88: Top Tips review: document what you learn
87: Top Tips review: enjoy what you do
86: Top Tips review: just get things done!
85: Top Tips review: why should you build your own website?
84: Why should you own a rubber duck?
83: How do you get started with a new framework?
82: What is semantic markup?
81: What is an API?
80: What’s it like behind the scenes of a podcast?
79: How important are CS fundamentals? (with Vaidehi Joshi)
78: How can developers get better at design?
77: Should you use boilerplates?
76: CSS Revisited (Rapid Fire)
75: Why do you need a website of your own? (with Chris Coyier)
74: How do you get started with testing? (with Brian Okken)
73: Why is Python a good starting point for learning to code? (with Michael Kennedy)
72: CSS Extravaganza!
71: How should developers market themselves? (with Shawn Wang)
70: Is "become a developer" still good advice?
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
Acquired