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.

@xcelestialdemon8245

8 ай бұрын

It does read like a "intro to JavaScript" udemy course 😂

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.

@AlexLazzarotto

5 ай бұрын

Im a self teaching coder with like 1 year of experience and found this interview pretty easy 😅

@josephito27

13 күн бұрын

@@AlexLazzarotto it's easy to understand and follow along what's being shown maybe, not like you can answer them on your own with precision to pass an interview with no sweat with just one year of experience, some of them are really advanced for a junior position.

@jasontricolor2978

8 күн бұрын

Do you know why this is? Because people don't trust new professionals anymore. I don't know if due to bad experiences, or if it is just a bias toward people that are coming to programming, but it wasn't this way before. I've heard from a lot of people that juniors before did a work of a junior and had a knowledge of a junior, and now a junior has to showcase incredible projects, while understanding every single concept of the job, and while having to apply things far from their current knowledge once they step in to a company. The real thing while many don't understand is that having a real job in a company, working with a team, will teach a lot of things, things more advanced about the role itself, and while growing inside of the company, how can a person grow if they don't have opportunities? This is the problem with the market right now.

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.

@WebDevCody

9 ай бұрын

💯 agree

@kalebkloppe6193

8 ай бұрын

This is the difference between tacit and explicit knowledge.

@user-lq1cs

8 ай бұрын

you actually boosted my confidence. thanks brother

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!

@dylanthony1

4 ай бұрын

I feel like the order makes them harder as well. A question about JS hoisting first I find crazy for a jr position

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.

@jonathanjeshualaniba5958

9 ай бұрын

i hope i would not get this kind of interview in the future

@WebDevCody

9 ай бұрын

It sucks that some people think giving an interview should be a school exam

@theminimalist538

9 ай бұрын

@@WebDevCody yeah it really felt like one, usually when I talk to my developer friends the conversation tends to be very chill, enjoyable and interesting, which in this case really wasn't...

@myonlylovejesus887

9 ай бұрын

​@@theminimalist538let us know if u actually got the job?

@theminimalist538

9 ай бұрын

@@myonlylovejesus887 as stated above I did not sadly, they chose someone else because they think that person fits the position better.

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.

That's a lot of questions for an interview 🤯

@Anthony-wg7fn

9 ай бұрын

Yea, a lot of questions that have nothing to do with the job.

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 )

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

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

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

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.

These videos are awesome honestly

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.

@WebDevCody

9 ай бұрын

I agree, showing you can apply these things is much more important than being able to explain them. You’re not hired to be an educator, you’re hired to solve problems

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"

@IShop-2023

9 ай бұрын

you could also call other class component refs methods inside of another class

Good job babe!!!

That was good, thanks for sharing. As a non React nor JS developer, I would have liked to hear about functional components. ;)

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

Arrow functions don"t set `this`, allowing the value from the outer scope to be accessed. Also, `{` & `}` are "braces". `[` & `]` are "brackets".

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. 🤢

@dandogamer

9 ай бұрын

Solid is one of those things juniors and grads obsess about, once you get to a level of seniority you can identify most of it from code smell.

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

I can only remember like 1/3 or 1/4 off the top of my head

I am actually very surprised about these questions... In my country you first have an interview with HR (some companies) and after that you get sent a test task which you have about one week to finish and send back (all of the IT companies). If the task is completed correctly you then have a technical interview where you showcase your code, they ask you a bunch of questions about why did you do it the way you did it... And that's it, none of this "theory" stuff... I applied for 3 junior dev jobs and all of them were like this. If I think about it, you do kind of "use" all of the knowledge above when trying to complete the given task that the potential employer gives you. In one interview they gave me 3 hours to implement a feature.

@popalopagos

9 ай бұрын

It's because it's America

@josephquintiliano2904

9 ай бұрын

What’s was the feature lol

@kreten780

9 ай бұрын

@@josephquintiliano2904 My task was basically building a client email app, which would use IMAP and SMTP protocols. You could send emails, you could show current conversations... (all of the email stuff). The additional feature was to add some filtering and a search bar for the emails. I used React and they wanted me to use native PHP (which was painful).

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.

@WebDevCody

9 ай бұрын

Knowing all of these in detail probably means you’re the type of dev who invests more time in the need technical side of a language instead of focusing on business needs. I see it with other people geeking out over various programming languages and paradigms, it’s fun but provide very little value to businesses

@cybroxde

9 ай бұрын

@@WebDevCody Definitely. I might be biased since I come from the hardware/ASM world originally but I think there's great benefit in people learning and reasoning about these paradigms. I do however also agree, that it is rarely ever benefiting your business case, it's more of a personal pursuit of knowledge which may or may not reflect in actual business value depending on your industry. Web-dev is definitely the least likely to benefit from this, though, unless we're talking extremely high levels of scaling or similar challenges.

Frameworks like Svelte and Solid has achieved better performance using the actual DOM. I think now a days real dom has become faster than Vdom implemations.

I've noticed a relation between low-salary and high-expectations on postings/interviews. If I got hit with all this I'd just say thanks and bail.

Imagine I was asked to build and LRU cache for a junior front-end position at microsoft.

@WebDevCody

9 ай бұрын

and you're tasked to draw rectangles on a page after you get the job

I'm not really familiar with the average knowledge a junior should have in the US, would you consider those questions easier or rather difficult ?

@tathagatmani

9 ай бұрын

IMO these should be the type of things you ask to break the ice

@piotroszko2

9 ай бұрын

I had a successful job interview about a year and a half ago for the same position (js/react junior). I had very similar questions. Most of those are just to see if you have more or less a grasp of the language and React. You don't need full answers, it's enough that you at least know what it's about, etc.

@popalopagos

9 ай бұрын

@@tathagatmani The difference is that you're allowed a social life in other countries. You can get a senior role if you can 'get the job done'

@joshuawalker7375

9 ай бұрын

I haven't started applying for jobs yet but I've been studying dev for the past 1.5 years and I was surprised by how basic this test was. I'm under the impression that most interviews will include practical problem solving exercises and a greater range of technologies. Regardless I knowing all the answers to this test I still plan on furthering my education before applying for jobs in the US.

Do you edit your videos or do it as little editing as possible?

@WebDevCody

9 ай бұрын

I try to record my entire video in one take then I edit about the parts in-between. I don’t script anything

@codedusting

9 ай бұрын

@@WebDevCody Cool. So a perfect balance between live and recorded. Thanks. Will try to apply this method

Wow, I actuallly think these questons are realistic and important to know for more solid js understanding, but def not all of them as a junior through consistent practice

To pick nits, HTTP = "Transfer Protocol", not "Transport".

"Typescript basically allows Javascript to not suck" 😂

Whats youre visual studio code extensions name list can you share?

@WebDevCody

9 ай бұрын

Bearded theme stained blue

While I do this the industry gets out of hand with this, it’s better for them to boost their false negative rate, assuming they don’t make it so hard that they have an open position for months and months.

where's the beard at :(

👍

Cool

What's your colorscheme? on vscode

Pls, make a codediscount for your course:((

Just a stupid question. What theme are you using for vscode😅

@WebDevCody

8 ай бұрын

Bearded theme

@medamine3142

8 ай бұрын

tanx bro@@WebDevCody

These are some basic questions tbh and you did a good job to explain them easily

Are you sure I was all of these just for to go for next phase internship they wasn't even job

It basically makes javascript not suck 😂😂😂

Man, where’s the beard?

Looks like one of the clueless HR interview...

What should I do? I can't understand the English...

Never been this early

no way people still use xhr in 2023

@WebDevCody

9 ай бұрын

Idk, someone recently sent me code snippets from a project they were working on and it had xhr everywhere, it was a legacy system. Even so using axios or fetch allows for an AbortController

Class components might be easier to understand imo 🤔 If we compare the useEffects with it’s class component matcher onMount, onUpdate and onUnmount are easier to understand. Writing multiple useEffects in one Component is also too ugly (form libraries use this approach) imo. So u may like the onMount approach This is the only benefit of class components imo

@WebDevCody

9 ай бұрын

I agree, use effect can get crazy, but it allows composition

First!

I hate.my.life

I appreciate your effort here but, I strongly disagree with you on the point that: "You don't need to know how to explain it, just show some code.". Maybe not as a Junior but the ability to explain using the correct terms is invaluable for a Senior. Especially since you're expected to teach Juniors. If you can't then there is no shared vocabulary and that will increase friction when communicating about code. Since there is no way to explain a concept other than creating more code, explanation will become a hurdle which is completely avoidable. Yes, if you're a beginner and learning then examples are best. But, the examples are intended to allow a beginner to create an abstraction, chunk it and build on for further learning. That abstraction requires knowing the correct terms and it helps you when you're communicating.

@WebDevCody

9 ай бұрын

This was a junior interview, so I stand by you shouldn’t be able to explain these concepts like you’re a senior developer. If you can show code and say this is what I understand being a closure, that’s good enough imo. I know senior devs who could not easily explain a closure, but they could easily code one without thinking. Teaching is a learned skill that also requires planning depending on how complex the topic is