The second question says "Select the proper order" but only lists single options, then when I clicked (thinking I was supposed to rearrange them) it just showed me the answer. From what I can tell it cannot be marked as correct or incorrect like the others. The use of the word "select" is confusing in that case.<p>While I realize these are toy problems, I would stay away from using "==" in an interview (or at all, unless you are contributing to a codebase that uses it). The reason is pretty clear from looking at the equality diagrams[1,2]. If you use "==" in an interview you should expect to be asked questions about how it works.<p>Will this evaluate to true? ( [1] == true )<p>How about this? ( [0] == true )<p>This one? ( [] == true )<p>This one? ( [[]] == true )<p>This one? ( undefined == null )<p>I would rather not spend my time in an interview talking about the JavaScript equality operator's Bizzaro World counterpart.<p>1. === chart <a href="https://i.stack.imgur.com/62vxI.png" rel="nofollow">https://i.stack.imgur.com/62vxI.png</a><p>2. == chart <a href="https://i.stack.imgur.com/35MpY.png" rel="nofollow">https://i.stack.imgur.com/35MpY.png</a>