4 ms·
> Most commonly it's a question like "tell me about a time when you encountered a bug in production, how you discovered it and the steps to resolve it". And ins
by Mawr 3y ago
> Most commonly it's a question like "tell me about a time when you encountered a bug in production, how you discovered it and the steps to resolve it". And instead of answering the question, they tell me about what they _would_ do, if they _had_ found a bug.
Of course they do, it's only natural and smart. They hear your standard formulaic behavioral question and cut to the chase instead of being sheep.
If you want real answers, hold real, natural conversations. Don't read items off a checklist.
- mvdtnz 3y agoThe question is just a jumping off point to talk about things like monitoring and alerting, production logging, your release process, testing, etc. It's why I want to start with personal experience. > Don't read items off a checklist. I've gone through periods of interviewing 3+ candidates a week for months at a time. It's just not reasonable to expect me to have a unique and interesting conversation with everyone. There are things I need to get into.
- Mawr 3y agoThat's fine, just be aware that the way you phrase your question is indirect and smells of the typical interview BS. If you'd like to find out how the candidate handles bugs, ask for that directly. Otherwise you're no longer in the realm of a technical question anymore, but in the "can you, on the spot, come up with a plausibly-sounding story that puts you in good light?". The ability to recall/make up/tell good stories (under pressure!) has nothing to do with engineering.