My interview is the same as my mid-level interview but judged for a lower level. I give them a problem they likely are familiar with but wouldn't do a lot. Then I watch them google and debug. They don't have to get it right or even make much progress! I'm just looking to see how they solve their own problems. They can also ask questions. If they have those skills then they're in a good position to succeed no matter what projects they wind up on.
That's great. I hope to get an interview with someone with the same mindset and methods. On my very limited journey into coding, my curiosity has been my number one reason for the (very small at this stage!) wins so far. If there is anything I hear that I don't know I have always jumped onto Google. To find a career where my curiosity to solve problems is rewarded would be phenomenonal.
I agree completely.
Critical thinking is an essential facet of working in any aspect of software and there's rarely anything wrong with asking questions if it will help you accomplish your task.
Programmers who research on their own and have the ability to quickly pick up an API or learn an unfamiliar library's syntax (especially in today's world of npm) if they find it will help solve their problem are some of the most efficient programmers out there.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.