3 ms·
I’m imagining many of the people who are against this idea have never been on the interviewer side. Or aren’t web developers and feel they should be able to ans
by dinkleberg 5y ago
I’m imagining many of the people who are against this idea have never been on the interviewer side. Or aren’t web developers and feel they should be able to answer this regardless.
The intention of questions like these aren’t to see if you know all the answers, it is to have a discussion and to learn about your experiences and see how you think.
Also if you’re applying for a web dev role and you’re not fairly familiar with what real world HTML looks like it’s may not be a great fit. You may not remember the exact syntax (because who care, you can google it), but you should have an idea of what you’re sending over the wire.
- noahjk 5y agoHN: complains about leetcode-esque interviews Also HN: complains about alternative conversation-style interview I don't work on the front-end, but I have had a general curiosity for it for a while, and I think this would have been a great conversation starter! And I think a lot are missing the point that the interviewer isn't exactly using this to just "fail" people. Like you mentioned, these are the sort of out-of-the-box conversation starters that good interviewers try hard to come up with so they don't have to just give coding tests and ask the top 30 JS trick questions that are easily googleable.
- degenerate 5y agoExactly -- it gets people talking so you hear how they communicate and solve problems.
- tgsovlerkhgsel 5y agoAlso, people who haven't been on the interviewer side have no idea what kind of idiots apply to jobs they're absolutely not qualified for. Like web developers who couldn't make a reasonable guess at more than two of these lines.
- woutr_be 5y ago> The intention of questions like these aren’t to see if you know all the answers, it is to have a discussion and to learn about your experiences and see how you think. I get that this might be the intention, but if you're being interviewed, and asked to explain the first 10 lines of some code, you'll rightfully feel nervous, and feel as if this is a pass or fail test. If the intention is to make this a discussion, perhaps change the question, and start the discussion yourself.