A subscriber was asked these interview questions for a junior front end role (React)

[ionutsandu]

Man this wasn't a junior level interview when I stepped into industry. I believe there are many mid-senior level developers out there not knowing the answers to all those questions.

[Sweet_Solos]

This looks like one of those clueless HR job postings with 10 years of experience required for a framework that literally came out a few months ago.

[mUrMajster]

Funny thing, we ask a lot of these question on our interviews, but it is to define mid-senior level. I would never bombard a junior with them! Jeez!

[kengreeff]

Far out, that is hectic for a Junior position. I've built a lot of products and don't know half of the answers. To be honest, I don't even think you need to know the answers when building actual applications. The best skill to have is the ability to find answers when you need them.

[theminimalist]

Hey Cody, I'm the guy that sent these questions. Yeah there were some more questions like Object.Prototype and some other JS stuff (can't remember because there was so much questions). The interview was long-ish it lasted for almost an hour. I did get response from them after a few days saying I didn't get the position because they chose some other candidate over me which is fine, it's a normal thing that happens to anyone. Thanks for covering these questions, I'm sure they are gonna help anyone that is preparing for their coding interview. And also I wanna note that the interview felt very awkward because the interviewer didn't have a normal conversation where we discuss and talk about these topics, it felt like I came to a quiz where I just get asked question and answer to questions without further discussions/talk. It was just weird and it felt very awkward, it didn't feel like a conversation.

[RatedSTARz]

I love these videos. Its so good to see these pop up and use as a good review. I keep forgetting one or two things and i feel like its cementing my knowledge each time i see these. Doesnt matter if ive seen similar reviews already I think its great to keep posting your take/review on these interview questions even if they are the same.

[mpotane]

That's a lot of questions for an interview 🤯

[Ca-rpbv]

Meanwhile the junior exam that I created was basically asking the person to use useEffect and useState lol ( and I would keep doing the same )

[DerEd]

Very interesting video, thank you! 30:29 the only reason I could think of to use a class component would be as an error boundary, since functional components do not have an equivalent to "componentDidCatch"

[cybroxde]

Nice, the video is a great overview. I'd argue the answers are more elaborate than expected from a junior, but that's kind of the point here. :)
Personally, I'm not a huge fan of throwing terms at people and see if they can reiterate what they have memorized. 80%+ of this can easily be wrapped in short exercises that - given a proper evaluation process - can tell you if the candidate knows enough about these topics to apply them properly.
But being able to put the explanation in words is certainly a benefit.

[tmsk]

I love this videos, ill start getting interviews soon, so your content is helping me a lot ! thank you!

[nottodaybro]

Great video! I am aware these are basic questions but in reality I really wouldn't be sure how to answer them, rather show them in code.

[dysb]

Arrow functions don"t set `this`, allowing the value from the outer scope to be accessed.

Also, `{` & `}` are "braces". `[` & `]` are "brackets".

[atulraj]

I think there are two virtual doms used by react for comparison and then finally based on any changes the real dom is updated.

[drewbird]

I don't think I'd want this to be the whole interview; but, its a good way to hear an interviewee explain their understanding.

I once had a live interview where each coding question involved JS-isms as a trap. "What will this return?" 🙄 Same interview, they asked me what the SOLID principles were; I said, I knew about them but that I wasn't really very familiar. Then, they had me basically try and guess what each principle meant based on the name of it. 🤢

[christiangoran]

"Typescript basically allows Javascript to not suck" 😂

[elvisgarcia]

I'm getting ready for Data Strucures and Algorithms and this video is very Helfull for basic javascript questions

[mohamadelgendy]

I just found your channel and you're good! Keep up the good work and looking forward to follow along!

[wobsoriano]

This is actually a good list to review. Thank you!

[cybroxde]

Oh and you'd have probably gotten bonus points for telling them that JS does not actually have OOP classes and inheritance but just a prototype model from which objects are derived and which is layered on top of each other on subsequent inheritances. But to be honest, I've worked with JS for > 10 years and if you're using TS + ES6 Syntax in a modern environment, knowing this is probably only for bragging rights at the interview.