4 ms·
What an interesting dance interviewing is. >'Then, when pushed, he had one, but one with parenthetical comments about how he had told them not to make the mist
by incision 13y ago
What an interesting dance interviewing is.
>'Then, when pushed, he had one, but one with parenthetical comments about how he had told them not to make the mistake.
We said "culture" but what we really meant was, "He's showing the kind of defensive behavior that you REALLY do not want in a devop when things go pear shaped."'
I had an interview where I responded to a "greatest challenge" question with a true story about recovering a disastrous project from the brink. I related the story in a very "what we did" as opposed to "what was wrong" sense.
Afterwards, the interviewer pressed on about what actually went wrong in the project to throw it into a death spiral to begin with.
I generally try to avoid talking about previous employers, particularly in a negative light when interviewing, but I provided an honest answer - a short tale of cronyism, incompetence and prior efforts made to save the project.
I don't think the interviewer took too well to that response and I had to wonder if I'd been pegged as being defensive or accusatory there? I expect I was.
In the end, I'm thinking questions which might beg or demand talking ill of a past situation can be a no-win situation for the interviewee and not necessarily informative for the interviewer.