4 ms·

I wrote a blogpost on this exact topic last year: http://hackerjobs.co.uk/blog/2012/5/16/assessing-a-company-questions-you-need-to-ask-in-an-interview http://ha

• a_developer 13y ago
  I really like your question about the impact if they can't fill the position. It seems like a tough one to get away with, though. It could come off as too cocky, or as too much of a salary negotiation setup. Does this one go over ok? What kinds of responses have you gotten? Also, on feedback: have you ever gotten useful feedback from an interview that didn't result in an offer? I've tried, but rarely gotten anything, and even then it was so vague as to not really be useful.
  • Peroni 13y ago
    Personally, I think the 'impact' question is completely valid and not even remotely cocky. It's important to avoid structuring the question in a way that sounds like "what's the impact of not hiring me" and make it clear you're interested in hearing about what's important for the business. It shows commercial awareness which is usually quite lacking in technical interviews. As for feedback, unfortunately most companies fail to offer useful feedback if you aren't successful in getting the job as you're no longer considered to be of any importance to the business. Some companies have policies that prevent them from giving you too much detail and some simply refuse in order to avoid opening up a legal can of worms. One seemingly harmless question that you could ask after you get rejected is "What one thing should I work on to improve my chances of working for your company in future?". Take the advice and address it in your next interview with the next company.