do you know enough to get HIRED???

do you know enough HTML CSS and JavaScript in order to get your first job as a developer well I'm about to go through exactly how much you need to know and if any like JavaScript libraries are necessary such as react or angular as well this is a super common question that I get all of the time from people just starting out learning to code and even people who have been studying web development for a while so you've been learning web development you've learning HTML CSS JavaScript maybe even some react or angular and you might even have a little bit of confidence at this point but are you ready to start applying for jobs do you know enough this is a really tough position to be in and I remember when I was first thinking about switching careers from a firefighter to a web developer and by the way we all have different walks of life and backgrounds that we come from and it's going to be different for everyone for me personally I actually did quite a bit of freelancing prior to switching careers and to be honest I think I actually prolonged applying for jobs longer than I should have because I was scared I was scared of rejection scared of failure so for me I worked in the e-commerce industry and that's kind of how everything got started for me in web development basically I worked on a bunch of CMS platforms and a CMS platform is just a it's a Content management system it can be pretty broad but I was working on Shopify big Commerce stuff like WordPress and it actually turned out to be a pretty good way for me to break into the tech industry because learning how to use these platforms is of course a lot easier than learning to code you know learning JavaScript or Python and actually being a front-end Under full stack web developer when you're working with a CMS like that you don't necessarily have to write as much code as you would in a typical web developer position and this was a really good spot for me to learn more about HTML and CSS and JavaScript PHP and just kind of how the web Works in general since it was a very entrylevel position it allowed me to get away with not knowing as much but I also got to learn a lot about like hosting and just how certain Technologies and plugins interact with one another okay but how do you even know if you're ready to start applying for jobs you do a quick job search on AED or something like that and for an entry-level web developer and what do you see entry-level web developer must have two years experience a bachelor's degree or equivalent in a computer science related field must be able to model code and test and C++ and Java python JavaScript and have an understanding of SQL or another querying language they want you to have a familiarity with AWS or cloud computing is a plus they may even ask for experience with a container like Docker or kubernetes dude are are you freaking kidding me how in the world is that an entrylevel web developer I think the entry-level requirements are really getting out of control in my opinion some of these companies are putting out senior level expectations for entry level pay but here's the thing you don't have to know everything listed in the job description in order to apply often times companies are just casting a huge net trying to catch whatever they can my rule of thumb and for you know what I follow and what I recommend others follow is if you match half of what they're asking for then just apply there's really nothing to lose and everything to gain even if you completely blow the interview assuming that you even get an interview at all which is rare that's really valuable experience on your end especially if you're new to interviewing for tech jobs you can get a feel of what they're asking you and and how everything works and just to solidify what I just said for my current job right now I actually failed one of the technical interviews and I still got an offer without going too much into it I it was for a front-end developer role and they gave me two technical interviews so they gave me a front-end interview which I did quite well on but then they also gave me a sequel interview it was a remote interview but we were on zoom and it was kind of awkward to say the least about it though and we joke about it now because we both work together but he saw that I was struggling to answer so he asked if I needed any help or Direction I was like yeah I really don't know much SQL at all I understand the basic create table you know insert into select all from Etc he took the time to explain to me how he would answer the questions and then we hopped off the call yeah I got off that Zoom like well I'm not getting that job and to my surprise the manager actually called me about 15 minutes later and this is another guy he said hey I heard how the sequel interview went there was a little bit of a pause and then he said hey don't worry about it you're good I'm good I was like what do you mean I'm good I just I just bombed that thing and he said look this Ro doesn't have a ton of sequel involved plus you didn't pretend to know what you were doing and try and Bs way through the interview you were honest and you told him that you didn't really know much squel and then you asked him to explain it to you he said we really appreciate the fact that you were straight up and honest about it plus since we have a data team that writes most of our queries he I'm not really worried about it man what what a relief I ended up getting a formal offer only a few days later now again this was a front-end role and like I said we have a data team now that handles all of our queries um if I was interviewing for a data team then that would certainly be alarming and I assume the outcome would be way different but since then I've been able to learn more about SQL and get more comfortable writing queries I say all of this to say that you don't have to know everything on the job to apply I mean if they're looking for a c developer and you barely learned JavaScript then maybe you should skip that one but if you feel like your skill level is even remotely close to what they're asking for then just apply I don't really care what anybody says it's good experience and learning to interview and portray your skills in and of itself is a good skill an interview is like a sales call and you need to sell yourself just make sure you know what you're selling it's really hard as an entry-level web developer to know when you're ready to start applying for jobs because well you you just don't have the experience yet you've never worked as a developer you don't know what the expectations are you don't know what the day-to-day is going to look like when you just start learning to code you're watching tutorials um you're following blog articles there's a lot of handholding going on and what do I mean by that you're you're following alongside a video you're following a tutorial um some documentation You're Building like a to-do app something very Elementary and you're getting spoonfed exactly what to do when to do it and where to type it and if you get an error you just rewind the video 30 seconds and you're good of course when you work for a company it's not going to be that way you're going to be the one creating right so what can you do to prepare yourself for that experience the only thing that's going to start to prepare you for that is going to be building things that you don't know how to build and that you can't follow a tutorial to build of course to even get to that level or the fastest way to get to that level in my opinion is to follow a course or tutorial it's the easiest way to learn the basic syntax and how to structure your projects but once you go through a course or two assuming they're well-rounded courses then you're ready to start something on your own I know it may not seem like you're ready but just start and try to build something that aligns with your interest most importantly my advice and what I did was I started building applications that have authentication they have you know a way for a user to sign up and sign in they have a way for user to log out and some sort of database to store uh user information or activity and some kind of dynamic routing building a project that follows those guidelines will really give you a good understanding of how applications work but when are you ready for this step even I'd say once you've built a few landing pages you've learned some JavaScript you understand the Dom you can write functions classes once you get comfortable with doing that then I'd start playing around with some sort of JavaScript libraries like react or angular then add in some sort of database once you have a pretty good understanding of how a library works such as react for example then it's time to start the larger project I'd probably start with a serverless database something like Firebase or superbase I'm currently building a superbase project and I'll probably make a video on it I have a lot of Firebase projects so I'll put a link up here if you want to see one of those projects that I built and you can follow along this will be a lot easier than spinning up a node server and writing a bunch of complex queries at least as a beginner and you can build pretty much whatever ever kind of app you want using those Tex Stacks also don't think that you have to build a whole application from start to finish without like Googling how to do something in order to apply for a job I used to put those types of limitations on myself I thought like once I can build these applications without looking stuff up and without Googling then I'll be ready to start applying for jobs but until then I'm not ready but the truth is there's so much information out there and text Stacks plus they're always changing it'd be impossible to remember everything so rather than memorizing certain things I just tried to understand how things worked so what kind of projects Encompass authentication and databases and routing Etc this could be something like an e-commerce store a real-time chat application or even something a little more simple than that because those things can get pretty complex depending on the level you want to take it to a simple one would be a too app but with all the functionalities so picture this you build a to-do app but a user has to sign up for an account and then sign in in order to to log a to-do that way when I sign in I can't see your to-dos and when you sign in you can't see my to-dos so that covers authentication right there then you could make sure a user canot only create a to-do but you can edit a to-do and delete a to-do and this will be from something like superbase or Firebase to start off with and to make this even more in depth and kind of take it to the next level you could add in some Dynamic routing so what do I mean by this okay so say you log in right so once you log in you can create a to-do along with maybe add a description but you can't see the description until you click on the to-do and it routes you to like my app.com walkthe doog or slash wash the car and you just set the route to whatever the title of the to-do is this is something that's fairly easily done with something like react router if you're building a project in react building an application like this kind of seems funny but it actually gives you a well-rounded understanding of how the front end works and the back end works on serverless databases especially working with react understanding State and they use effect and routes so if you want to see how to build an application like that from start to finish you can even follow along with me I'll put up two videos right here so make sure you click on one of those thanks for watching you guys I'll see you on the next one

Channel: Code Commerce

Views: 2,741

Keywords: web developer, html, css, javascript, react, how do you know when to apply for web developer jobs

Id: D7YTGf7jwjY

Length: 10min 10sec (610 seconds)

Published: Tue Jan 23 2024