Beginner React.js Coding Interview (ft. Clément Mihailescu) 

Checkout the video we made on Clem's channel where I do an Algo interview: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-vHKzIPwWQkg.html

Interview for a FRONT-END position - "The uglier the better" "This is my jam!" Thanks, we'll be in touch.

Do you know what the scariest thing in the world is? Not knowing how to write a React component in a Ben Awad interview.

As much as most of this makes sense to me as a Junior Webdeveloper, I find it stunning that people can write code from the get go just thinking through the application and using knowledge they've gathered over the years. I literally have to google nearly every shit that I try to make and it really puts it into perspective for me of how much I still need to learn. :)

cool trick: 1. Know nothing about React 2. Watch this video 3. Study React for a bit 4. Come back 5. "oooh"

I wish every tech interview was as friendly

How front end interviews should be: This video How they actually are: ok so can you invert a binary tree for me please

I'd love to see you guys continue this as a series, gradually increasing the difficulty!

This way of interviewing seems way more relative than just doing algorithms, I wish companies would adopt this.

Ben is doing the sassy interviewer stereotype perfectly here.

so i work for him and he works for you...? i may have to quit

i like the fact that clement is humble and admit that he doesn't know about the error upfront

thank you, that was so nice! as a junior I feel comforted seeing this type of interview, I could actually answer those questions without even typing the code. now it would be really cool to see something like this for junior+, middle, middle+ etc. levels!

Thank you guys for making this video. I really enjoyed going through these questions & trying to code the solutions to test myself before watching Clément's solutions . Keep making such videos.

33:06 - you'd wrap fetchNextUser in a useCallback if you wanted to satisfy the linter and pass fetchNextUser to the dependency array. This is because the function is re-allocated on render because it's within render scope, and therefore the function reference changes between renders, causing your useEffect to every time (based on shallow comparison of the dep array), so useCallback avoids that and keeps the reference the same between renders.

seeing some React stuff ( other than algo ), was really exciting. Also learned a lot. Please try bringing many more stuffs like this. Will be happy to watch :)

So much fun just watching you write React in this context. Nice video! :)

This is really good, I've done interviews in C#, python and on regular stuff but had no idea what it looked like for front end, this is a really approachable React interview to practice with!

This should be a series !! With a bunch of different languages, and levels of difficulties

I wish all interviews Front-End were like this. Relaxing, yet, extensive.

I started with react 6 months ago cool to see i was able to answer this stuff. You guys make great videos

"Uglier the better, this is my jam" nailed it.

gender: “female” name: Object 8:32

Great video, love this live coding even though the task isn't that complex, very efficient, and accurate solution :)

Loved this video. Super natural and really funny from both of you. PLUS really useful as well for beginners.

Hey Ben and Clement, nice interview! For your question at 33:11, React encourages you to wrap your fetchRandomData function in useCallback and add it to the dependency array of the useEffect to satisfy the linting 😁 Unfortunately then you'd have to handle the dependency array for the useCallback hook, but it's the "official recommendation". I liked the useRef hack though :) Nice work and entertaining content as always!!

Should totally do the advanced react interview next

Wow, I never knew you could do {name: {first, last}} to convert nested objects into variables, awesome.

Thank you for adding tips and best practices too. Highly appreciated.😃

it feels so good to know what they are talking about :)

I love these two guys! Two of the most trustworthy coding mentors out there.

Very cool. I really like how you both talk us through what's going on.

This is really fun. Do more of this, please.

Awesome stuff ! what I most liked about this video is the fact that Clément was thinking out loud so we could have a better understanding on how he would solve a problem. I would love to see a second video. Thanks guys, from France PS : René Coty was a french president ;)

Interview: Why do you want to join this company? Candidate: I was bullied into doing this interview. lmao

Love this!! Thank you so much! Please provide more videos like this~

This was great!! It's super helpful to follow off-the-cuff reasoning. Coming from Vue and starting to dust off my very limited React knowledge

0:50 Make a counter 3:10 Fetch an API 14:10 Display the API data in UI components 22:06 Add a button to load more results 29:38 Bonus: fix the linter's useEffect dependency array requirement

I used this to practice for my first React interview - it helped - thanks!

Another version for sure, this was one of my favorites!

Can we just appreciate and admire how Clement has nearly 100% accuracy while typing at those speeds

Just got to the gym, still in the parking lot .. can’t stop watching!! Haha great video

For the final bit you can pass your setters in the effect, or memo it instead of ref it. But I usually don't have empty dependencies as linting error. Also, I'm almost sure that if you try to set some state while the component already unmounted you'll get a memory leak error on your log, so to go around that you can return early in the promise resolution by setting a flag on a return function of the effect

this was really fun to watch, and really interesting to see the thought process off it

This was fun and I learned a bunch. Thanks for making this video!

Bro i watched your video just like 30 mins before my web development interview and in the react section they have asked the same questions as you have asked and I have solved all those questions thanks to you 😀😀

i just started learning react few months ago and I am so happy that I understood all the questions and the potential solutions :) Great content!!

This is pretty similar to a recent react interview I had. Nice video and convo :)

This is interesting, I wish all interviews will be this fun and interactive

Clément's confidence started to increase once he figured out that the bug was from line 31 instead of 32.

This is the greatest crossover of all time

beautiful...... I'm gonna get to this level soon bro! that feeling of complete confidence in your problem solving skills is the sweetest thing in the world. Excellent work Clément

Lol, this is really good content. Keep it up guys! I had so much fun watching this.

useCallback instead of useRef - it memoizes the fetch function for ref equality, so the effect doesnt rerun on every render. UseCallback will mean that if you eventually do a refactor so the function *does* depend on some value inside the component, your compiler will yell at you until you include it as a dependency. Useref might solve the problem now, but it can hide future potential dependencies. Also, working with a ref is annoying, constantly looking up .current or forgetting to. If the function used really doesnt depend on anything in the component then it should be externalised if possible.

This is the most forgiving interview I've seen LOL. Pls be everyone's interviewer Ben!

Hey Ben! You should add more such videos. Loved it!

That was an amazing performance, both of you!

Aside from needing to learn more about pagination, I’d get the job 😂 I wish interviews were like this

Clement is such a good sport. Legend! Ben too :)

Best React tutorial format I've seen so far.

Very nice and clear video, didnt get fully understanding on the empty array error and the sol of it... Keep doing videos like so, very much appreciated !

I was dying with laughter when he tried to disable the lint rule with a comment

I've got notification of this video from both channels.

Do more like this!! Super entertaining and learned even more

This was fun to watch. Thank you for this. Also, I have a lot to learn. I was able to follow it, but I need to develop the instincts to find the solutions in a timely manner.

fetchNextUser() is a function that gets newly created on every render call since its defined inside the component. Wrap fetchNextUser() inside the useCallback() hook and mention the dependencies which when changed must create a new fetchNextUser(). It's a bit more efficient this way and I guess that can get rid of the lint error.

Moving from another framework to react I love that I was able to understand all the questions and the solutions and I have learnt more from this video than from many tutorials and courses

every time I watch you guys videos I feel like I am hanging out with the best!!!!!! thanks guys!!!!!!!

This is great @benawad I really wish more interviews like this!

Amazing what’s next a cook book app ?

damn, even I'm nervous for Clement lmao

As someone just breaking into the world of programming this was incredibly insightful!

This was so great. Love your videos, they’re really helping give me more confidence. One side note, never use index on as a key unless the list is immutable. Also, your fetch function was a const, so I’m not sure how the reference would be reassigned.

This guy could probably speed run building startups

I literally had this interview today... Dude launched right into it with no small talk and went through it at 3x speed. It was rough.

I've never been so happy in my life, watching coding videos!!! 😄😄😄

it was a blast watching this, guys. I really like the format of the interview!

For that linter error (which I deal with weekly), take that huge function expression out of the component (it's unreadable to define those in there anyways). Your first thought will be, but now I don't have `setUserInfos` in scope. Right, so pass it as a callback function. You have one function that fetches data, creates a new merged list, and updates 2 pieces of state. It does too much anyways. Ok, but now you're thinking that you need to add `setUserInfos` to the dependency list of useEffect, and you're right back to where you started, right? That's fine, the function that comes back from `useState` is the same exact function on each render. It'll never change. Consider this snippet from the react docs: "React guarantees that setState function identity is stable and won’t change on re-renders. This is why it’s safe to omit from the useEffect or useCallback dependency list."

12:26 we're not gonna catch any errors cuz..... we don't do that here *CEO MATERIAL SPOTTED*

This was actually a very interesting video and was fun to watch. I wish interviewers would learn from this

This is awesome. Great work guys ❤️🤝🙌

imagine saying "the uglier the better" to a front end dev😂 Ps- Thanks for the 200 likes

Bruh, Imagine getting a job.

This was really fun. We need a second version of this but with Auth APIs ;)

this was amazing. Loved that it was frontend ( I never get that in my life anymore)

23:16 So much passion in this

"I'll put this in a p tag" "fantastic...!"

Only a few mins in but this makes me feel better knowing that other people do stuff like trying to call function before it has been declared 😀. Cool interview!

hey Ben, I really like this video, I hope u make more videos like this in the future with other devs.

Jajaja I've never imagined see those two in a vídeo jajaja

Ben, can you interview the Techlead? :D

It was so fun to watch this. Expecting more videos like this.

AWESOME! please do a second part BOTH OF YOU, of course with another topic PLEASE!!! Cheers from Arg

Waiting for the next interview... Angular xD

Clement when you did map - you forgot to assign key attribute.

As a person who has started learning react this gave me a confidence boost since I was able to give right answers

This video was so helpful! I had a job interview and they gave me this exact test using a different API.

At 11:50 You can't use Await directly in UseEffect Callback. Even you can't type async directly into useEffect Callback for example useEffect( async ( )=>{ const response = await someApiCall(); } ) You have to create a new function inside the callback of useEffect and then you can use Async Await. For Example useEffect( ()=>{ async function helloWorld (){ const response = await someApiCall(); } helloWorld(); }) This is the correct approach.

I'm surprised that Clement used axios for the API Question and not just fetch with async await.

This is the kind of content I needed in my life