I'm trying to think of the intention of asking this question. Sorry, the only thin come to my mind is to worry about how much they pay for this position.
One of my big bug bears about recruiting is that candidates never ask questions - and they really should. It's a chance for a candidate to find out if the CTO / Chief Architect / Lead Developer who's doing the interview knows what they're talking about, or are just copying questions from Stack Overflow (or Dev.to :D).
I'd at least ask them why they chose to use MongoDB in their stack.
No matter how many £££ or $$$ they throw at you, if it's a messed up company who make tech choices based upon the last person to buy the CTO lunch, it's going to be no fun.
I'm trying to think of the intention of asking this question. Sorry, the only thin come to my mind is to worry about how much they pay for this position.
One of my big bug bears about recruiting is that candidates never ask questions - and they really should. It's a chance for a candidate to find out if the CTO / Chief Architect / Lead Developer who's doing the interview knows what they're talking about, or are just copying questions from Stack Overflow (or Dev.to :D).
I'd at least ask them why they chose to use MongoDB in their stack.
No matter how many £££ or $$$ they throw at you, if it's a messed up company who make tech choices based upon the last person to buy the CTO lunch, it's going to be no fun.
I agree, candidates should challenge interviewer to make sure their skills are assessed by a capable person