How to Get a Job as a Front End Web Developer: The Complete Step-by-Step Guide | Kalob Taulien | Skillshare

Playback Speed

  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x

How to Get a Job as a Front End Web Developer: The Complete Step-by-Step Guide

teacher avatar Kalob Taulien, Web Development Teacher

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Watch this class and thousands more

Get unlimited access to every class
Taught by industry leaders & working professionals
Topics include illustration, design, photography, and more

Lessons in This Class

    • 1.



    • 2.

      Don't Believe Everything You Hear


    • 3.

      The Truth About React And Bootstrap


    • 4.

      The REAL Requirements


    • 5.

      Do You REALLY Need A GitHub Account?


    • 6.

      Do You REALLY Need A Portfolio Website?


    • 7.

      Dont Get Stuck On The Small Things


    • 8.

      How To Find Web Development Jobs


    • 9.

      Remote Jobs Are NOT The Best


    • 10.

      Applying For Your First Web Development Job


    • 11.

      Your First Interview


    • 12.

      Don't Be Nervous


    • 13.

      How To Get Tonnes Of Interviews


    • 14.

      Negotiating Your Salary


    • 15.

      What Companies Are Actually Looking For


    • 16.

      The Hard Part


    • 17.

      After Your First Job Offer


    • 18.

      Not Getting Interviews? (Solution)


    • 19.

      Soft Skills Always Win


    • 20.

      How To Get A Job By Making Friends


    • 21.

      Your First Few Months


    • 22.

      This Entire Course In One Video, Action Items and What to do Next


  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.





About This Class

*** If you're interested in becoming a front end web developer, this course IS for you! ***

This course is the result of a web development job study I did and I ended up getting 12 interviews in 12 weeks. Yes, I'm serious. Of those 12, most of them offered me a job and in the end I was able to pick which company I wanted to work for. 

The goal was to learn what skills companies are actually looking for, and I found those... and much much more. I found a formula for getting interviews quickly. 

I even had The City (that I live in) interview me. Twice! 

This course goes over everything I did, in a simple step-by-step guide. You'll learn:

  • How to find what skills are ACTUALLY in demand in your city
  • How to filter the noise and bad advice in Facebook groups
  • The REAL truth about React and Bootstrap
  • The REAL skills you need to get a job as a front end web developer
  • If you REALLY need a GitHub account and a portfolio website
  • How to NOT get stuck on small things (hint: stop being a perfectionist, it's holding you back)
  • How to find companies that are hiring in your city
  • Why remote jobs are NOT as awesome as people think
  • How to apply for your first job
  • How to manage your first interview
  • How to manage your nervousness in interviews
  • How to get TONNES of interviews. I got 12 interviews in 12 weeks.
  • How to negotiate your salary and how to deal with the dreaded "how much money do you want?" question
  • What companies are REALLY looking for (hint: it's not what you think)
  • Can't get any interviews? There's a lesson on how to climb out of that hole
  • Soft skills vs. technical skills -- which should you focus on?
  • How to get a job by making friends
  • What to do once you land your first web development job

This course is action-orientated. If you are willing to do the work, this course WILL work for you and get you a job soon. 

You will learn about some nasty truths about getting an interview in any industry and how to handle them. Don't get discouraged when somebody doesn't call you back. 

But most importantly, you'll learn the secret to always having a job in web development. Actually, it's not a secret, it's just something nobody openly talks about. 

If you're serious about getting a job as a front end web developer then this course is definitely for you.

The new an improved version of this course can be found below. The new course includes updates for 2019-2020 and focuses on web development (frontend and backend), whereas this course is strictly frontend. 

Meet Your Teacher

Teacher Profile Image

Kalob Taulien

Web Development Teacher


Hi everybody! I'm Kalob Taulien.


Here's the TL;DR (short) version about me:

I have been coding since 1999 and teaching people how to code since 2013 I have over 350,000 web development students world-wide I'm on the Wagtail CMS core development team (Wagtail is Python's #1 most popular website making system) I try my best to answer EVERY question my students have  I love teaching — it's definitely one of my natural talents  Also I love goats! (Great conversation starter with me if we ever get to meet in person)

Below you can find all my Skillshare courses. The categories go from easiest to hardest, except for the Misc. Coding Courses at the very end. 

If you're brand new to coding, start with BEGINNERS WEB DEV.&nb... See full profile

Related Skills

Development More Development
Level: All Levels

Class Ratings

Expectations Met?
  • 0%
  • Yes
  • 0%
  • Somewhat
  • 0%
  • Not really
  • 0%

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.


1. Introduction: All right. Welcome to this course. Now, a few things you need to know before we get started first, what you're going to learn in this course you're going to learn how to get a job is a front and developer. And what that means is you need to know what skills you need to know. You can't apply for a job if you don't know what they're looking for. I'm going to teach you how to find jobs. I'm going to teach you how to multiply your efforts so that you can reach more people. Ah, you can reach more employers without doing any more work. I'm gonna show you a cool little life hack that that worked for me. Very, very well. I'm going to show you how to apply for jobs. I'm going to show you how to get interviews. I'm going to teach you what to do If you don't end up getting an interview like what else can you do? A lot of people just give up. That's not an option for me. And that's not going to be an option for you either. Now, this course is definitely for you. If you want to get into front end Web development. If you were looking for a job as a front and web developer, you're stuck. You can't pay your bills. You want to change careers, maybe get into Web development as a new career or just hate your current job. You want more freedom in your life than yeah, this course is definitely for you. Now, this course is not for you. If you currently love your job. If you love your job wide, why take this course? Um, if you want to make $200,000 a year Or maybe if you want to get hired by Google with no prior experience, guess what this course is not for you. You're going to be left with a broken heart now in the middle. Of course, I'm gonna ask you to leave. Review. Um, the platform that you're learning this on might ask you to leave. Ah, review as well. Um, please do leave a review if you've learned anything new. If you love anything in particular share with people. What? What did you love? Ah, What did you learn? That's that's amazing. Um, and then, yeah, uh, I guess right now we're going to go and get started. 2. Don't Believe Everything You Hear: all rights. Don't believe everything you hear when you enter Facebook groups, People talk about what you need to know what you need to dio where you need to do for all this stuff. But what they're saying you need to do frankly are lies. People make things up that often don't apply to you. It may have worked for them. It may have worked them for one or two jobs, but I got 12 interviews in three months, less than three months and I'm gonna show you how I did it. And the first thing I did was I stopped listening to what everyone on Facebook was saying and I went out and did my own thing. I started from the bottom and I reworked how people get interviews and I did a whole study on it. The first thing you need to do is you need to stop listening to loves echo chambers on Facebook. People say you need to know react. You need to know view. You need to know angular. You need to know Jake weary. You need to know, Uh, all these graph graphing libraries. You don't need to know all that stuff. All you need to know at this point is you need to know what employers are currently looking for. And then you need to go and learn what what they're looking for. That's it. So if you were looking for a job where you know you write, react what you're going about it the wrong way. Um, yeah, it's great if you know, reacts, don't get me wrong. But if you're looking just for react jobs on you're gonna be limited, especially if your city doesn't really care about react or view. Now, if you go and look at employers and you see that you know, 20 out of 50 of them are looking for a J query, 25 out of 50 of them, So 50% of them are looking for view that maybe 35 out of 50 of them are looking for react. Now you have validated the idea that react is something you need to know because 35 or 50 or 70% of employers are looking for react skills. And by react, I mean react Js. So while some of the noise that you hear on Facebook might maybe be true for you, it might not be true for other people like New York, San Francisco, San Diego. Ah, Las Vegas, Houston. Ah, lot of these huge tech hubs. Yeah, they're gonna want react. But if you don't live there which surprise, surprise. Most of the world does not live there. Maybe maybe people just want J query skills. Maybe they just want vanilla. Yes, six skills may be Ah, The most common thing is CSS like you don't know until you actually look, I'm gonna show you how to do all of that. But the first thing you need to do is you need to stop paying attention to what everybody else is saying because it might not apply to you. So we're going to learn how to figure out what companies are looking for and what you need to know from the ground up. We're gonna do it the proper way 3. The Truth About React And Bootstrap: All right, let's talk about react. Angular view, Jake Weary es six and every other JavaScript library and framer you could possibly think of . Here's the truth that most junior developers do not want you to hear, and they're gonna tell you the exact opposite. But the fact is, there, Junior Dev's, they don't know what the market wants. Chancer. They've only ever had one job. And so they're spewing at you. What? Their one little tiny work environment is like and they're they're projecting it across the entire world and places like Facebook. Uh, there these massive echo chambers and so you don't know what people actually want. And so here is the truth behind that. You do not need react. Angular view, Jake Weary. Uh, yes, six. You don't need all of these things. You need some of them. You don't need all of them and you don't know which ones You should learn that here's more . You don't need to know. Bootstrap. You don't need to know foundation. You don't need to know you I kid or any of these other full front and frameworks. Sure it helps, but you don't need to know all of them And here's why. If you spent every day learning all of these frameworks, sure, you'd be incredibly skilled, but it's gonna take you a long time to get a job. And frankly, I don't think anybody wants to spend two or three years practicing JavaScript in these different frameworks. Getting really good. A bootstrap 23 and four or foundation or you I kids two or three. Or you know any of these things. You don't want to spend two or three years trying toe really narrow down and hold all of your skills because you're not making any money at that point. And while you're not making money, guess what? You still have bills. You might have a family you might have pets to take care of. You might have medical bills to take care of. It's just not feasible. And so a lot of these people are saying it takes like a year takes two years. Now it doesn't. It takes a couple of months at most. Now we're talking about react. Angular view. Jake weary. Yes, sixties air, not mandatory. Not all of them are mandatory. Um, they are in demand, so knowing them does make life easier, But don't waste your time learning all of them because you're going to waste your life learning all of them and end up realizing that Oh, okay. I spent all my time learning react and view, Um, and maybe Jake weary. But my employer, my new employer, my new job that I'm working once angular. Oh, no. I spent all the time learning everything else. It's wasted time. Don't do that. Find out what employers are looking for before you start learning something new. So if you're interested in learning react, that's great. But make sure that it's actually in demand in your town or in your city. Otherwise you could learn react. But if no one's gonna hire you for react, guess what? You've wasted a bunch of time in your life. So in summary, you do not need to know. React. Angular view. Jake Weary es six. All these of the libraries you don't need to know. Boot strap foundation. You I kid and all these other frameworks you don't need to know all of them. You just need to know Ah, few off them and I'm going to teach you how to figure out which ones you need to know and which ones are a little more optional 4. The REAL Requirements: when it comes to front and Web development, there are some really requirements now. These are not optional. You have to know these. The 1st 1 is html a 2nd 1 to CSS. Okay, there are only three things that you can ever use. When it comes to creating a website html, you get CSS and JavaScript. Now I would suggest, you know html five semantic, which is it's pretty easy, to be honest. Ah, you learn CSS three. Get a little bit familiar with animations, things like that if you know SAS or less, even better, although those air not technically mandatory. Ah, those air. Just nice little development tools. Um And then on top of that, I would say you need to know basic JavaScript. You need to know Basic Ajay Kori. And now JavaScript and Jake weary go together because pretty much every website usage a query. There was a time when browsers did not really, you know, they didn't agree on a lot of different standards. And Jake Weary was the way that to javascript could be written in one way and work on every browser. And so you see, J query on almost every single website these days, so that is definitely a must. You don't need to be an expert in JavaScript. You do not need to be an expert in Jake were you just need to understand how they work. So you need to understand the core fundamentals of a programming language. If statements, maybe a little bit of try, attach. You know your variables. You know how to manipulate the document object model that Dom's You know how to make a little bit, um, some interactive changes on your website or on your Web page, And that's pretty much all there is. Ah, to being a front and Web development. That's where you get started. So if you take anything away from this video, it's no HTML in HTML five. No, CSS and CSS three and you know some basic JavaScript and how to use a little bit of a query again. You don't need to be a pro with that 3rd 1 That 3rd 1 is completely, you know, I wouldn't know. It's not optional, but you know you don't need to be an expert at that one, so it's kind of like, you know, 2.5 ish and again. With that said, they're only really three components to every website. You've radiation Will, CSS and JavaScript. There are no other languages. There's no other markup that you can use. It's just every browser uses HTML, CSS and JavaScript, and that's all there is. So you don't have to learn PHP Python. No, you don't have to know all this other stuff. It's just the three. And so people think, Oh, well, you need to learn all these other tools and you can learn and PM and you need to learn sass and less and things like that. You know, frankly, you don't. Those are tools are not every Web firm uses? Ah, went from that. I work at uses, ah, sass and lesson and PM and all these other cool tools, but they're not mandatory. I got hired as a front end Web developer, and I didn't use any of those tools I wrote, you know, just plain old boring CSS. Plain old boring JavaScript didn't use Web pack or gulp or grunt or any of that stuff, either. Um, and then I just adapted, cause that's what you do when you get a job. Eso the take away here. Uh, the real requirements for front and Web development is H validation of five CSS CSS three basic JavaScript. Basic Jay Query. If you aren't familiar with these four components again, sort of. Those last two are kind of, you know, little optional sort of it. But if you're not familiar with those, go get from there with those. Now go spend an hour Googling reading documents, reading articles, hop on W three schools or maws or wherever, um, Mozilla developer, network as well. Eyes a fantastic resource on Just brush up on it a little bit again. You don't need to be an expert. You need to know these things because you're going to be using them every single day as a front and Web developer. End of Story s so those are the real requirements again, React is not a requirement. It's a nice toe. Have. It's easy to learn once you know javascript, not a requirement. So, uh, if you're not familiar of those, go get familiar with those and we'll see in the next video 5. Do You REALLY Need A GitHub Account?: do you really need to get help? Account? That's the question, isn't it? Ah, lot of people say yes, you. Absolutely. To get help account. I'm going to tell you that. No, you don't. You don't need one. Because what if you were a developer working at a private company? Like I don't know, Netflix or Facebook or Google? Um and I mean, you can't commit that kind of code to public repository. Just doesn't work that way. Otherwise, you're giving away your whole platform, and so your history would look like nothing. Um, and that's sort of the flaw in the logic. There s ou Tony to get help account. Does it help? Absolutely. Yeah, it does help. So I would say right now if you do not have a get hub account, go ahead and create one. Create one. It's free. Um, if you prefer to get lab use that bit bucket, I don't really care. Get hub is the brand name. So maybe created Get help, account their fill it out. You don't need any projects or anything. You don't need to start contributing to open source projects. That's another myth. People say Oh, employer is always looking for me toe contribute to open source projects. No, no. They're looking to see if you know how to use. Get if, you know, how do you create branches? If you know what, emerge if you know how to commit if you know how to do any of that stuff, Um, again, you don't really need to be pro when it comes to get either. Because teams use get in different ways. Um, one team might love creating a ton of different branches and merging them together and another, another team or another company might want to re base everything. Um, another company might even just want everyone to work off of master somehow. So I mean, there are different opinions on how to use it, but the fact is that you do not need get, you don't need to get help account. Um, but it is definitely gonna help you get a job. So go ahead. Creating count. Now, don't start contributing to open source projects right now. That's a waste your time. You want to focus your efforts on actually getting a job? Um, and frankly, the projects that you put on get or get hub, get Labit bucket. Wherever you go, they could be your own projects. They don't have to be someone else's. They don't have to involve other people. They don't have to do all that stuff. You just need to be able to show your employer that you can use. Get now, if you don't get is. It's basically a version control, Um, and like your project history, but allows teams to work together on different pieces of code and come together in one main area. You can create like this branches for staging so you can have, like, two different sites. And then you can bring the code back into a main site there. Um, so I mean, that's really all it is. It's Go ahead, get your get up account set up created. Make it professional. This is one of those times. It's like Lincoln make a professional. Don't use dumb pictures or anything like that. You know, you want to get a job, act like you want to get a job. Um, so there you have it. So your homework for this lesson is to create a get help account. If you already have, get have account, you don't have to do anything, and we'll see in the next video 6. Do You REALLY Need A Portfolio Website?: Do you really need a portfolio website? You know what a lot of people say? Yes, a lot of people say no. What is the honest answer behind that? The honest answer is no, you don't need one. Mr Dick is off. You don't need a portfolio website because it doesn't often show some of your greatest work . Now, if you're brand new to Web development, it's definitely gonna help. When you apply for jobs, they're gonna want to see what you haven't have not working. If you don't have a get hub account, you might want a portfolio website. If you don't have a website that basically or even just a single Web page that shows off the other projects that you have worked on other website you sue, you work on, you have literally no work history behind you. You're going to want to go and create a couple websites. They don't have to be big. They can just be landing pages. Remember, your front end Web developer doesn't need to have a database that doesn't need to stream videos or anything like that. It just needs to be html. CSS and JavaScript need to look and act nice. That's it. So if you don't have a portfolio website, that's totally fine. Just make sure that you're able to provide some sort of code example or maybe screenshots of some of your projects. Or maybe just be able to prove that you can write some of the code that is actually behind certain projects. Common practice when you go and finally get an interview is employers are going to want to do this thing called white boarding, where they give you a problem and you actually write out the code on a white board and they want to assess? How do you figure that out Now, there's not really any right or wrong answer. They just want to see Oak and this person actually figure it out Or, um, you know, like, how how do they work with problems that are difficult? So we're gonna talk about that a little bit later, but for this lessons, you need a portfolio website. Technically, no, but it doesn't hurt to have won. It definitely increases your chances of getting a job if you do have one. Furthermore, you don't necessarily need a portfolio website. If you have a get help account, you can put all your projects on, get hub on. And if your employer can't read code from get hub, um, or can't clone one of your projects from get up. You know, chances are they're not very advanced anyways, and they probably don't really care too much about the actual looking at your portfolio. And they're more interested in actually figuring out what you can do for them to help them grow there in a smaller stage of business development. And so they're just looking for people. But at this point in time, it's probably a good idea to have a portfolio website again not required, but it does increase your chances. 7. Dont Get Stuck On The Small Things: don't get stuck on the small things. This is very important. A lot of people become perfectionists when they start coding and they get into, Ah, new industry or they wanna just become Web developers. They're looking for a job. People start to become perfectionists, and that's going to slow you down. It's unnecessary. You don't need to be perfect at anything. Now. Don't wait to your portfolio. Website is perfect to apply for a job. Apply now. Don't wait to your get up. Account is absolutely perfect. Has 1000 commits and you're contributing to AH 100 different open source projects. Don't do that. Apply now. Don't try to learn everything. Find out what employers want most. Learned what they want. Learned that first. Eso. If an employer wants you to learn or most of your employees and you say, let's say like 60% of them want you to learn view. Learn view. That's the most in demand in your city. Go spend an hour learning whatever it is. You don't need to spend a lot of time. Go and apply now, even if you don't have the skill. If you can get the skill quickly. If you can learn view rather quickly. Go and apply now. And the reason that I'm saying that again is because you don't need to know everything underneath the sun. You just don't. And getting a job in Web development is not going to be one of those things where you apply . And the next day they're calling you in. The next day you have a job. It's knotted two day turnaround. In fact, a lot of places are several weeks, if not months. They want to make sure that you are a good person or higher, because hiring a Web developer who doesn't turn out is very, very expensive. If you don't turn out to be an asset to their company within three months, I guess what they wasted three months and you wasted three months. Nobody wants that. So they want to hire slow and make sure they find the right people. You just need to make sure that you're the right person, but in that time frame that three months, it might be three months. It might be three weeks. Either way. It's not going to be two days. You're going to want to apply for jobs and start start learning. So if you apply for 10 jobs that want reacting, you don't know react and you apply for 15 jobs that want viewer angular and you don't know viewer angular will go ahead and start learning those things as soon as you apply. You know what you have to learn. And again, chances are you're probably going to apply for junior or intermediate positions. You don't need to be an expert of these things. They are expecting you to not know everything. They're expecting you, Teoh. When you come in, you are going to learn a bunch of new stuff, and you're going to apply that at their company. The lesson here is don't get stuck on the small things. Don't wait until everything is a pixel. Perfect. Don't, uh, don't waste your time, okay? Employers are not looking for pixel perfect websites. They're looking to see what you can do and what you can do for them. So don't get stuck on the small things 8. How To Find Web Development Jobs: How do you find a Web development job in your city? This is the golden question. This is why you're taking this course before we do that. Let's start at the very beginning, okay? You want to look in your city or in nearby cities within driving distance. This is not a course to teach you how to get a remote job overseas or how to get a job in a bigger city without moving away from where you live. This is a course that teaches you how to get a job in your city. Now I'm recording us in Edmonton, Alberta, Canada, and it's not a big city. There's 7 800,000 people in the city, um, 1.11 point two million in the metro area. It's not very big. There's not a lot of Web development jobs that said, I mean, the economy here is not fantastic for Web development, And yet I was still able to yet 12 interviews, not just people who are interested. I got 12 interviews. I went to 12 interviews in less than three months, and again, this course is about finding a Web development job, a front and Web development job in your city. So the first thing you want to do is you want to look in commonplaces Craigslist. If you're in United States K g a fear on Canadian soil, really any place that you know, people are selling things. If people are selling things, chances are their job postings there. So, uh, look on forums. Look on really anywhere. That someone's gonna sell something. Ah, and you'll find job listings. The next step is Google Web development. And then just insert your city's name and you're you're gonna have to look at every single website of the every single company. You might only have five. You might have 50. Look at every single one. You have nothing better to do right now. Then toe. Look at every single one. See if they're looking for any developers, See if they're blawg has any mention of looking for developers. Some companies will post job postings in their blawg instead of posting it in like a were hiring section. Look for a career section. Websites or different companies are different, but essentially a job posting is a job posting. So you're gonna want to look at these these different places now 1/3 option and a lot of people don't like this, but this is this is a great way to leverage people in your network is to ask your friends and to ask your family. The reason that I'm saying that is because just you looking for a job is just one person. But if you have two or three friends that are, you know, sort of just keeping an eye out for Web development jobs or maybe they heard something you don't know what other people do know. It doesn't hurt that house, right? There is no shame in asking your friends and family for a little bit of help here. You want to make a positive change in your life, Ask people to help make that positive change in your life. I mean, simple is that I mean, that's what friends and family are. Essentially four. There, there, there, as your support network. Now you should be able to find tons and tons of jobs. Uh, if you can't find a bunch of jobs, if you look, go and look at a bunch of different Web development firm websites and they just aren't hiring and guess what? Save their contact details anyways? Because they might be hiring in the next few months. They might be looking to hire someone the next few months. Maybe in the next week. We don't know. We don't know. So keep that option available. Always keep that option available. Now what? I want you to dio this. This lesson has a little bit more homework than all the other ones. But I want you to create a spreadsheet. I don't care if it's excel or if it's a Google spreadsheet. I don't care how you do it. Create a spreadsheet, and then I want you to list every single job posting you have found. Okay? And you should have a list of at least 20 at least 20. Even if you find job postings that you don't think you're gonna get. Maybe they're hiring an intermediate developer. And you still think you're junior? Guess what. Keep that like, keep it. It doesn't hurt to apply. Anyways, we're going to apply a little bit later. You don't have to do it now. Just keep that list. We're going toe work through that list little bit later, but the first thing you need to do is come up with a list of people who are looking for front end Web developers. Secondly, create another list. It could just be another sheet in your spreadsheet for companies that are not currently hiring but have AH, contact form or contact email or something, because you can approach them in a different way and just say, Hey, look, I've got some skill. If you're looking to hire a developer, just, you know, keep me in mind type thing. Eso create those two lists basically, while you're going through that list. Um, while you're seeing all these different websites, all these different companies learn what is most relevant. We're gonna talk about this a little bit more in a future lesson, but learn what's most relevant. So if you see that most job postings are looking for, um, maybe they're just looking for Jake, where they're looking for sex. Maybe, maybe, um, out of the 20 that you find maybe 16 of them are actually looking for react. Maybe you live in one of these cities where react is it is the go to JavaScript framework, you know, just keep noted that you can even put that in your spreadsheet, Which is why I told you to make a spreadsheet and not just duck because you can move over just a couple columns and you can say, Oh, they're looking for a reactor looking for react. You know, they're looking for angular and just check it off. Research is your best friend here, and this is the first step to finding out what people in your city really, really want. It doesn't matter if 100% of the people in your city really love react if nobody is hiring for react. Well, guess what again? You're wasting your time, so just make sure that you're logging not only the u. R l is, but maybe some contact details and what skills they're looking for. Maybe they're looking for a reactivation of five CSS and maybe some skills that you don't have maybe sass less. Maybe some back end skills. Maybe they're looking for a full stack developer. And, you know, maybe they're looking for a little bit of PHP and my SQL. Or maybe some noted mongo. Whatever it is, log all that information away, and we can filter through that a little bit later. So go ahead, get started on that list and we'll see the next video 9. Remote Jobs Are NOT The Best: why remote jobs are not the best. Okay, A lot of people think remote jobs are the best. They say, Oh, I want all the freedom in my life. Actually. Don't you think you do? You don't The freedom Don't get me wrong. The freedom is really nice. I've worked remote jobs. I've worked from home. I've done all this stuff, Um, and it's nice for a little bit, but there are a few drawbacks. Okay, First of all, it's lonely. Okay, you're working by yourself. You don't see other people humans by default where social creatures. We need to see other humans. And you see less of them when you work by yourself. Number two is it's quiet. Yes, quite as nice is great for concentration. Again, we're social creatures. We want to be around other people, even if it's just the hum and buzz off going to a Starbucks, We want a little bit of an always a little bit of a distraction. Lives, but not too much, not too much. But the third reason and the main reason why I do not like working remotely. And this is the reason that I think you should adopt immediately is because you will not be learning rapidly anymore. When you get a job at a company, your skills they go from here to here within a couple months like this could have taken you a year to get here. And this massive leap here might only take you a month or two months like not very long. You're you're never going to learn as much as you will at an actual job Now. With that said, you're not going to learn as much from YouTube videos or courses or articles. Doesn't matter how much you read online. You will never learn as much as you will in an actual job. And that is why I think working remotely is a bad idea. No, Sometimes you don't have a choice. Maybe life through you. Ah, bad card. And you've got health issues. Or or maybe you just had Ah, child. And you literally cannot go to an office because of whatever reasons, family reasons. Maybe maybe you just can't get to in office. Maybe you can drive. There's no bus routes and you have to work remotely. In those cases, it's fine. You just have to make sure that when you are working remotely that you are. You are learning as much as you possibly can every day. So you end your day thinking Wow. I learned a lot today. Even if it's just you just by yourself, you go. Wow. I learned a lot of stuff that I didn't I didn't know Now that versus working in an actual office with people across from you where you could just lean over and say, Hey, buddy, I don't really understand this. Can you help me? You know that seven minutes with another person could be the difference between seven minutes and learning in your skill or learning a new programming fundamental or a concept versus spending three or four hours trying to learn it on your own, you know? So now you've got seven minutes, three or four hours, like which one would you rather take? Would you rather get paid 100 bucks for seven minutes, or would you rather get paid 100 bucks for three hours? I mean, it's it's the same concept here. You want to learn as fast as you possibly can. So that's why I think remote jobs air. Not fantastic. But again, you know this opinion is not for everybody. But I think regardless of who you are, you should be focusing on learning as fast as you possibly can. 100% always learn as fast as you possibly can. 10. Applying For Your First Web Development Job: applying for your first Web development job. First thing I want to do is you want to search your city for common job requirements Now, in a previous lesson, we had done that already. So go through that list. You should have a neck self spreadsheet or Google spreadsheet with up to 20 job listings at least 20 if there are more, put more in there if you confined 55 50 and then go through that list and figure out what the most common job requirements are. So now we're working this list. We've got this Excel sheet and we've got 20 or 50 employers on there and we're looking to see Do they want react? Do they want to? Angular. Do we want? Yes. Six. Do they want Jake Weary? Chances are, they do want bakery in a little bit of vanilla JavaScript. But do they want more? Are they looking for more? Maybe you found a Web firm that's looking for someone who only wants Pierre JavaScript like No, library is nothing like that is just straight. Yes, six. Figure out what that is. Okay, that's that's the next step. You have to figure out what they want. So now I'm gonna create a hypothetical sort of situation here because I don't know where you live. So saying your city there's a, uh, 50 job postings for front end web developer. 40 of them want react. 35 of them want of you, Um, 30 of them. Who wants angular? 20 of them wants J query on 10 of them. Just want plain vanilla JavaScript. Now, those numbers don't add up because there are overlapping requirements. May be one place once Jake weary on and react. Maybe another one wants. Just react and view. Maybe one. Just one's view and angular. Maybe one just want angular. You know, you don't know what you don't know until we start looking through some of this data. So you find your top three. So you know, if it's reactive, you and angular, those are the top three super reactive. You and angular, uh, simply start learning those, um, but there's sort of a little bit of catch to that. So, uh, if you don't know, react and it's the number one in demand framework in your city, Well, guess what. It's time to go and learn a little bit a little bit about react, but before you do that, apply for the job. Apply anyways, even if your resume or your C V is very, very bare bones right now. Apply anyways. Let them know that you're a junior Devin this area and you know you might not get the drug . You might not get an interview, and that's fine, but it doesn't hurt to apply now after you apply. So find your you know, 35 or 40 or 45. Whatever your company's in your list that have a requirement for react, apply for all of them. Then spend an hour or two today learning about react So you're applying first and then you're learning. I know that sounds completely backwards, because why would you apply for a job when you don't actually know the skills that are required? Well, guess what? Web development is one of things where you can learn, react very, very, very quickly If you have a company that calls you up and says, Yeah, Caleb, I would like to pay you, you know, $60,000 or 70 or 80 or $90,000 to be a front end Web developer, but you need to know, react to, you know, react. You know, as Richard Branson says, If you don't know if you don't know how to do something, say yes and learn how to do it. So that's what we're doing. We're taking a billionaire's advice and we're actually applying that. Apply today. Do not wait because jobs take time. And frankly, I mean, if you apply for 50 jobs just for react today, chances are you're not gonna get any phone calls or any emails back for at least a week. Um, and then you've got to book an interview time, and you've got to sort of get to know them. You've got to get the culture they've got to know. You have to get to know you. There's this whole waiting period in that waiting period, you might as well learn, react. You might as well say Yeah, I know reacts and and I come, I can learn it. Um, if you if you find out that you don't like react when someone gives you a job offering four react, you know, just turn it down. If you would prefer angular, you can turn it down. But the fact is you actually got someone to call you, and that's the important bit here. Now, I would say, because this course is all about getting your first job that you don't turn it down. Maybe your first few weeks could be really, really hard. And that's fine, because you're going to learn a lot again. You're never going to learn as much as you possibly can when you when you start your first job. And the last note for this one is, don't wait until you're a pro Yuri Pro. If you wait until you're a pro, you're you're never, ever going to apply for a job. You'll never gain the expertise required if you can't land the job. If you can't land the job, you can't get the expertise. So what do you do? You start at the bottom. You start as a junior intermediate, and you work your way up. You let them pay you toe, learn new things, and now all of sudden you've got income coming in and you have skills that are being built at the same time. Now, a lot of your stresses have been, you know, washed away just because you can pay some of your bills now. Ah, it might not be a lot. Your first shot might not pay a lot, and that's totally fine. But the fact is, you're making some money and you're continuing to educate yourself. Now, if there's one thing you take away from this course it does, that is, you want to be paid toe learn stuff. That's it. If you can get paid to learn something that you're interested in, how does life get any better? Really Think about it. If if you wanted to learn, ah, more boot space. So let's say you wanted to be an astronaut and NASA came up to you and said, Yeah, we want you to be an astronaut. I mean, doesn't work that way. But if it did, why wouldn't you say yes, they're gonna pay you to be an astronaut. It's the same thing with coding. Someone's gonna pay you to learn how toe code or, uh pay you to learn how to code reactor view or angular anything like that. Guess what? Take that opportunity, take it and figure it out along the way. It's a little scarier this way. I know it is, But guess what nobody else knows. It's just you. Um, is this an ethical approach? I would say absolutely. Yeah, because between the time that you get the job, interview our callback or even between the time you apply and the time that you actually get the job, this could be, You know, that timeline could be three months. And in that three months, you could become very, very, very proficient and reactor viewer angular J Career SX or anything. Three months is a long time to learn something. And if you know, someone might be interested in years, if the company is vetting you for a position, you're going to put a lot more emphasis behind it in your life. So go ahead and apply now. So go through that list. Apply for all those different jobs. Um, and don't wait until you're a pro, apply and then figure it out. Say yes to something that you don't know how to do and figure it out along the way. That is the best advice that Richard Branson has ever given Probably anyone, and that guy's giving out a lot of great advice. So go ahead, get started with that 11. Your First Interview: Okay, this point, you probably don't have any interviews lined up, but theoretically, you would. So if this course was gonna take you three or four weeks, you would probably have an interview lined up by now. So in the event that you do have an interview, what do you do? Well, I have actually seen this before. This is a terrible, terrible mistake. Just because you get an interview does not mean you stopped looking for jobs. Does not mean you stop a playing. Just because you have an interview does not mean you're going to get the job. Even if you've got a great feeling about it. Don't Don't trust your feelings. Your feelings are wrong. Okay? So keep applying for jobs. Keep keep accepting interviews, Keep looking for jobs. Keep asking people to look for jobs for you. Keep doing all this stuff. It's very, very important. While you are waiting to maybe be approved for a job after your interview that you keep a plane because you don't know it's not a guarantee thing. And because it's not a guarantee thing, you can't rely on it, so don't do that. Next thing is when you get an interview. Be prepared for some pretty tough questions, questions that nobody else has thought to ever ask you. Um, answer them honestly. Uh, feel free to take a little bit. Time to answer some questions you don't have to be like super witty. You don't have to be like Robin Williams, Witty. You know, you can just answer them the way you normally would, and that's completely fine. They're looking for something like that. They're hiring ah, person, not a robot. And so, with these questions, you can You're going to face some really, really hard won, some that you might not even be able to solve on the spot. And that's fine. If you don't know how. Just put an emphasis on Look, I don't know how, but I'm going to figure this out. I'm going to figure out how I can do this, and again, that's that's totally okay. If you don't know how to answer a question, you don't know how to answer a question. If it's a technical, a technical question that you don't know, guess what. A quick little Google can solve that problem for you, but always put an emphasis on wanting toe learn and how you can solve problems, though that's what Web development companies are looking for. They want to take you from here to here so that you can be a bigger, more reliable asset to their company. But they also want you to be able to solve problems for them, because self problems for a Web development company means money and money means they can pay you and other employees, and that's very important to them. So that's what you focus on when you get an interview, you focus on a being honest. Feel free to take your time. If you don't know how to answer a question, you don't know how to answer a question. That's fine. I don't feel like it's the end of the world. Don't walk away feeling bad about yourself for anything. Those hard questions are designed to be hard, Um, and also don't expect them to be hard. I've gone to several interviews where they were a Parise. It was just, like done, You know, there was like 15 minutes in 15 minutes out. Ah, little talking on the side, usually about something very your things, like Space X or Tesla or something and then Ah, yeah, I mean, that's it. Easy. So some some people ask you easy questions. Some people will ask you harder questions, and I mean, that's just life. You don't know where you're going to get, so you just walk in there with an optimistic attitude and you do the best that you can dio . And if it's not meant to be, guess what it's not meant to be and you'll just move onto the next one because you have a list of employers Now you know who we're looking for jobs, and you can just go on to the next one so keep on keeping on. 12. Don't Be Nervous: why you shouldn't be nervous about a Web development interview. So this lesson comes with a harder to swallow pill. Some people may not like this, but it is Thea salute truth, and this is no different for me and so different for anybody else that I know. And I know some very smart people, but just a general life. Fact is, you were probably not the smartest person that they're interviewing. As hard as that might sound. That's actually OK because a lot of places are not looking for the smartest person. They're looking for smart people, Yes, and that's if you're taking this course. That's obviously you. When you had an interview, they're not just looking for technical skills. They're looking for soft skills now. Another thing is, you're probably not looking to make a $1,000,000. Your focus should be just finding a place where you can learn a lot in a very short amount of time and you can get paid to do it. That's sort of the ideal situation, but, you know, here's your just. The truth is you shouldn't be nervous because you're not going for a $1,000,000 job. You're not going to be the smartest person in the room. In fact, you were trying to get a job because you are not the smartest person in the room because you want to go and learn things. And that is actually a good thing. And, yeah, you're not gonna make a $1,000,000 But that's okay. You're probably not gonna make, like, 100,000 either. You probably start off it. Ah, junior wage. And that's okay, because you have to start somewhere once you get your foot in the door, Then it's nowhere, but up and again. That's a good thing. The more you learn, the more you earn. And that's a lesson that we learned from Ah Warren Buffett, another billionaire. 13. How To Get Tonnes Of Interviews: how to get tons of interviews now this is what people are really interested in. I must tell you straight up my secrets of how I got tons of interviews. To me, it's not really a secret, but I guess it's not. It's not like a common practice, so the first thing I did was I applied for every job. I couldn't find anything that said Front end or back in because I'm a full stack developer . But for you, anything that says front end developer apply for it. If someone's looking for a reacts developer, but you write viewer angular apply anyways, not that much of a jump from view to react. There are some considerable differences, but it's really not that hard to learn, not even, Ah, it's not even like a scarce resource. I mean, you can find tutorials and classes and courses all over the Internet that'll teach you the stuff in like a date. The next thing is, you need to know that lots of companies hire people over skill. What I mean by is they're looking for soft skills. Technical skills can be taught, but personal skills that's harder to teach someone they have to be good people on their own , and then you can teach them the technical aspect of a job. It's much easier for a company to do that. Another tip for getting lots of interviews there, even just finding a lot of jobs is to ask your friends or family to keep an eye out for job postings in different positions. And here's why. You know there probably won't be able to help you too much unless you have friends or family that already in Web development. But here's the thing is the more eyes that are looking for a job posting for you, Lord, our position as a Web developer. The more people that are looking for you, the better your chances. That's that. That's just the truth. And here's the golden rule. Okay, you need to multiply your efforts. If you are able to apply for 10 jobs a day that you know, we're looking for whatever skills that you have, you need to multiply that effort. How can you find someone else to do the exact same job for you? Well, have you ever considered using a recruitment agency? A lot of people say No, I don't want to use a recruitment agency, but at this point you're looking for a job that's going to pay you so you can learn. And then if you don't like that job, you can go somewhere else. There's nothing wrong with that. If they don't treat you well, don't stick around. I mean, it's pretty simple. So what I ended up doing to get 12 interviews in in about 12 weeks was I used a recruitment agency. Now the recruitment agency actually only landed me and was like four, maybe five of them, so it wasn't even half, but that boosted my number from 12 from 7 to 12. That's pretty good. Now if I said if I that I got seven interviews in three months versus 12 interviews in three months or ah, one interview a week, it's a lot less impressive, right, And that's because I used a recruitment agency. Now I didn't accept any of the jobs from the recruitment agency, and to me that's totally acceptable. I went to go and see how the Crewmen agency did something really cool. It got my foot in the door with some pretty big companies here and admit him and I even got two interviews with the city of Edmonton who were looking for developers at the time. Just a couple developers. And, uh I mean, that's pretty good. Like it's hard to get that kind of interview from, you know, just your own efforts. But someone else from a recruitment agents, you might be able to get you in with one of the big local companies that's reached out to them and said, Hey, look, can you do some vetting for us? Or maybe the city that you're working is like, Hey, maybe in one of these recruitment agencies, you know, do some vetting for us and, yeah, absolutely what they did and they got me a bunch of interviews, and so I don't sound super ecstatic about that or anything, but it was a super, super cool experience toe. Have these big companies bring me in interview me and offer me jobs now? Ultimately, I ended up turning down, Um, all of them out of the 12 of the ones that actually offered me a job there was, I think it was like nine or 10 of them actually offered me a job on, and I turned all of them down. Um, because they weren't the type of culture I'm looking for. I like the startup culture where you know, you can hold her across the room and you can get ah, senior death to help you. Or you can help one of the junior guys. I like that kind of culture, and they weren't able to provide that for me. Um, the company that I ended up going with actually pays a lot less, but I am significantly happier there. And that sort of leads me into the next topic, which will get into, um, and that's about chasing money. Do you want money or do you want happiness? Um, and there is the right answer to that. Doesn't matter who you are on the last sort of point for this video is don't be the person who's too good for a job. You know, take whatever you can get. If it's if you your first Web development job, take anything because you're going to learn a lot. Even if the job stinks, you're going toe, learn a lot. And while you're getting paid, you can continue to look for another job, and this way you don't have the stress of bills, you're still learning a little bit. You know, life is starting to progress, though, but you might not be the super happy guy in the office or a super happy woman in the office at the time. But guess one again. You're making progress. You're getting paid. You're paying your bills, your learning a lot. And now you have that next little step to go to the next bigger company or to the next better company. Just make sure you learn something new from every job in your life. The big tip here is use a recruitment agency. Even if you don't like him, use him to get interviews. And you know what? Ah, there are ways around it. If if you don't like recruitment agencies and they keep setting you up with bad companies or companies that have terrible rip reputations, you know, maybe choose a different recruitment agencies, there's tons of them out there. They get paid typically when they find you a job. So they're going to look pretty hard to get you a job on again that gets your foot through the door. So I mean, that got me less than half of my interviews, but it got me a handful on him, and it got me quite a few interviews with some pretty interesting and hire people that I probably wouldn't have had the chance to meet. Even though I didn't take any of the opportunities, it was still really cool to meet and to connect with these people. And I still keep in contact with several of these people. So in the event that I do need a job in the future, Aiken personally reach out to them now without a recruitment agency. And I can say, Hey, you looking for people? And I think so, Yeah, I know, you know. I mean, we can cross that bridge when we get there, but now I have that opportunity set up for so, uh, definitely consider using a recruitment agency. 14. Negotiating Your Salary: How much money should you be asking for? Well, that really depends on your skill on the value that you can provide to your new company, how much money you can make the new company, your local, your local economy. There just too many variables for me to actually give you a number. I wish I could just give you a number and say, Yeah, you should be asking for $70,000 Or here's the national standard for whatever country you're living in and this is what you should be asking for. But frankly, it's different for everybody. And so it's hard for me to give you just a straight answer on this one. But I can't say a couple of other things. First of all, don't chase the money. They're going to be companies that will pay you more. And they will. There's a reason they pay you more. Um, they make you wait. You don't learn a lot, and maybe they treat you poorly. They don't give you extra benefits. Um, sometimes chasing the money seems nice because you have bills or you have dead or you help health problems or or whatever it is. I mean, everyone needs money and a little bit more is always nice. But at the end of the day, what development isn't about making money? And I know you might be thinking Well, Caleb, isn't that the point of this course like to start making some money toe, you know, actually get a job. And while it's a yeah, absolutely. It's it's good to make money and t earn a living, but at the same time, don't just chase the money, have somewhere gonna offer you $80,000 But it's not gonna pay any of your benefits. People there generally miserable. Um, you don't think you're gonna learn too much? That's probably not the place for you. Now, if someone else is gonna pay you, let's say 65,000. So $15,000 Last that's that's more than $1000 less every month is what they'll be paying you. You might be thinking, Whoa, that's hard to justify. But if they're going to give you great benefits, if they're gonna treat you right, if there's less pressure, if you're gonna dio, if they're going to treat you like a great employee, then you were going to be willing to work a little harder, which is totally fine. And, yeah, you'll be making a little bit less. But at the end of the day, you're going to be much happier. And cultures, company cultures that sort of do that. They end up paying a little bit less. But you know, they make up for it with great people with great companionship, with little parties. Um, that was there, typically happier places to work. And frankly, I mean, if you can't get by on, like $65,000 a year, I mean, you got it cut back on your spending. That's that's not their problem. That's more of a you problem again. A little tough love there, I suppose. Um, but yeah, so don't chase the money. It's better to be paid less and learn more than it is to learn nothing and to be paid more . And the reason for that is because you want to future proof your job, which essentially means the more you'll learn in the higher chance or the higher success rate you will have When you eventually move on to the next job, you'll it'll be easier for you to get a new job. It'll be easier for you to apply for new jobs. It'll be easier for you to go to another company and demand more money because you can actually do that at that point. Now in and in for you, a lot of companies will say, Well, how much are you looking to get paid? And this is a tough question, because if you say too low, they might think that you're undervaluing yourself or you don't actually know anything you say to highly go. We don't want to pay this guy or this woman too much. Um, but here's what I typically tell people, this is what has worked for me. A lot is I don't mention any money until we get close to the job. Until they actually say, Look, this this job is yours. We want you on board. How much are you looking toe to make? Um, And even at that point, I mean, if if the job isn't like, 100% secured yet, what I'll say is something along the lines of, um, you know, I just really want to get to know you and the company and some of the people in there Ah, and I want to be able to figure out where I can fit in and and how I can really help whatever the company's name is, grow and become more efficient. And I think once we figured that, oh, too, then we can talk a little bit more about economics. Um, so that's really good out for that uncomfortable conversation. But I mean, if you know your number, stick with your number. If you have a ton of interviews, you can stick with your number. I would say, you know, anywhere typically in North America anyways, anywhere between about 50 and $70,000 is pretty good. Um, but I mean, if you're in Europe, that can change. If you're in India, it's definitely different. If you're in China, it could be completely different. Even depending on your city that you're into North America, I mean, that could be completely different. So I mean, whatever your number is, you can stick to your guns. Just make sure that you know that if you say a number that's too low, you might be devaluing yourself. But if you say number too high, you might be valuing yourself, obviously too high and the company is gonna get a little bit weary about that. So generally what I've done is, um, all sort of pussyfoot around the conversation a little bit. Um, and I will actually make sure that I am a good fit for that company. The company is a good fit for me now, when it is actually time to start talking about salary, I usually ask them, like what? You guys usually start a developer office. So if I was applying for a senior developer position, or even like you might be in a junior junior developer position, I might say, What do you guys usually pay your Junior Dev's? And they say, Oh, you know, somewhere in the ballpark of 45 or $50,000 and then you know, you can put your number somewhere in there. Now that number might be lower than what you're expecting. But if you currently don't have any income, I mean, it's basically if you said yes to a lower number, as long as you can survive on that, you can pay your bills. Then essentially, it's like going to college, but getting paid. You don't have to pay anyone. They're paying you to learn. And so that's sort of the opportunity here is, even if you're making less money, as long as you're making enough to get by your actually doing a great job and then all you do once you get in as you focus all your attention on learning as much as you can and then when it comes to your probation or your quarterly or bi annual or annual review, then you can get a raise. They will probably just give you a raise on their own to be totally honest with you. I've done this with numerous companies and numerous industries, not just Web development. And yeah, it works. It works very, very well. Um, so how much money should you ask for? Well, you gotta feel that one out. But don't be scared to to ask the company, like how much usually pay someone in this position and you know, if if they don't really tell you a number, I mean, you can just throw it out there. I mean, really, it's just guessing at that at that point in time. And yeah, that's what you do. That's how much you should ask for an unknown amount. I know. Not helpful. Right. But that's how life is. Eso Yeah. There you go. 15. What Companies Are Actually Looking For: all right in this video, I'm gonna talk about something that a lot of people don't really pay attention to. But it's sort of the key ingredient to success getting a job as a front end developer, and that is what our companies actually looking for. People make the mistake of thinking that a company is looking for a reactive Elber or a view developer or an angular developer or some particular skill, when in fact that's actually the wrong way to look at it. We should be looking at it from a company perspective. Now, as someone who has started companies who started projects was hired. People I know a little bit about what a company is looking for, and I can tell you this with absolute certainty that it's not just skill. It's not just technical skill. We're looking for soft skills, someone who can come in, who is willing to teach other people in our group or ah, other colleagues. I should say we're looking for more than just technical skill, and it actually even goes beyond culture or soft skills because at the end of the day, a company does not breathe oxygen like you or me a company breathes money, and I don't mean that to sound greedy or anything, cause it's not. It's just the nature of how the market works. It's It's all based on money, right? And so companies don't care if you've made you know 100 or 1000 or 10,000 mediocre applications, they just don't care. That's not in their interest. I mean, it might be cool on. Some companies might think that's impressive, but I mean, if you made 10,000 mediocre gaps, I mean, you're pumping out like dozens a day like it's That's no good. They're not interested in that, Um, because I means lower quality. But if you're if you've only ever made one I mean, if it's taking you five years to make one, well, why is that? Are you Are you slow or you are perfectionist? Don't be perfectionist. Companies don't care about perfection. They want to get a product through the door, or, in this case, they want to get a website or an application through the door. You can fix bugs after you launch something, but you have to launch something, and that's the key. Now company is only care if you can really help them with their bottom line. And what I mean by that is, Ah that you need to make sure that you can make them money. And now don't be offended. This is basically just economics. If you can help them make money, then you're considered valuable. No company is going to hire any employees that cost them $10,000 a month. When you're only helping the company make, like 5000 like they're losing $5000 a month off of that and that's no good. So if you are interested and getting paid, for example, $5000 a month as your salary, then you have to make sure that you were worth more than $5000 a month. Now it's a little bit hard to justify being paid more than that, especially if you come from like a freelancing background, cause it's like $5000. I mean, that's that's a lot as a freelancer as, ah, independent contract, but they have a lot more weight and power behind them because they're a full Web development firm. They've got sales people typically, or they got someone who can actually do the sales process and all this other stuff that you don't have to do now. The key is, if you were going to ask for $5000 again, you've got to make sure that you are worth more than that. And now, skipping back to what I said at the very beginning, companies are actually looking for decent people. They're looking for good human beings, not just skilled people, but they're looking for nice, helpful people who were willing to learn. And I mean, you've got to be able to admit that you're wrong on when you're wrong. You've got to be able to put your ego aside a little bit and ask for help. Asked for correction, Sometimes it sucks. And walking like this happens to me whenever it does happen to me. I mean, yeah, I mean, I've gotten ego just like everyone else, and I put it aside and I swallow my pride and I say so and so, Yeah, I think you're right. Can you show me your way? Sometimes I like their way. Sometimes they don't like the way, but either way I'm learning something and I'm learning something about someone else. I'm learning their perspective, which is also incredibly valuable to a company. So what? A company is looking for us. Technical skill, soft skill. They want to make sure that you can actually help them make money. Because if they can't make money off of you, well, guess what? They can't hire you or they can. But then they're gonna have to fire other people or they're gonna have to fire you because they can't continue to pay you and lose money. Business just doesn't work that way. And so if you sort of check off each one of these options, then you should be good to go. And that's sort of just what a company is looking for. Companies looking to grow or sustain itself. It's not ever looking to sort of dwindle down and, you know, let people go. Nobody wants to get fired. Nobody wants to be fired, and nobody wants to do the firing. So business generally would like to grow, And if you can help them grow, you're considered an asset 16. The Hard Part: All right, here's the hard part. This is the part where everybody gets discouraged and they end up giving up. And that's not that's not necessary to be totally honest with you. Now the hard part is actually getting a job. You can get interviews, you can have interviews all day long every single day and never get a job. And I mean, that's frankly, that's just sometimes how life goes, Um, and landing that job can be incredibly difficult. So my advice for you is to repeat all the prior steps. Just keep going through it, create more less, keep applying, keep applying to the same place. If you applied somewhere, and three months later, they still haven't got back to you, Um, apply again. If they said they'll get back to you in a week and they don't get back to you in a week, maybe wait a day or two after on, then hold them to their word. If they said, yeah, we'll get back to you will email you in a week, a week being seven days. If they don't get back to you in like, nine days, email them and be like, hey, so and So I just wondering, haven't heard from you and was just wondering, uh, what's up? Or if there's any way I can help or what I can do? Or maybe you want to grab a coffee and we couldn't talk about anything that might have come up internally. Or maybe they're busy. Ah, throw them some some empathy and be like, I understand it's a busy time of year, especially around Christmas or Thanksgiving or whatever sort of holidays coming up. Um, you know, throw them some empathy, a little bit of sympathy. But then all you have to do is just repeat this process over and over and over again. So this is essentially what I did. So I made a list of 50 companies. Um, and I didn't even get through my entire list. To be honest, when I got my 12 interviews, eso seven of them were my own, and five of them were from a recruiting agency. And over the seven, I ended up taking one that I had up getting on my own. I didn't take a recruitment agency job or a job. That recruitment agency ended up supplying, and out of those 50 I maybe got 20 to 24 into my list. So not even 50%. And I had this incredible turnout rate. Um, now they're several reasons why and their cell For reasons why not? They're out of the Okay. Okay, so let's talk about the ones that I didn't get. Um and this is what you know, People who make courses like this never tell you is that there's a hard part in there is a downside is 50% of the jobs that I applied for almost all of them. So, like, if there were 24 I would say 10 of them didn't call me back. They didn't email me. They didn't even acknowledge that I existed. I had the perfect skills. I have the soft skills to work with him. I have everything that they were looking for. I know that. And they just never got back to me. Maybe they're busy. Maybe my CV got lost. Maybe my introductory email got lost. Maybe they hired someone, said, Well, we're not gonna bother this anymore, cause it's a waste of time. You don't know. You don't know. And there's no use getting down or offended. I voted a lot of people at this point when someone doesn't get back to them, say, Oh, they obviously don't care Well, that's that's not true. It's just they're running a business They have jobs to do. The people who are making the hiring decisions have jobs to do, and so if they fill the position, why would they spend any more time? You know, talking to people who are not going to fill the position now. I mean, it's technically bad recruitment, but a lot of companies do that. So out of the 10 the 10 out of 24 that didn't contact me at all, I just said Whatever and I'll just keep moving on. And if they had not contacted me after I had started getting interviews, I would have applied again. And I know a lot of people like, Well, why would you play more than once? And that's because I mean, it's not technically being annoying. It's being ambitious. Being annoying is applying every single day or calling every single day. Don't do that. That's irritating. Nobody likes that. You'll never get a job that way. But if you don't hear back from them after a little while, you know, get back on and be like, Yeah, I really want to work here. I really I think I have something to contribute to you. And when that happens, uh, and you will eventually. If you don't have a confidence now, you will eventually get that kind of confidence you will be able to go to companies say, Look, I can help you. I know I can just let me prove it to you And eventually a company will say yes, we want you to prove it to us. We want you on our team now. The more applications that you put in, the more times you apply to a job, the higher your chances. It's a simple is that I mean, if you apply for 1000 jobs and you get zero of them, there's probably a reason. So, like if you applied to be a Web developer and 1000 different jobs and nobody called you back, maybe it's because nobody's getting your email. Maybe it's because your CV or your resume or the little piece of paper that you hand into them literally says you cannot tight. You can't type it all, Um, and Even then, I would say that's pretty rare because I just wrapped a blogger article about a Web developer who's blind and got a job. Yeah, imagine that one blind typing and he's used a Web developer. It's pretty amazing. So just keep on keeping on. And anyone who says no to you say, Okay, thank you for the opportunity. Mind holding onto my CV or mind holding on to my resume for a little bit. And next time you have an opening, please consider me and then just apply next quarter next three months. Apply again for the people who are not hiring. But you might want to work there anyways. And there are a lot of companies like that in every city. All you have to do is say, Hey, look, I know you're not hiring. Do you mind holding on Teoh my CV? I think I can be an extreme help to you guys. That's really it. On. Last point for this video is you need laser focus, and that's your key to success. You really need to focus a lot, and it's hard, and it's hard to focus special when you're not getting responses. Ah, it's hard to focus when someone says, no, we're not looking for you. It's hard to focus when, ah, an employer might email you back and say, Look, you just don't have what it takes, like don't let that bring you down and said, Let that inspire you. Let that push you a little bit more So you need that laser focus. Put in as many applications as you can to as many different places. Basically, repeat this process over and over and over, and everything up until this point until you land a job. And then once you land a job we can start talking about. You know what you do after your first month, your 1st 3 months, you for six months after your first year, Um, and all that good stuff. So this is the hardest part of this course right now is I need you to go out and apply for jobs. You made that list and if you haven't, please do go get a list of employers, a list of Web development companies that are looking for people in your city. You make that list, it's not available anywhere. You make that list and then you reach out to every one of them apply to every single one of them. I'm not even kidding. Even if the even. If you think you have 0% chance of getting the job apply anyways because you don't know if they have another position where they might want to might want to put you into it. You know, you might see ah, senior JavaScript developer job, and you might not be able to get that apply anyways because, you know, maybe they're looking for a junior Dev, but they just haven't put the boasting up. Or maybe they're looking for a junior Dev and you know they're ready to put the posting up , you know, later, stumble on yours. Or maybe they don't find any senior Debs that they like. And they come across your resume and give you a shot like you don't know. So you just got to keep those opportunities open. And so, yeah, just rinse and repeat. And once you get a job, then you're laughing, and it's all about learning as much as you can as fast as you can 17. After Your First Job Offer: All right, let's talk about your first job offer. People will typically get pretty excited as soon as they get their first job offer, and they say yes immediately, without thinking about whether they actually work there without doing any further research . And you probably expect me to say, Don't do that. I guess. What? I'm not saying that. It's totally okay to say yes and accept your first job offer with one caveat that carry it being. Keep looking for other jobs. You don't know if you're gonna like this place. You don't know if this place is gonna like you. Maybe they treat you poorly. You don't know yet. Right now, it's still a big mystery, But that mystery comes with a little bit of a paycheck. Yet see you go in for a little bit, and while that's happening, keep looking for a job. And this is one of those hard parts as well, where you work a full day, you're coding your coding, and it's mentally fatiguing toe work all day, especially when you're learning a lot of new stuff, including how a new company works, how their tech stack works. Who people are what people's rules are what your role is. You're trying to learn all this stuff and you don't know how everything really works yet. So just keep looking for another job, because again, that question mark that you don't really know if something's going to work or or not work. Ah, but my advice to you is keep your opportunities open, so keep applying for jobs. And guess what? If you end up loving the place that you work, you can turn down the other jobs. That's fine. Or if another job has a great community or is gonna not a community if they have a great culture, or if they're willing to pay you, like twice, twice the amount, or pay you a lot more and they're a great company to work for and all this other stuff, then you assess the situation that point and maybe switch companies. And that's totally fine, because at the same time the company is also assessing you. How are you doing? Are you eventually going to make them money? Are you going to be an asset to the team? Do you get along with the team? Are you helping other people grow as well as are they helping you grow? So there's assessment going both ways here and it's okay for you to say, Well, you know, this company is great, but it's not really teaching me a lot. And you go over to another company that's going to actually challenge you. Now every company has its own unique culture. Uh, and I mean, for me, the startup culture is nice. I've been enjoying the work life balance. It's fantastic. The people I work with are amazing. And frankly, if I ever got a job offer where I had to work with people I didn't like or people that were , you know, just a holes to me all the time, I would not work there very long. I would take the massive pay cut and leave, and that's sort of my advice for you as well as you don't want to have to work your butt off all day. Um, have people treat you terribly and then go home and you're too tired, too exhausted to go and look for another job. You want to make sure you're in the right place. You want to make sure you have all your opportunities available to you and you want to make sure those opportunities continuously come in even if you love your job. Once you get that job, if you love it, continue to apply for other jobs, even if it's just to keep you on your toes to keep you sharp. There's no harm in doing that, Um, and even if it's just to go and network with people and to get to know ah, bunch of new people who you know make hiring decisions, that's not a bad strategy for the future either. We know autonomy is taking over a lot of jobs. Web development is fairly safe, like we're one of last ones to go. But you mean that doesn't necessarily mean that the company that you're going to be working for is safe from that either. So always make sure you have opportunities open to you now and in the future. 18. Not Getting Interviews? (Solution): This is not for everybody, but it is definitely for the people who are not getting in any interviews now. This depends on where you live, what the economy is like if people around you are buying websites or not. But generally there is a way to solve not getting in and getting more interviews or getting any interviews. So here, a couple of tips. 1st 1 Use different resume types. If you're applying for a job that wants react put react near the top of your resume or your CV. Put it at the top. Put things that are similar to react at the top. Put libraries that are similar or use react at the top. If you're looking, you're applying to a job that uses React Jake where it should definitely be on there, but it should be near the bottom. If you know viewer angular as well again. Definitely put it on there because that shows that you know a lot of JavaScript. But don't put it at the top. What people are going to do when they look at your resume air. Your CV is they're going to take this piece of paper and they're going to look from the top to bottom. So they say your name. They see your phone number, your address. They see some some of your skills and they see some of your history, something along those lines. And if they don't make it to the bottom where it says all of your react skills or the talent that you have, it's react based. Guess what? Then you just lost an opportunity. Now, what I ended up doing was I had Ah, I had six different types of resumes, if you believe it or not. So that really boils down to one resume for every four jobs. Now you don't need to stick with that kind of ratio. I just had six because one focus on python one focus on PHP. One focused on just javascript One focus a little bit more on front end, like CSS one focused on Dev ops. You know, things like that. I didn't end up using all six, but I did have them ready. And that's in in the event that there was a job posting that like, Oh, you know, we're looking for a Dev ops person, then? No, look, you know, I just happen to have my resume. Um, you can try using a difference recruitment agency if the one you're working with right now doesn't get you any interviews and guess what. Go work with someone else. Cut the ties there and go work with someone else. There are tons of jobs for front and developers. If they can get you one, they're not the people for you. Another tip. Stop applying for the best jobs only. Yeah. Okay. Applying for 100 $50,000 a year job. Awesome. If you get that amazing. And I hope you get jobs like that. But that's not always the case. And some people can't figure out why they don't get jobs or sometimes they get interviews, but they can't get the job. Maybe it's because you're asking for too much money. Are you asking for too much money? Take a realistic step back and say, Am I Am I going to be able to make this company $100,000? If not, then why are you asking for $100,000? I mean, it's really that simple. So apply for smaller jobs to even if it's something little like 20 or $30,000 a year, some insanely tiny salary that you obviously can't live on. It gets a little bit of money through your door into your bank account, and you get to learn you don't have to be there for the full year. You only have to be there for a little bit. Learn as much as you can for the first month or two. Continue to apply for other jobs while you're making that money. So now I mean, you might not be able to pay all your bills, but you will be able to pay some of it. And that's stress of not being able to pay your bills starts to sort of diminished a little bit. And plus, you're going to be learning a lot because every time you get a new job you learn a lot. You're going to be able to take that skill from the first, even like the 1st 2 or three weeks, and layer that on top of what you already have. And now you can apply for that next job up and plus you're gonna a bunch more confidence as well. Have you asked why? Maybe there is a reason why people aren't hiring you. Maybe there's a reason that ah, you know, they chose someone else over you within the job that I'm working right now on. I love the place that I worked at, but I work with a guy who got the job quite a bit earlier than I did. I had originally applied for the job that I took at the beginning of my three month little practice period, and I they were actually last ones to get back to me. I went on several coffee dates with, uh with their hiring manager for the development department. And yeah, they ended up hiring someone else over me. And I mean, I work with a guy and he's super super smart. I understand why, and they did the right thing by hiring someone over me. And I only know that because I asked why. I said, Hey, like, how come you hired someone else over me? And they said, Oh, well, he's got a little more Dev Off Dev ops experience, and, uh, you know, that's what we're currently looking for, someone who could do a lot of things but can focus a little bit more on Dev Ops. And guess what? At the end of the three months, I got a call back saying, Hey, look, you know, we're looking for someone on the front end. Are you interested? And I said, Yeah, absolutely. Um is a great company. It's a great company to work for, and I love being there. It's not paying as much as I hoped. But you know what? I'm happy there, and I can pay all my bills and I don't have to worry about money. It's It's the perfect middle ground for me. But I only know all this because I asked why. Why didn't you hire me? Was there something that I could have done That was better. And you should be asking the same things if someone says no, no, we didn't hire you. We hired someone else simply asking, Hey, look like no hard feelings or anything. But why? Why did you not hire me? Is there something that I could improve on? How can I make? How can I make hiring me a simpler, easier, better decision for you? What do I need to do? And they will give you direct feedback. And if they say something fag like, Well, you know, we just hired someone else instead. Ask them why, Like, what is that person have that I don't? And again, it's not like you have to go and hate everybody who gets a job that you applied for. You just need to figure out why they got hired and why you didn't and just learn what they know. I mean, learning is really easy. And so the best way to improve really anything is through direct feedback. Um, and then you have to also realize that there's a business perspective when when companies hire people, they're going to hire internal references over strangers. So right now you're a stranger. If you don't know anyone that works at the company, guess what. You're a stranger. They're going to hire people that they know. So if they have any friends that air, our developers, they're gonna hire them because they're less risky. They'll hire people who could, for all we know, have the exact same skill set is you but are willing to work for a little bit less. That said, Don't devalue yourself too much. Don't put such a low price point that you know either you can't pay your bills or a company says, Well, why? Why this person not think that they're worth, you know, 60 grand? Why do they think they're only worth 20 or something weird? Um, and again they hire references and essentially friends of friends over strangers. So if a company has 20 employees, they're going to ask everyone inside all their 20 employees. Do you guys know anyone else that's interested in a development job? Then chances are they do, and they're going to try to hire those people first because you were typically friends with people who you are similar to, and that means they are less of a risk than a stranger. And as of right now, you are a stranger. Now there is a way to sort of sneak past this one. We're gonna talk about that any future video, so just hold onto that thought for a little bit. So to summarize some other ways of sort of ensuring that you can get some interviews is use different resume types, use a different recruitment agency, stop applying for just the best jobs, apply for all jobs. You are not too good for any job on. That's essentially the mindset of every billionaire on the planet. They're never too good for any job that goes for me. That goes for Elon Musk. That goes for your Steve jobs. That goes for you as well. I mean, the rule applies to everybody the same. Ah, get feedback about why people are not hiring you. Um, figure out what you need to learn and essentially realized that there is an internal business perspective. Ah, and you might maybe want to consider not being a stranger again. We'll talk about that a little bit. 19. Soft Skills Always Win: sub skills always win. You could be the best coder you could be The best programmer in city could be the best programmer in the world. But if you were not nice toe work with nobody wants to hire you. And if they do hire you, they're gonna quickly find out that hiring you was a mistake and they're gonna let you go even even if you make them a ton of money, they might not want to keep you around Just because you can be hard to work with. Are you hard to work with? I don't know. But if you think that you could be hard to work with her you know someone who is hard to work where there has been hard to work with. Think about those traits that they have. And are you copying any of them? Are you using any of them in your day to day life? If so, stop it. You want to be not a joy to work with like I am not, you know, great to work with. But I'm No, that's terrible to work with either. I am very work focused. I don't care too much about making friends at work, and I mean that may or may not be for you, but that's the way I prefer toe work. But I'm definitely not an A hole, and at the same time, I'm not super nice. I'm not super chippy, are chipper all the time, but I come in. I do the job I get along with. Everybody asked people how they're doing. But I also don't sit down for an hour at lunch and talk to everyone every day and ask them about you know, all the things that they've done over the weekend. But again, that emphasis. I'm not in a hole to anybody. Like I come in, I do a job, and I mean, I'm getting paid to do a drops. That's what I do. If you could be nice to people, if you can get along, if you can be friends with everyone, that's even better. I highly suggest doing that now. Soft skills always win over technical skills because technical skills can be taught, but personal skills cannot. A company cannot teach you to be nice. A company cannot teach you how to be a better person, but they can teach you how to code. And so they're not looking for people who can, you know, code the entire Internet or make Facebook on their own. They're looking for people who can get along with other people who can work in a team who can contribute to a company. People who don't have those soft skills. Unfortunately, they're in for a little bit of pain is the best way I can put that you're gonna need to want to change yourself. And changing internally is extremely hard, and I'm not telling you to go and change yourself. But I am saying that if you are hard to work with there, you don't have any sort of soft skills that you're gonna find this whole process a lot harder and that you cannot necessarily make up for that by increasing or improving your technical skills. And my third point is, soft skills can be sometimes look too soft like, Are you crazy? Do you, you know, talk too much? Do you ramble? Are you un disciplined or you unfocused or distracted? Rather, um, you know, don't be that crazy person who just talks all day about their cat. Don't get me wrong. I have two cats. I love them and they do talk about them, but I don't spend an hour at a time talking about them. I do focus on my work a lot, and that's definitely something that you were gonna have to do as well. But at same time, be a genuinely helpful person. And if you do that, you'll find job. No problem. So in summary, uh, you could be the best code in the world. But if you're in a hole, nobody's gonna want to hire you. Soft skills over technical skills Because off skills cannot be talked about, technical skills can be taught, so it's easier to teach someone how to code than it is to be a nice person. And basically, just don't be crazy. Just be a genuinely helpful person. Do all that and you'll find yourself with a job, probably in no time. 20. How To Get A Job By Making Friends: Here's how you can sneak into a company, and I don't mean that in any sort of illegal sense. I mean a completely legal way to sort of sneak your way into a Web development position. First thing you need to do is to find out who works at a Web firm and friend them on Facebook or LinkedIn or follow them on Twitter. Don't stock them. Don't be like two weird or anything. But, you know, if you follow them on Twitter, if you friend them on Facebook, you know, create these little tiny interactions. So if someone that your friend that works at that firm that you might want to work at, um, Post something cool about code, something that you're both interested in, just say, Hey, this is really cool. Um, And then, you know, leave that alone for a day or two, and then when you see them again in a few days on Facebook or on Twitter, just say, Oh, you know, I really like us. And here's what I like about it. Um, you know, Don't be too weird. Don't be too stocky or anything. Just be like regular Facebook friends. And then, after a little while. You can message them and say, Hey, you know, Ah, I really liked We've been posting. I think it's really interesting just wondering if you would like toa go for a coffee and maybe talk some code or something, or I'm interested in getting a job as a web developer. Do you know anyone that's hiring? Um, you know, anything like that? Because now all of a sudden you're not a complete stranger to that company. That company has an employee who now knows about you. And you could do that with one or two people. Don't do it with, like any more than two people. Limit that to two people per de firm and figure out who you're following. So if you're gonna follow someone on Facebook, all right. Sorry if you're gonna. Or rather, if you're gonna friend someone on Facebook, Um, and you're looking for a front and development job. Make sure you, your friend, a front end web developer, don't friends than account manager or a back end developer, because you're not gonna have a lot in common with them. If you want to write javascript, friend, the people who write javascript, then slowly over time, you continue to connect with them. Ah, and then these people essentially are, in some sense your friend, their Facebook friends. And then, you know, you can talk to these people in a more personal level on. Then you can take their interest to a more personal level as well. You can say, Oh, you know, um or Gary doing You have say anything. If they post a picture off their son or daughter, I click like, say, Oh, that's a nice picture of you guys or something like that Again, Don't be weird. Don't be stocky or anything, but get your foot in the door with these people and then slowly over time, become friends. This is not an overnight thing. This doesn't work overnight. This takes a lot of time. So I would suggest starting now, friend, other developers in your city. Because as soon as it comes to looking for a job, you can message people. You can put a post other and say, Hey, look, I'm I'm finally looking t get a job as a Web developer. Does anyone know anyone that's hiring where you can message some of these people and say Hey, look. Ah, I know you work at whatever company. Do you have any suggestions for applying here, or do you know of any other competitors that are maybe looking for someone like because I'm looking to get into the industry? Um, any helpful tips would be fantastic. And so if you take that personal approach all of a sudden, you're not a stranger. You're someone that is coming to another person. A Facebook friend, albeit not like a real life friend, but still a Facebook friend. Ah, and you're asking for their help. And people love to help other people. It makes them feel good. And that's something that you can bring to them. Now, don't be needy. Don't ask them for everything in the world. Just say like, Hey, I'm looking for a job. Do you know anyone that's hiring? If they say no? Well, you say okay, What do you know of any sort of like other web development companies in the in the city that I might maybe that I might be interested in possibly applying to or anything that And if they continue to say no, then obviously they're not interested in helping you, but they might point you in the right direction. And if they do point you in the right direction, well, that's just awesome, because now again, you've got a foot in the door and you've made another connection. But again, this isn't This doesn't happen overnight. This is not an instant thing. This is something that can take several weeks to several months. So if you're gonna take this kind of approach, probably best to start now again, you should have that list of Web development companies in your city. Just go and look at them. See who works at what firms. A lot of companies like toe show off who works, who works there and just find them on freight on Facebook or linked in connect with them on some way that they like to be connected with and be legitimate friends with them. And now all of a sudden, when you apply it, guess what? You are actually a friend of a friend. You are a reference from someone who's already in side. So that's a cool, little sneaky tip on how to get into a Web development firm 21. Your First Few Months: All right, let's talk about your first month now. I don't care what anybody says. Once you land a job as a Web developer, you have two comes of this. You have two purposes at your new job. Your first purpose is to help the company make money be as fast and efficient as possible. But chances are you're not going to actually help the company make any money for the first few months. And that's sort of just a risk that they have to take. And they hope that over, you know, 456 months that you end up getting really good at your job and you actually start making them money. So that's your first purpose. And that's how you maintain your status at any job is you have to be able to make them money the second purpose on, and I would actually argue this is the most important purpose is you have to learn as much as you can never, ever count on job security. People count on job security, and then they lose their jobs, and they think, How come I got fired? Or how come they let me go? I don't because you relied on job security and didn't realize that you were automated by a machine or that they don't need you anymore or that the industry is down a little bit because of recession or something. Or maybe there's a new law coming into effect that has prevented customers from buying from you. You don't know. And this is just a general good rule of thumb for every industry, not just by development, but learn as much as you can all the time. Just keep learning. And if you keep learning as fast as you can as much as you can, you will never, ever be without a job. Well, I mean, you might have periods in life where you don't really have a job, but you won't be unemployable rather. So if you're in retail right now, let's say you're working at Walmart and they bring in those self check machines. Well, guess what? If if you're one of the cashiers, you're either going to get moved to a new department or they're gonna have to let you go and believe me when I say if they have the option to let you go versus keeping you on board , they're gonna let you go because he's going to save them money again. It's not. Greed is just economics. It's just how how the market works. Just, you know, with shareholders and and stock prices and and all that's nonsense. That's not part of this course. So when I say learn as much as you can, I mean assumes you get that job, assumes you land your first job. Your your goal now is to within the first week, learn as much as you can about that company within the next three weeks or your first month . Learn as much about their text back as you can. I'm not saying be a spy. I'm not saying corporate espionage. I'm just saying, Learn about their tech sack. So if they're using grunt or Culp or NPM or something like that and you don't know how to use that stuff, guess what? It's time for you to get really familiar with it, because they're gonna pay you toe, learn how to do it, and then you want to basically invest in yourself. Invest in your own education. Whether that means taking another course online, maybe get the company to pay for a course if you don't know something, but you need to know something. Um, whether that means watching YouTube videos, whether it means taking another one of my courses. Whatever it is, you have to keep learning all the time. Never, ever stop. Now, your second month in. We just talked about your first month, your second month in you should be learning. Uh, not just about your job, but about some other people's jobs to and then your third month in is basically just getting faster and faster and faster. So by your third month, you should know how to do your job, but you're probably gonna be pretty slow at it still, and that's fine. But by your third month, you should be practicing on how to get faster and more efficient, faster and more efficient, faster and more efficient. So now not only are you fast, you're efficient. You're probably going to start making the company money. If not, at least you're breaking even. And you've learned a ton, which means after your three months, if the company doesn't like you or you don't pass your probation, or maybe they just can't afford to have you around anymore. Whatever The reason is, if they cut you from that position, you can take everything you've learned and apply to another job. Now. This is also I have said in a prior lesson that once you get a job, don't stop applying for other jobs. Just keep on applying. Keep those opportunities rolling through the door. Opportunities are not one offs who almost fell off my share. Their opportunities are not one offs. Opportunities come over and over and over again. It's very circular. And once you once you've taken opportunity, more will come. You just have to be open to them. So in summary. Ah, your first. I guess this review called your 1st 3 months. Um, I don't really care what anyone says. You have two purposes. The 1st 1 is helping the company make money by being fast and efficient. On that secures your job there and the 2nd 1 and probably the most important one is learn as much as you can as fast as you can. Just always be learning. Just be an information. Be a knowledge. Sponges take it all in because once you take that information and guess what, no one can take that out of your brain, and that means that you will be able to go to another company in the future. Maybe you don't like this company. Whatever it is, you can take your information. You can take your skills and move somewhere else if you wanted to, or you can really reapply it over. You know you can teach online or you can coach or, you know you can do a ton of different things, but always be learning. That's really the key. Here is learn as much as you can in the shortest amount of time possible. 22. This Entire Course In One Video, Action Items and What to do Next: all right, if there is one video that you watching this entire course, I hope it is this one, because this one is going to quickly go over everything and it's going be very quick, is gonna be very fast paced. And now here's what you need to do to get a job as a front end Web developer to start find 20 job postings in your city. If you can maximize that and create a list of 50 I'm not kidding. 50 Then create a list of the most in demand skills. So if you notice that 20 of the 50 companies that you create in this list want react, then put React down is 20 and if 10 of them want view or angular, put them down as 10. You want to create a list and prioritize it and figure out which is the most in demand skill in your city, and this changes from city to city. So no matter what people say, they could be wrong. So if someone on Facebook says, Oh, go and learn, react and it turns out that you learn react and nobody in your city wants react well, guess what you just wasted Ah, lot of your life because some jerk on Facebook said Teoh, go and learn reacting. You didn't do your homework. So this is your homework going? Figure out if they want react. If they want view angular. Maybe they just want playing. JavaScript just es six. Jake weary. Maybe they don't care about that stuff because they have their own framework. Maybe they want bootstrap or foundation. You know, figure out what they want and learn those core skills and pick the top three and try to learn them. Don't learn them right now, though, because your next step is to spend 90 minutes reading about the top three in demand skills . Read the docks. Google. Why people like or dislike a framework. And if you have any time in those 90 minutes, then practice some scope, some code. And so this point right here is going to take you a minimum of 4.5 hours. So if your top three skills in your city or in that are in demand is, uh, you know, react Jake weary and yes, six spent 90 minutes on react 90 minutes on J Query 90 minutes 90 minutes on E s sex. Read about them. Read the docks. Read why people like it read by people, dislike it, get involved in conversations. And if after all of that, because you might already be familiar with some of those you have some extra time practice writing some of the code. Just get a project set up, get it going. But don't spend more than 90 minutes right now. Then I want you to write your resume or your CV. Okay, that's your piece of paper that lists all the different skills that you have your background, different jobs that you've had. And I want you create three variations based on the top three skills, so create a variation for and this is just hypothetical. But if if the skills in your city are react, view and angular, create a resume for react view and angular just like that and each one you should be putting an emphasis on each skill. Eso again. If you know angular is and demand created TV that focuses on your angular history. Put that at the top. Uh, put reacting view and other skills near the bottom. Switch it up a little bit the layer doesn't have to be different. It just has to have information in different sections. Then I want you to find 1 to 2 front and developers at several companies that you've applied at. So if you applied at, you know, like 10 different Web development companies in your city, um, go and find 1 to 2 and reach out to them on LinkedIn or Facebook or Twitter Twitter, and slowly connect with them in a meaningful way, actually become friends with these front end developers. You're looking to become a friend and developer. Guess what Front and developers air friends with front end developers. So go and make some friends. Now you have this list of 20 or maybe 50. I'm hoping it's 50 job listings companies that are actually looking to hire people. Um, so take that list, and I'm not even kidding when I say this. Go and apply to every single one of them. Even if you don't think you have the wildest shot in the world of getting that job going, apply anyways because you don't know if they're looking for a junior deaf. You don't know if you're looking for an intermediate deaf you don't know if any senior deaths have even applied to the job or not. Maybe they just like you. And they think, Yeah, we'll train you on the technical aspect because you have all the soft skills again you don't know. So apply to all of them. It's only the first few that are scary after that, it's like, OK, I'm just clicking a button or uploading files, clicking a button, uploaded a file and then Ah, really? After that, you have to repeat these first few steps over and over until you get a few interviews and then as a reminder. This is one of the harder parts of this whole course. This whole process is actually getting those interviews because you're gonna get people who don't call you back. You're gonna get people who don't even acknowledge that you exist, and sometimes that hurts inside, and so you just have to move past that. Just ignore them. You might even get some people who are kind of mean to you. You know what, Just ignore them. You don't want to work with those kind of people anyway. Ah, and then your next up is once you get an interview. If you don't get the job itself asked for feedback, why Why did I not get it? There's no harm in saying, Hey, look, I want to improve my skills. I want to figure out how I could become employable. And so you ask. Someone asked the person who did the interview with you just email them or call them and say, Hey, I'm just wondering, like, How come you didn't hire me like, What's What's the problem here? Did you like someone else, or was I lacking in a skill? Or is it a soft skill thing? What is it because you don't know unless you ask. And then once you've landed a job, your goal is to learn as much as possible. Uh, just keep learning, like, literally be an information. Be a knowledge sponge, assume a negative mindset. Just assume that they're not going to keep you around after that three month probation. Just assume that in three months the company is going under, but for that time everything operates. Normally, it is now your goal. Once you have a job no more, and this helps make the entire process easier for you in the future so that if you do have to do this process again, guess what? It's so much easier for you because now you have way more skills. You know what kind of technologies people are looking to use. Ah, you know how to do this job very, very well from a prior company. And so you're sort of future proofing yourself when you have to redo this entire process. So if there's anything that you can do today, it is. Hop on Google. Look for Web development companies in your city. Create a list of 22 50 and apply to all of them. Figure out what they want. React angular view, whatever it is. Ah, and then learn those skills. Don't listen to the people on Facebook, but you can do all of that in one day. Tomorrow. You can spend, you know, 90 minutes on the top three skills just reading about it. You don't actually have to get your hands dirty with any of the code, but just read about it. Figure out what it actually is, what it does, why it's great, why companies want it and you can do that tomorrow and then over the next several days, you can You can hone your skills. You can customize your resume. You can repeat this process over and over and over again. You can write more code, don't get sucked into the code trap. That code trap is when you write or when you want to rights. Nothing but code. Then you like. Okay, we'll get really, really good and they'll have to hire me because I'm so good. Yeah. No, that's not a thing that's just your brain procrastinating because you're scared of applying for a job that you might actually get it. It's called fear of Success. And if it's not that it's your fear of failure, which is Oh, they don't want me. Either way, your brain is trying toe psych you out and scare you. Don't listen to that. Those fears air stupid. It's just your brain just being dumb. Uh, and that happens to all of us, Believe me, even happens to me. Um, so you just gotta work past that and then, yeah, overtime. Just friend. A few people in every Web development company that you apply it. Oh, and don't forget by the end of this week, so I'm going to give you a timeline here in the next five business days. Seven days. So from today to next week, I want you to reach out to a recruitment company. Say, Hey, look, I am a front and Web developer. I'm looking for a Web development job. Ah, I write html CSS three JavaScript, maybe right. React view and angular. Throw that in there and say, Look, can you help me get a job or not? And chances are they'll say, Yeah, because that's how they make the money. Once they place you at a at a company, they find you a job. That's how they make their money. So they're gonna work really hard for that. So multiple your effort by making them work hard. If you can get away with multiple recruitment agencies, definitely do that. But some recruitment agencies have a little closet making signs that you can only use one at a time. So just be aware of that. And then really, all you have to do is get started. So, uh, with all due respect, stop listening to my voice and just go and get started And remember, at any point in time, if you get stuck come back. Because this is the exact process that I use. This whole course is the exact process that I used to get 12 interviews in 12 weeks and ultimately got me the job that I love a lot right now. Um, So go ahead. Get started. I wish you the best of luck if you find any success out there. Definitely, definitely. By all means. Share it with me. Share it with the group. Share it everywhere. Shared on Twitter share on Facebook. Shared on Lincoln. Share it with me. Message me directly. If you can't reach out to me on Twitter and say, Hey, Caleb course was really helpful. Would love to connect with you. Let me know your success stories. And I mean, if you're interested, I'll share them with people as well. All right, so that's it for this course. Um, I hope you find it helpful. Uh oh. I have one more piece of advice for you. Um, some parting advice, even you're probably not going to be confident when you start. And that's totally fine. Something I've learned over my life in start ups and Web developments, changing industries and all that stuff is when you fake your confidence. Nobody knows. So you could be very scared inside. You could be trembling inside, but if you fake your confidence, nobody else knows that you're faking it. They just think that you're confident. And guess what? You don't have to fake it very long. Go to an interview. If your interviews like, 45 minutes, you just have to figure confidence for 45 minutes in your car. You can freak out. Just don't freak out in the building. Just fake it till you make it right. So that's a little trick, and it actually works. So I wish you the best of luck. And ah, please share your success stories with me. All right, I'll see you out there. Cheers.