3 ms·
The best questions are the simple ones that start a conversation. That only works if the interviewer is confident in their ability to read people and competent
by iratewizard 5y ago
The best questions are the simple ones that start a conversation. That only works if the interviewer is confident in their ability to read people and competent at their job. These articles are written by and for people who don't meet those criteria.
- heavyset_go 5y agoI just don't see the value in the questions from the OP. What if the person being interviewed genuinely doesn't know and says, "I don't know"? Asking them to then guess what the markup could mean doesn't really tell you much about their skills or abilities. It feels like a potential dead end to me. I think there is better material to review and ask questions about that actually pertains to the abilities of the interviewee or the skills needed for the job at hand.
- tgsovlerkhgsel 5y agoThere's 10 lines. If they're applying for a web development role and say "I don't know" to all of them, it tells me enough about their skills and abilities to end the interview right there. If they don't know half of the trivia but tell me "this looks like it probably controls browser feature X", and they're making a reasonable guess (regardless whether it is correct or not), that's a good sign. If they don't know something but confidently pretend they know and spurt bullshit - red flag. I don't want to have to second-guess everything they say, and have them deliver something that looks right while being completely wrong. If you don't know what that specific prefixed attribute does, I don't care. If you don't know what a vendor prefix is in CSS, you haven't written much CSS.