This is just my personal opinion. Feel free to disagree (I would actually like to hear your thoughts).
This might be difficult for someone who hasn't had any challenging problem recently.
So, an honest answer like "I actually haven't had anything challenging recently" might not do them justice.
Just because the project/environment/company they're working at/on isn't challenging doesn't mean they couldn't handle one.
It's kind of like asking a body builder "have you ever lifted a horse?" and they say "well, no, because there are no horses where I live".
Just because he hasn't, doesn't mean he couldn't, if necessary.
Good one. I would however hint at what you mean. It might not be very clear exactly what you're thinking of.
Very good. If you can't explain something in simple terms, it usually means you don't really understand it as well as you think.
Good, but depending on X, it might be difficult to think of answers on the spot.
Perhaps a better approach would some thing like "Do you think 'this quality' is required for X? Why?"
Honestly, I think a lot of people would not know how to answer this question. Or, at best, just give a random/standard answer which doesn't tell you much. :D
I think most people will avoid talking about failures, because they know this reflects badly on them.
Honestly, I think some people will just say they can't remember such a situation or just tell a small lie.
I agree with you wanting to find out how they deal with failure, but I don't think you'll find out this way.
What you're basically asking them is to open up (slightly) to a stranger.
Good one, but I would rephrase it simply as "What is your opinion about agile? Or working in a agile environment"
After that you can extend the discussion, if necessary.
Asking them about pros and cons would require too much "processing power" IMO :D
I'm not sure if this is really relevant.
You can have good developers who have never held a presentation in their life.
It's good that you want to know about this and let them know that your company supports this, but be advised: some people might consider this a personal question.
I'm not saying don't ask it, just to be mindful. :)
Thanks for taking time and providing your thoughts.
Here are mine:
And if at the end they really said they haven't, then imaginary situations can be used.
All of the questions can be delve more into if the candidate hasn't fully understood them.
Really good point and we usually have different forms for rephrasing these.
I'd argue about generalisation in this area. There are many people who know their limits and potentials really well. But even if they can't describe themselves, it's a really good starting point for provoking some thinking to see what is their evaluation about themselves. In another aspect, it's up to the interviewer's people reading skills to get the value out of this. But I wouldn't say the question is worthless.
Failure's definition can vary for different people. It's up to the interviewer to create a safe environment and let them know they embrace failure and value people who learn from them. Everyone has failed at something even in their day to day job, the fact that how they react and recover from it is the core for this question. So let's agree to disagree in this one.
This is really important for many companies including consultancies. As I mentioned before I don't just mean public speaking. Presentation in its simplest form can mean pitching your idea to your team. We're looking for skills in someone to simplify an idea and explain it to people concisely. Again we can agree to disagree.
We're not after their personal life's details. Simply to understand whether they are able to unwind and have the ability to maintain balance. We don't want someone who is super active for a couple of months and then goes under the weather for the next couple.
Thanks for your comments again, they'r really valuable for readers 🙏🏼.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.