For a junior full stack position this interview a complete non-sense :D As you mentioned, this feels like a final exam in school where you need this stuff to be written in your mind from the night before. If I would be interviewing a junior I would rather see them in action with some code demo or ask them more practical questions to reveal their passion for programming. With that passion and mental support they can grow and get better over time. The last two question were just humiliating and sadly might also be the reason why many people lose any passion that they gained during their learning experience :(
Im a Softwaredevelopment apprentice in germany and these questions are exactly like my exams in my 2nd year. I actually think theoretical questions (e.g.: how are server requests beeing handled?) can be a good indicator of an future employee's knowledge, but letting them work with code can't be a bad choice. Nevertheless I have to admit, I don't exactly know what the average level of a Junior Dev in America should be and how much experience they shouldve gained before they take a Junior dev position.
@@krypton366 We shouldn't avoid theoretical questions. However we should approach them in a different manner. Why not join these questions with some examples? A great example for any fullstack position might be implementation of a API controller with a few endpoints and on that you can extend the question into how you can access these endpoint and you can go as far as you want in the interview. You could potentially end up into asking how client-server communication works. By this you give a lot more breathing room, more interaction than just straight up pulling a question and waiting for an answer.
Right. I don't get why we need to remember what we can easily get an answer from googling. Mathematician is someone who can calculate something calculator or computer cannot calculate. Programmer is someone who can tackle problems and solve with any information by search and logic.
I'm always amazed at your responsiveness to your viewers. You do such a great job for us daily and even respond to critics. Thanks for doing this, I thought it was a great idea to answer some of these! (even if a lot of them are bogus / dumb questions to ask a junior FE dev)
Agree with everything here. To be fair, none of these questions are necessarily hard. However, if someone ever told me, "come on, you should know this because you're x or y," I'd straight up say Fuck you and quit the interview right then and there. I've worked with lots of people like that and they're almost always idiots/low-level. The higher level you go the more humble people get, ironically.
Great video! Love the content you do regarding interview questions and home tasks! Keep it up 💪 I know that there are lists of questions but could you do a list on the best interview questions regarding fullstack and/or frontend with react?
I gave an interview last month for a full stack fresher position and every question you explained was exactly word to word asked in that interview, even the assignment was exactly the same. Wish I had come across this video before giving the interview. I also didn't have any prior experience with AWS services but completed the project successfully. Got rejected.
Hi Cody! Another great video! I really appreciate how genuine you are with the questions, whether they're ridiculous or not appropriate for a junior position. By the way, sorry if I there is already a video about this, but is there any chance that you could explain how a full-stack application would be deployed? For example, a blog website. I'm asking this because I don't really know how the front and back end fits together in terms of deployment and I got lost about topics like serverless and edge.
I have 1 year personal experience, 0 years professional experience with Node, and 5 years Java Spring experience. Learning all these new technologies takes time, but I made a commitment to deliver a Node application despite my team having mostly a Java background.
if this was asked during my interview i would just fail anyway and find a new one these probably my computer test questions back then when i was still on senior high school
As a junior software developer who just got from college, having theoretical knowledge, it have to be easy to answer this question, moreover not every interviewer expects you to answer/know all these stuffs, but if you answer any question, the main thing is how are you answering, how deep your knowledge is, if i ask a topic and i will let the interviewee to drill down more about that answer. That's all, how you accept that you don't know stuff but if you ask them, tell me the answer, they will think of you as a curious person and maybe impressed by you that you didn't know the answer, but want to know. For the last heavy application development, the interviewee should ask money to build that😂😂
Kind of makes sense to ask these questions for a technician but for a junior dev it’s way too much. As a senior architect with 10+ years experience, I am dealing with these things everyday just so a junior dev don’t need to worry about it.
Seems like an interview testing what they expect a student to have learned in college as opposed to what they'd expect a junior developer to do on the job. Would this interview someone is the best candidate for a particular job? I guess it largely depends on the job and the training they provide
to play devil's advocate - we don't know the company and what their product and how it relates to understanding networking protocols. Did the job description say that they need knowledge in this domain? - is so then its on the candidate to prepare in advance
I think the interviewer wanted to mess with him because he said he is an "engineer". Being an engineer means you have lots of knowledge/degree and should already know meanwhile anyone can be a developer.
Those 2 first questions look to me like they are supposed to be warmup round, since those are things that are pretty basic, assuming you are a CS student. The rest was just dumb.
It is painful when the interviewer asks these types of questions to put the interviewee putting him/her on the spot and make feel bad if they don't know the answer, I believe that the interviewers should try to encourage the interviewee even if they don't know the answer. I feel bad for the person that had this interview, once the interview finished it must has been painful and demotivating to have experienced that, I wish you more luck on you next interview and that you don't have to go through something like that again.
I think it's a bit ambiguous for the position "full-stack". Like you mention, it's completely useless to ask a web developer who only uses HTML CSS and JavaScript questions like these. But if you're involving backend as the position states, these questions are legit, at least for Junior positions. Because I think that, if you cannot answer the basic questions, it would probably mean you're lacking of something. Those types of questions are not lke you have to study days and nights to know, they just come to you as a nature if you face them enough and it just sticks with you forever. If you apply for a full stack position that involves servers and you cannot tell the difference between TCP and UDP or how the internet works, maybe apply for a frontend position.
I've went through a bunch of interviews for a mid full stack position, to be fair most of the questions were reasonable, like: explain SOLID JOIN vs LEFT JOIN what is REST some JS live coding challenges - for example: how would you implement `map` function for JS (hint: put it on prototype) some basic TS questions - what is type any implement a CRUD API in Nest.JS ___ ^ To me, those assignments seem reasonable in terms of how they relate to your daily work. Questions that I saw on your video are absolute BS IMO, because: 1. Not particularly relevant for job 2. Not to mention, should target mid level developers.
What guy? These are legit questions a company is asking him during interviews. I’ve know this subscriber for almost 2 years now and I’ve helped him land his first job.
That 8th one should have told him what kind of company it is and walk away, hell in 4 years of uni only questions 1 2 3 were covered rest were coding and algos
I can honestly say as a full stack web developer, I've never had to even think about UDP...
For a junior full stack position this interview a complete non-sense :D As you mentioned, this feels like a final exam in school where you need this stuff to be written in your mind from the night before. If I would be interviewing a junior I would rather see them in action with some code demo or ask them more practical questions to reveal their passion for programming. With that passion and mental support they can grow and get better over time. The last two question were just humiliating and sadly might also be the reason why many people lose any passion that they gained during their learning experience :(
Im a Softwaredevelopment apprentice in germany and these questions are exactly like my exams in my 2nd year. I actually think theoretical questions (e.g.: how are server requests beeing handled?) can be a good indicator of an future employee's knowledge, but letting them work with code can't be a bad choice. Nevertheless I have to admit, I don't exactly know what the average level of a Junior Dev in America should be and how much experience they shouldve gained before they take a Junior dev position.
@@krypton366 We shouldn't avoid theoretical questions. However we should approach them in a different manner. Why not join these questions with some examples? A great example for any fullstack position might be implementation of a API controller with a few endpoints and on that you can extend the question into how you can access these endpoint and you can go as far as you want in the interview. You could potentially end up into asking how client-server communication works. By this you give a lot more breathing room, more interaction than just straight up pulling a question and waiting for an answer.
Right. I don't get why we need to remember what we can easily get an answer from googling. Mathematician is someone who can calculate something calculator or computer cannot calculate. Programmer is someone who can tackle problems and solve with any information by search and logic.
Would've assumed there'd at least be questions on SQL, REST, HTML, CSS, JS, maybe one or two frameworks; you know, the basics
I'm always amazed at your responsiveness to your viewers. You do such a great job for us daily and even respond to critics. Thanks for doing this, I thought it was a great idea to answer some of these! (even if a lot of them are bogus / dumb questions to ask a junior FE dev)
It feels like company owner googled "CS curriculum" looked at what's in there and came up with some questions from them :D
Good luck to that company on finding a “junior”, sounds more like they’re looking for a senior dev they can underpay
true that!
Love these type of videos, very informative and useful thanks
listening to your explanation of question 3 refreshed a lot of forgotten knowledge I learned in my networking class a month ago lol
Agree with everything here. To be fair, none of these questions are necessarily hard. However, if someone ever told me, "come on, you should know this because you're x or y," I'd straight up say Fuck you and quit the interview right then and there. I've worked with lots of people like that and they're almost always idiots/low-level. The higher level you go the more humble people get, ironically.
Great video! Love the content you do regarding interview questions and home tasks! Keep it up 💪 I know that there are lists of questions but could you do a list on the best interview questions regarding fullstack and/or frontend with react?
your content is a blessing for us, thank you
your videos are great my guy, keep it up
I gave an interview last month for a full stack fresher position and every question you explained was exactly word to word asked in that interview, even the assignment was exactly the same. Wish I had come across this video before giving the interview. I also didn't have any prior experience with AWS services but completed the project successfully. Got rejected.
I've been asked these questions in written university exams. Crazy to think people are being asked this stuff to get into web dev lol feelsbadman
1 bit equal to how many bytes. I thought he meant to calculate the fraction 1 bit = 1/8 byte lol
Hi Cody! Another great video! I really appreciate how genuine you are with the questions, whether they're ridiculous or not appropriate for a junior position.
By the way, sorry if I there is already a video about this, but is there any chance that you could explain how a full-stack application would be deployed? For example, a blog website. I'm asking this because I don't really know how the front and back end fits together in terms of deployment and I got lost about topics like serverless and edge.
I can try to make a video on that
I have 1 year personal experience, 0 years professional experience with Node, and 5 years Java Spring experience. Learning all these new technologies takes time, but I made a commitment to deliver a Node application despite my team having mostly a Java background.
Nobody cares
@@lvar5621 Of course, if I cared what everybody thought, I’d be handing out stacks of cash.
if this was asked during my interview i would just fail anyway and find a new one
these probably my computer test questions back then when i was still on senior high school
interviews seem to be going to the opposite side of evolution
As a junior software developer who just got from college, having theoretical knowledge, it have to be easy to answer this question, moreover not every interviewer expects you to answer/know all these stuffs, but if you answer any question, the main thing is how are you answering, how deep your knowledge is, if i ask a topic and i will let the interviewee to drill down more about that answer. That's all, how you accept that you don't know stuff but if you ask them, tell me the answer, they will think of you as a curious person and maybe impressed by you that you didn't know the answer, but want to know.
For the last heavy application development, the interviewee should ask money to build that😂😂
Kind of makes sense to ask these questions for a technician but for a junior dev it’s way too much.
As a senior architect with 10+ years experience, I am dealing with these things everyday just so a junior dev don’t need to worry about it.
Been to those interviews where an interview becomes an interrogation & humiliation, not a discussion.
Seems like an interview testing what they expect a student to have learned in college as opposed to what they'd expect a junior developer to do on the job. Would this interview someone is the best candidate for a particular job? I guess it largely depends on the job and the training they provide
to play devil's advocate - we don't know the company and what their product and how it relates to understanding networking protocols. Did the job description say that they need knowledge in this domain? - is so then its on the candidate to prepare in advance
can OpenAI replace frontend or backend developers??
No clue haven’t looked into it, I doubt it
Good job babe!!!!
Thanks bub!
I think the interviewer wanted to mess with him because he said he is an "engineer". Being an engineer means you have lots of knowledge/degree and should already know meanwhile anyone can be a developer.
Those 2 first questions look to me like they are supposed to be warmup round, since those are things that are pretty basic, assuming you are a CS student. The rest was just dumb.
It is painful when the interviewer asks these types of questions to put the interviewee putting him/her on the spot and make feel bad if they don't know the answer, I believe that the interviewers should try to encourage the interviewee even if they don't know the answer. I feel bad for the person that had this interview, once the interview finished it must has been painful and demotivating to have experienced that, I wish you more luck on you next interview and that you don't have to go through something like that again.
I’m willing to bet these are from an HR rep with no dev experience.
I think it's a bit ambiguous for the position "full-stack". Like you mention, it's completely useless to ask a web developer who only uses HTML CSS and JavaScript questions like these. But if you're involving backend as the position states, these questions are legit, at least for Junior positions. Because I think that, if you cannot answer the basic questions, it would probably mean you're lacking of something. Those types of questions are not lke you have to study days and nights to know, they just come to you as a nature if you face them enough and it just sticks with you forever. If you apply for a full stack position that involves servers and you cannot tell the difference between TCP and UDP or how the internet works, maybe apply for a frontend position.
Who would want to work for this interviewer. Who says that to people like wtf.
I've went through a bunch of interviews for a mid full stack position, to be fair most of the questions were reasonable, like:
explain SOLID
JOIN vs LEFT JOIN
what is REST
some JS live coding challenges - for example: how would you implement `map` function for JS (hint: put it on prototype)
some basic TS questions - what is type any
implement a CRUD API in Nest.JS
___
^ To me, those assignments seem reasonable in terms of how they relate to your daily work. Questions that I saw on your video are absolute BS IMO, because:
1. Not particularly relevant for job
2. Not to mention, should target mid level developers.
I suppose the subscriber didn't get the job
const { job, employee } = useJob();
probably not,those interview questions were bs anyway
The most irrelevant interview questions I've ever seen :D
Don't bother with such company
that's just some pathetic questions to be asked. Who cares about that really. Unlucky for the guy
1,000% this guy is abusing this channel to answer homework/quiz questions. No developer needs to know this shit in an interview
What guy? These are legit questions a company is asking him during interviews. I’ve know this subscriber for almost 2 years now and I’ve helped him land his first job.
Why wouldn't they just use Google to answer them? I just assume your comment is satire.
Most of those quest are kinda dumb for a dev job.
Agreed
That 8th one should have told him what kind of company it is and walk away, hell in 4 years of uni only questions 1 2 3 were covered rest were coding and algos