In my experience interviewing candidates and being interviewed, the experience is wildly inconsistent. Most times, if it's a Front-End specific position, I woul

In my experience interviewing candidates and being interviewed, the experience is wildly inconsistent. Most times, if it's a Front-End specific position, I wouldn't (and haven't been) asked about algorithms or data structures. I think the most important thing is to be able to talk intelligently about a bunch of subjects. Some examples: - Do you know a client side MVC? Do you know why the internet thinks this client side MVC is bad? What are some alternatives? When should you use what? - Why is SASS valuable? - In javascript, describe the this keyword. What is the difference between Call and Apply? Bind? - What is prototypal inheritance? How do you feel about it (no right or wrong answer, just a thing to talk about). - Typical web security vulnerabilities. If I whiteboard a candidate usually it'll be something very basic, something like write a palindrome function in JS, then write it a different way, then tell me when to use which. Also, I ask a lot about a candidate's interests. Why do you think Elm is cool? What've you written with D3 that was nifty? Talk about the problems you've solved, how you solved them, and why it was interesting. Most importantly: be passionate about learning and doing.