Senior Frontend Developer Interview Questions 2024
Вставка
- Опубліковано 26 бер 2024
- ------------------------------------------------------------------------------------------
👇🏼 HOW WE CAN HELP YOU
🤔 Find Your Technical Gaps With This FREE 10-Minute Technical Assessment
learn.theseniordev.com/techni...
🚀 Get Rid Of Impostor Syndrome And Fast-track To Senior Level
learn.theseniordev.com/free-tr...
------------------------------------------------------------------------------------------
Find your technical gaps with our Free Technical Assessment: learn.theseniordev.com/technical-assessment 🎯
This was a great video! Love the depth on the answers. This should really help people to get a better sense on what they can expect in the interviews and how to approach answering a question. Would love to see more videos like this one 👏
Great video loved it. Pps bring more videos on senior Frontend content. Keep going!🎉
Move of those coming soon @onecurious
Quite good (and important) questions. Cheers, guys!
Glad you found it useful @renato
I've never heard of anyone using the term "essential state" before In React. I even tried googling "essential state" and found nothing lol. I assume this question is more or less asking about being able to have computed values that rely on other state using something like useMemo or something? It's kind of a weird way to phrase the question.
The answer that was given in the video was such a non-answer as well, it was basically "essential state is state that can't go any farther". Like, what does that even mean? It can't go farther? Where is it trying to go?
Anyway, if anyone is reading this and wants to know about derived state. I think the answer given is a vague overview, but more specifically it's basically the idea of composing a value based off of existing state. You can just make a normal variable for it honestly, there's no reason why you can't. However, you can also use the useMemo hook if you need to memoize it for performance reasons. In the future with React 19, the new compiler will reduce the need to manually memoize various things like with useMemo or useCallback.
outstanding answers for the questions!
Glad you enjoyed it @nazardzys
Amazing.
Thanks a ton❤
You are welcome @chiran! Glad you enjoyed it :)
Great session , preparing for an interview in 1 hour and just saw it , questions i didn't think about and make so much sense.
Best of success @iziversano
Great video, thanks guys 👍
You are welcome @cankat
Amazing video. Thank you 🙏🏻
Thank you @anastasia
nice, need more vids like this. Im your follower now)
Awesome @MeLu! glad to have you on the channel
I believe the answer about Pure Component is slightly wrong.
Pure components as far as I know are still quite often used.
In Function Components, for example, you can create a Pure Component by wrapping it into a React.memo function.
In React, again, as far as I know, everything below the component that changed is re-rendered. If the child component is a Pure component, the re-rendering propagation ands in this component IF the props passed to it has not changed.
Hey @rjborba, referencing the React Documentation:
"Unlike PureComponent, memo does not compare the new and the old state. In function components, calling the set function with the same state already prevents re-renders by default, even without memo."
React.memo and PureComponents are two very different things and in functional components, memoizations happens at many different levels by default so there is no need to use PureComponents.
Referencing the docs, functional components are preferred with React.memo rather than PureComponets(class based). You can read more here:
react.dev/reference/react/PureComponent#migrating-from-a-purecomponent-class-component-to-a-function
@@therealseniordev I’ve been trying to answer back but by comments keep vanishing. Maybe because I’m sharing an link to a implementation that exemplifies what I’m trying to say. But as it seems to be not possible, I’m going to explain myself here.
First of all, I’m a big fan of your work. Thanks for these videos. They’re pretty helpful.
About the pure components, it is unrelated to use state change. It is related to prevent the children to be rerendered when the parent is rerendered for changes in states that the children is not dependent of. So, essentially as it is today, pure components are components that has a MEMO call. Documentation is a bit misleading regarding that. They just stop the natural propagation of react rerender
@@rjborba From what I understand as a junior dev, here are some key points and I am kinda confused:
1. The senior developer was trying to connect pure components with props, that pure components won't re-render if the incoming and existing props are same.
2. But you're suggesting that pure components has nothing to do with props or state but with parent components renders, and a pure component won't re-render if some parents state changes.
3. Finally the definition of pure functions states that "a react component is considered pure if it renders the same output for the same state and props".
@@rjborba You are conflating something key: a Pure Component is a specific React implementation for class components, which is different than how we talk about things like "pure functional components" today. So it is indeed related to state changes.
thanks !
You are welcome @nutan
Awesome interview conversation bro's❤
Thanks @GreenWorld, glad you enjoyed it :)
In my experience I'm totally against asking for acronyms or enumerating many things like (say the patterns you know). It happened to me that many times you know how to use something but maybe you don't remember the name (like IIF). Or you use a pattern and you are unaware of its name (module pattern for example).
Well done video. But you should mention this is for a React Developer
Noted @Johan
Nice
Thanks :)
crazy level.
i couldn't answer any questions :(
More of like the candidate is holding a guest lecture and the interviewer is clearing his doubts 😅
yes, we had to move into that direction to give more value to the audience, is a mix of both, lecture and interviewing, hope it is helping you folks :)
@@therealseniordev Yes definitely really helpful. I was just trying to express the extent to which the candidate was experienced. 😅
in 2024 do we really need to learn 'webpack' and 'babel'?, 'create-react-app' / 'vite' etc are doing everything in the back, we just need to know about what they are and how they actually work in the backend, am i correct ?
hey there, ideally you do know how to set them up also - if you are going for a Senior position they will always ask about it. The problem with vite / creat-react-app is that the complexity is hidden - however as a senior you are expected to know what happens under the hood and the best way to see that is by setting up smthign like webpack.
Thanks..
Basically, not bad, basically
glad it helped :)
is this really senior level questions? where are those about type coercion, backtracking, event loop, generator functions, inheritance etc?
this is a Frontend focused interview, not a JavaScript one, type coercion => TypeScript, Event Loop => JavaScript, Generator Functions => JavaScript, Inheritance => OOP & JS, we are pulling different series, this video is focused on more FE related questions, cheers
FrontEnd is so endless in technologies, names, paradigms, libraries, etc that it is virtually impossible to give one only type of interview. Depending on the role the company looks for they can be interested in architecture, patters, CSS and styles... Hundreds of possible combinations and limited time. One can not be answering, explaining, doing assigments etc forever
Why is this common standard? If the candidate have documented experience and education, this should not have to be "tested" again and again. The narrative as a whole is sick, and we need to start trusting people instead. You're hiring a human being, not a machine. I get that you might have questions about skills and competence if the candidate has no experience, and bare minimum education. But to treat everyone like this, is disresepectful towards those who are experienced and educated. I disagree with this entire approach as default.