Home
Starting Up
Case Studies DB
Products
Ideas DB
Vibe Coding Tools
Subscribe to IH+
Starting Up
Case Studies
Ideas DB
Products DB
Sign in
Join
5
Likes
3
Comments
Curated list of 44 Frontend Interview Questions
by
Victor
https://twitter.com/vponamariov/status/1518247390679076864
Why would you ask these questions? It's probably a stressful quiz that doesn't assess capabilities but rather memory of basic concepts.
I am not sure it's the way to go, feels like worse than a whiteboard interview.
But maybe I'm wrong?
On the contrary, these questions almost have nothing to do with memory abilities. They are not like "what will be the type of NaN" or something.
When you work as a frontend developer you usually:
And all of that. Nothing what I wrote in this answer I googled. It's just a typical workflow:
"Hey guys, we need to display a list of cards on this page, so the API request is this, don't forget to proxy it due to CORS issue we have, and yep, these cards should have a nice close icon positioned absolutely in the right-top corner."
Some of difficult questions are called difficult for a reason. Assuming a customer says "Hmm, the menu animation is slow for me, what's wrong with that???", and you know all that reflow/repaint concepts, and you can optimize animation.
Or such questions as Virtual DOM - well, that's how frameworks work.
Or how to make authentication. How can we call it a quiz or memorizing? We can have many ways of making authentication, communicating with API (graphql/rest), etc.
EXAMPLE of memorization:
Okay, there is a question about data types. It should be asked not in a way: "Wait, you named 6 types but there are 7, you forgot BigInt!!". No. But if you stars saying something like "pointers, chars, lists", then you're probably C++ developer. It's an intro question just to check that you know that there is null, number, object, bla bla
After last fails looks useful for me:)))