4 ms·
Having spent a lot of time being interviewed recently, I've noticed a certain type of question asked in technical interviews that I think can sabotage perfectly
by ravenstine 8y ago
Having spent a lot of time being interviewed recently, I've noticed a certain type of question asked in technical interviews that I think can sabotage perfectly qualified engineers. I'm not sure if my view is sound, but maybe someone can pipe in and tell me why I am wrong.
Imagine being asked this question in a technical interview:
> When do you decide to use frontend validation?
(yes, this is based on questions I've been asked IRL)
The problem that I have with this type of question, even though it can be answered and seems reasonable, is that it's not even how engineers tend to think most of the time. It's about a solution looking for a problem.
When I'm faced with this kind of question, I often stumble to come up with a hypothetical need for the solution being proposed. It's not that I can't come up with an answer, but I end up lacking eloquence and saying "ummm, well, okay, so..." a lot while using my imagination. It would be like handing a hammer to someone and asking them to find things to nail with it.
In essence, it's backwards from how I would tackle most problems.
Here's the sort of question I would rather be asked:
> Let's say that we've built out a web form that the user can submit, and there are a lot of inputs they have to fill in. They can only know if they made a mistake once they've hit "submit", due to backend validation. How could you improve this experience for the user?
I find this preferable because it's a lot more realistic and natural. Instead of looking for problems to fit the solution, I have a problem and need to come up with a solution. To extend my hammer analogy, this is like providing the pieces of a wood table and allowing the candidate to show how they would assemble that table. Anyone can memorize terms like "frontend validation" and what sort of problems they are associated with, but it demonstrates more skill to be given a problem and know where to go from there.
My guess is that there's a lot of good engineers out there, even senior ones, who get weeded out in the hiring process because they're being asked not to approach problems like engineers but like they're contestants on Jeopardy.
- bschwindHN 8y ago> How do you know if you need frontend validation as opposed to the backend? You _always_ need backend validation. Never trust the client. You can then layer on frontend validation where it's needed to make a better UX.
- ravenstine 8y agoI think that could have been a poor choice of words on my part. From memory, when asked nearly the same question, I don't think it was suggesting frontend validation exclusive to backend validation. Then again, maybe that was how it was phrased. Ugh. Maybe I'll edit my original post. You are definitely correct, however.