markdown guide
  • How does a browser request for resources; what are verbs and the fundamental headers (content-type, cors & origin issues)?
  • What is hoisting? How does it impact code execution?
  • What are closures? Common applications?
  • What's the reason behind the infamous behaviour of this? Why we have to bind it?
  • Arrow functions vs function expressions, what's the practical difference other than the syntax?
  • Why do we call functions 1st class in JavaScript?
  • How do you listen for events in JavaScript, and how do you deal with bubbling and unwanted side effects?
  • == vs ===. Why we want to avoid == as possible?

  • Common issues with accessibility: nonsemantic HTML, handling focus, contrast ratios and color blindness

  • "Controlled" vs "uncontrolled" HTML elements

  • Semantic tags?


A lot of these are great but come from a line of 'traditional' / 'booksmart' thinking..
which is great for probing and making sure candidates have the knowledge behind knowing how to answer the question... but for a lot of these i'd accept an "i don't know, but i'd look at the API docs for this method/class and learn how to manipulate the js object or function to my need"

yakno? js evolves so quick; knowing the fundamentals of OOP + quick absorption of docs + knowing how to quickly iterate = a winner


I was mostly pointing out the common ones for front enders.

The memorable ones from my last interview were also:

  • how do you approach this one project, where do you start, what's your thought project

  • how do you deal with a colleague that won't give up an idea that you find very wrong

  • will you trust your boss decisions even if you won't always get the entire picture

I don't know if you can "study" these


OOP is mostly a disservice to producing quality code

  • Please estimate how long it would take to build this webapp based on these requirements?
  • What if you only have half an hour?
  • Let's build it. Now. Together.

This gives us insight in how you handle challenges and if you can prioritise the features that bring value.


"Do you agree that React is massively overused and is basically like using a sledgehammer to crack a nut in most cases?"


Assuming they'd be expected to know about the "virtual DOM", popularized by React and others, asking why the virtual DOM is needed and how it generally works high level.


What is the difference between the focus and the caret ?
(Actually I use that question when I am grilled by people who know a js framework very well, have very limited frontend knowledge and try to establish a position of dominance. )


Do you think that tools like Webpack, SASS or jQuery made us to use them even for a single landing page? And what would you do to avoid it?

Classic DEV Post from Nov 9 '18

Multi-cursor in Visual Studio Code

Multi-cursor is one of those features that impresses many non-programmers but, ...

Christina Gorton profile image
Web Development Instructor and Front End Developer. Check out my courses on Design+Code and SkillShare