Keep at it! We're all working on the first job... until we're working on the second!

Write down questions you get during interviews. Research and Study the answers. Write down the coding challenges. Practice them and research the answers.

You've included the baby stuff. Anyone that has done some internship or self studied can do what you mentioned. It's the interview part where you compete against 100s of Candidates, lot of the times company hire terrible people, terrible programmers, most of the time it's the soft skills that get them the jobs. They can talk the walk but can't really walk it. Some people just know how to talk and they are usually the ones getting either promoted or hired.

@@Ki1ngOfGods I actually made a reply to this comment to give my own input as this comment was just summarizing their opinion. But KZfaq deleted it for some reason and I'm not going to redo it. Too much time to risk KZfaq deleting it again. The basic idea was that you should do these things in a more professional way so that you know how to talk about it. I wouldn't say this is "baby stuff" as most CS grads don't know how to do much of this. Though even if it were "baby stuff" it just so happen that most people struggling to get a job are trying to get entry level "baby stuff" jobs. :P The interview is important, but if you're not doing the stuff mentioned in the video, then you're not ready for an interview.

@@connorskudlarek8598 I know what you mean and I've seen Cs majors totally fail an internship only because they couldn't fetch, or any of what you mentioned. What I'm trying to say is that the job market is so saturated right now it's just hard to get a baby entry level job. And I call it baby because I self studied on my own, have made projects at a full stack level, have done internships, and even contributing to open source. I also went to a boot camp, became a lead, taught others and even though those others were not as great they got the job because of how they present themselves. Bubbly personalities, cheerful happy people, it's something I lack like a lot. I'm technically capable of solving problems, even on Leetcode, my problem is not knowing how to explain technical details. I've tried and no matter what I can't find the right words sometimes so I end up not getting the offer. I got interviewed by Dropbox and PayPal, literally did great on the technical aspect but I basically worked on the problem without talking or mentioning my thought process. I learned that if you need to solve something in front of someone, you need to be able to pause and explain of what's happening in your code. Now when it comes to behavioral questions, yep, I'm dead. I either say the wrong thing, or say something they don't like. The people that I've taught before, I can tell you they are not 100% technically ready but their soft skills are some of of the best I've seen and companies basically hire them because they know they are coachable and have the potential to be great team players, they can train them on the job if need be. Me on the other hand, I stopped applying. I've practiced behavioral questions but end up forgetting or just saying the wrong thing. English is my second language but again, I also know people who sound like the terminator but are very charming and still get the job and trained.

The baby stuff gets you the job. Soft skills are important for sure.

@@CoderFoundry okay man I'm way past the baby stuff. But it's very hard to hire for entry level roles, if you don't have the charms to charm your way then you Def need experience and soft skills, no one really ever talks about that. Some people have it naturally, some people have to practice hard for it.