I have been interviewing for a couple of years now. It is fun! Especially when you asked the same question already a couple of times and you see how each candidate approaches the problem in a unique way.
I have two questions:
1. How do you recognize cheaters?
2. If you have a good (front-end) interview question and you are willing to g to share then pls DM. I am searching for a good one :)
Good questions. Unfortunately I only conduct system design interviews so I can't help you with front-end questions.
I try to demotivate cheating by making the problem very open-ended. By creating problems with multiple solution paths, I'm not looking for a specific answer, but interested in the candidate's reasoning. I also ask open-ended questions to understand their thought process. If they still perform well, I dig deeper with more complex follow-up questions.
This approach works well for system design interviews but has limitations for straightforward coding and algorithm problems, where cheating can be easier.
Lots of good advice. There are many benefits of becoming interviewers as Fabio mentioned. It's also a motivation for an individual to learn current hiring practices and making themselves as a trained candidate in the current market situation. So start with small like "I'll take 1 solo interview within next 3 months"
Indeed...doing an interview can be a bit nerve-wracking, even if you are on the other side as the interviewer. But, it is a great experience for personal growth. Go in with curiosity, as Fabio says, and you will do great!
Good insights! Thanks Fabio!
I have been interviewing for a couple of years now. It is fun! Especially when you asked the same question already a couple of times and you see how each candidate approaches the problem in a unique way.
I have two questions:
1. How do you recognize cheaters?
2. If you have a good (front-end) interview question and you are willing to g to share then pls DM. I am searching for a good one :)
Good questions. Unfortunately I only conduct system design interviews so I can't help you with front-end questions.
I try to demotivate cheating by making the problem very open-ended. By creating problems with multiple solution paths, I'm not looking for a specific answer, but interested in the candidate's reasoning. I also ask open-ended questions to understand their thought process. If they still perform well, I dig deeper with more complex follow-up questions.
This approach works well for system design interviews but has limitations for straightforward coding and algorithm problems, where cheating can be easier.
I see thanks! Yeah I mostly ask algorithmic questions. Cheating is easier there…
Lots of good advice. There are many benefits of becoming interviewers as Fabio mentioned. It's also a motivation for an individual to learn current hiring practices and making themselves as a trained candidate in the current market situation. So start with small like "I'll take 1 solo interview within next 3 months"
Indeed...doing an interview can be a bit nerve-wracking, even if you are on the other side as the interviewer. But, it is a great experience for personal growth. Go in with curiosity, as Fabio says, and you will do great!