DEV Community

Cover image for 50 Frontend Interview Questions

50 Frontend Interview Questions

shrey vijayvargiya on February 09, 2023

Save the blog for the future and CRACK any interview in the WORLD. Under the Hood I’ve given more than 100 interviews in my 4 years of ...
Collapse
 
bytebodger profile image
Adam Nathaniel Davis •

I was recently asked: "What are the Container component and Presentational component?" And it threw me for a bit of a loop - because in my experience, hardly anyone in the React community uses this terminology anymore. In fact, it can even be thought of as deprecated.

Don't take my word for it. Dan Abramov himself states as much in the top of this article:

medium.com/@dan_abramov/smart-and-...

Collapse
 
peerreynders profile image
peerreynders •

In fact, it can even be thought of as deprecated.

That was in 2019.

Now in some circles there is a practice of separating pure and effects components to decouple presentation from effects.

Cognitive Loads in Programming

Collapse
 
bytebodger profile image
Adam Nathaniel Davis •

Pure vs impure (or, as you put it, pure vs effects) is not the same dichotomy as container vs presentation.

Thread Thread
 
peerreynders profile image
peerreynders •

See this discussion.

Both suggest that at times component-centric can be too lumpy.

I think Dan Abramov was getting frustrated that the approach was being mindlessly applied without a priori assessment of the trade offs.

Thread Thread
 
shreyvijayvargiya profile image
shrey vijayvargiya • • Edited

Again it hardly matters, I don't think so we write code with 2 components in mind whether it's presentational or container we just write when we want to write that's it.

Thread Thread
 
peerreynders profile image
peerreynders •

is not the same dichotomy as container vs presentation.

Looks like with React Server Components it's been reincarnated as “Presentational and Data Components”.

Collapse
 
nachiket_salvi_d54a6d4dd9 profile image
Nachiket Salvi •

I built a free, no-signup site for frontend interview practice. The angle is reading a problem and knowing which technique it wants — every question pairs the signal with the tool and walks it easy → hard, across HTML/CSS, browser, JS, TS, React, system design, and DSA. Every code question has a runnable editor so you write and test your answer in place. It's a zero-dependency static site (one build.js, no framework), deployed on Netlify. frontend-interview.com

Collapse
 
taepal467 profile image
Chantae P. • • Edited

Question, do interviewers ask algorithm questions as well?
Great post by the way. Will definitely come in handy.

Collapse
 
shreyvijayvargiya profile image
shrey vijayvargiya •

Yes they do, but basic ones not really in-depth DSA

Collapse
 
taepal467 profile image
Chantae P. •

okay, thank you.

Collapse
 
khalildev profile image
Khalil Dev •

Recently, I had an interview for frontend position. I would say that I was asked around 80% and above of these. Nicely listed!!

Collapse
 
shreyvijayvargiya profile image
shrey vijayvargiya •

Glad to hear that !!!!

Collapse
 
clericcoder profile image
Abdulsalaam Noibi •

Thanks for sharing

Collapse
 
shreyvijayvargiya profile image
shrey vijayvargiya •

Thanks for reading and the comment !!!

Collapse
 
nekomamoushi profile image
nekomamoushi •

The title is a little misleading…

Collapse
 
shreyvijayvargiya profile image
shrey vijayvargiya •

In what sense?

Collapse
 
nekomamoushi profile image
nekomamoushi •

Because the title says FRONTEND questions but it's all REACT questions :)
So for me it's misleading.

Thread Thread
 
shreyvijayvargiya profile image
shrey vijayvargiya •

Well not really, in 2023 frontend development means React is a must.

I've added Javascript questions also, including map, filter, promises, async-await, closures and so on and only those things are asked when it comes to javascript.

Rest, React is imperative so most of the things will revolve around React and that comes under Frontend development itself.