How To Get A Coding Job Without A Degree

How To Get A Coding Job Without A Degree

Hi my name is Mitchell, and this is a video today. I wanted to talk about how to get your first job as a developer, even when you haven't sunk yourself into debt and despair by getting a degree first, this seems impossible when you first start out, but it's completely possible with a more purposeful focus on the things That truly matter, currently I work as a front-end engineer, but prior to 2018 I had no work experience. I had to figure out a lot along the way in the past three years to progress to where I am and now I would like to pass those tips on to you guys to hopefully help you kickstart your career. So, let's talk tip number one be open and honest. So when it comes to getting your first job in IT can be really tempting to lie about your experience or just stretch the truth really thin about where your knowledge and skills currently are

So let me get this straight you're, an expert in in Python C Java Script go c-sharp, Java, rust and you helped build Facebook, yep yeah every every language that is mentioned there. If I wrote it down, definitely something I know: you've got like the Python and the Java or the JavaScript one. What else? Oh and the Facebook yeah yeah me and Zuckerberg like this? I pretty much did it all and he just kind of took the credit so yeah. I know I know what I'm doing trust me yeah. I know what's going on. Definitely definitely you may also feel like without lying. You have no chance getting that job. I'M here to tell you that that's completely wrong, while lying on your resume may seem like a good idea at the time. It will almost immediately be found out and you'll look 10 times worse. You can't control what level of experience you have or whether or not you have a degree. But what you can control is how open and honest you are as an employee and sort of how you come off towards your potential employer.

So be honest, use that honesty and openness to show your employer that, yes, what you lack in experience, you actually will be able to make up with with an eagerness to learn and a completely clean slate for them to instill good work values on to having no Experience framed it in the right way can be a positive thing. Tip number two always be learning. You should pretty much always be taking this approach throughout your entire career, but especially important when you're first starting out in the industry.

Learning how to code is one of the easiest skills to find resources for online. I made a video about this a couple of months ago, but in my opinion, the best way to learn is to be working on your own project. This is going to look great on your resume. It'S also gon na give you a lot of skills that you can then show off to potential employers. It may also expose you to other areas, which can also be beneficial for your job search and for your own personal skills, such as learning how marketing works when it comes to developing your own application, UI UX, and how the user experience you know, impacts how your Your app is perceived and also like graphic design.

Just take it take a shot at You know, sort of designing your own layouts for different pages or how your apps gon na look, and while it may not be great skills to start off with. If you can do all of this, you can wrap it all into one and build your own app touching as many areas as possible. You actually going to be really valuable to potential employers, basically go out and learn the latest new trends or technologies or frameworks, or anything that really interests you, because that's pretty important, make sure it interests you, because you're going to learn it way faster, you're gon na Be much more excited about it and you're going to have all of these new technologies and new skills.

That'S actually gon na make you valuable to more older programmers who may have tons of experience and may know a lot there's a lot. You could learn from them, but there's also stuff there that they could learn from you because they've been in this industry for 10. 20 years - and they don't exactly know how the latest iterations of some JavaScript frameworks work so wake up every day and go find something That you're excited to learn and learn it. You can do so much in one day and if you focus that energy on learning for it for two or three months, you are easily going to be able to land a job somewhere and get started in the comments down below. I encourage you guys to. Let me know something that you want to start learning today or if you've already started learning something in the past few days. Put that down as well tip number three is have confidence in what you don't know. This may seem less intuitive than the previous points, but I can promise you it's been integral in me, landing certain jobs and the growth that I've had during those at the end of the day.

There'S really no escaping it. Without experience, you're going to be lacking some fundamental skills that can only really be gained from being in the industry and working with your peers, you can choose to shy away from these in constant fear that someone's going to one day expose you, because you don't know How a database works or the language that the system is built on? You only know how to google it and that's about it, although that's most of what the job is, but don't shy away from these things that you don't know be upfront about it and focus on personal growth. In my experience, employers have never shamed me for not knowing things. For instance, your boss is gon na want to trust that they can give you a task, and it's going to get done, and if that task involves doing things that you just don't currently know, then they can at least feel assured that you will ask for help.

Instead of just randomly trying to press buttons and writing scripts that are going to either break off the system or leave a trail of bugs behind them, okay, so the bosses asked me to simply do that thing with the database. So I guess I can just Google database commands and I'm sure I'll figure it out I've. Many too late, tail interesting, drop tables, that's a weird term, but it seems like it could be useful. Let'S give it a shot. tip number four is work hard and always push for more. This seems obvious right work hard to get anywhere, but it's actually important to be quite conscious about your want to be better at your job and to excel in the job that you've been given. When you manage to land your first job, which is awesome, congratulations, you may be stuck with a junior developer role or a QA role, or some tech support role, and some people can stay in that role for four years, without really moving that far up or gaining Too many skills, but if you want to be a developer and you're stuck in QA as like a stepping-stone, make sure you're conscious that this is a stepping stone and the way to move to the job. I want to get

I have to learn certain things and I'm going to tell my boss: that's what I want to do constantly be pushing take on as much responsibility as you can reasonably take to. Let your boss know that you are very eager to learn and you don't want to be staying in your current role forever most IT companies can actually have a budget for personal development, and they may be able to help you get that online development course that you Feel is going to make you so much more of a developer or is going to help

You learn a specific language that you're really interested in as long as you can convince him that it'll help you on the job as well. Don'T ask them. Oh. Can I take this course in Python, when it Python doesn't touch a single part of your code. Make sure it's related to what you're doing, but most companies will be eager to skill you up a bit because remember the better developer, you are the more you learn Yourself, the better developer. You are for the business as a whole. In my first IT role. I went from tech support to junior DevOps in a matter of like four months, because I was constantly pushing for more and more responsibilities. So don't be complacent, don't sit there in your comfy role and be like I'm doing my job and everything's good, constantly try and push to do better and be a better employee tip number five. The last tip is to stand out from the crowd, so in my first job in IT I was eventually given the responsibility of sifting through all the different candidates for a tech support job that we were advertising for and to pick out the who seemed like the Best ones to move on for a phone interview, No yeah, all right, yeah, no Mitchell, how those resumes yeah, the resumes are yeah they're, coming on great boss,

No, no, No. This helped me discover that 80 % of applications look exactly the same In my experience, especially in IT, and they will be just immediately discarded by most companies, so try and think if you can add some personality to your resume, while keeping it professional. So, for instance, in my resume I had a picture of myself in the in the top right corner and then I also had like, like color just a little bit of color

Most people have a straight black-and-white resume. I chose you know what I want to put some color in there, and also this is what I look like deal with it. This is actually works quite well for me in the past, with employees saying that this was actually a positive thing and helps them kind of like see a little bit more of Who I am, and it's do that a little bit more from the same black and White wall of text resumes that they used to seeing, but keep in mind that I have read online, that some people don't like this people, don't like some people, don't like having like a picture in the resume or having some color. That should be a standard way to do it and for me, if I'm gon na be turned away, because I made my resume a little bit more creative while still staying 100 % professional. But it's got a little bit of color.

It'S gon na picture of me If that's gon na make you turn me away because I'm not standard enough or something like that, then that's, probably not a company that I would have wanted to work for in the first place. So it helps me weed out potential employers who are going to I'm gon na, like I'm gon na get the job there and then two weeks in I'm gon na be like wow, I'm working in a jail cell, or something like that. I want to be able to enjoy the place. I work as much as possible, and so, if they don't like the bit of personality, I've shared in my resume, then we're just not a good fit for each other.

Now, referring back to tip one when it comes to your resume, don't put skills on that you don't truly have and more importantly, don't list every language and technology. You can possibly think that you've ever touched before in your entire life. So in Mitchell, I can see here that you've listed JavaScript as something that you feel confident using, which is great, because this is this is a front-end role. But you also listed other things and I'm curious why you felt the need to add these as well to your resume.

Let me just read them out for you here, so you've got docker and go okay, Machine learning, augmented reality, typing online research, Adobe Photoshop every tool in Microsoft Office I mean you've, just listed them all and finally, you've ended up with we've minecraft you've added minecraft to You a list of skills, So I'm wondering oh, I'm incredibly insecure with my skills and feel deeply inadequate compared to my peers, applying for the same role right sure. Also, I really just like Minecraft it makes you seem like either you don't have true competency in anything or you're, just a liar, Let'S say, for instance, you're applying for a front-end position and you've told them that you feel really confident using react and you've even showed Them a few projects that you've built before they're, probably going to know that you know how HTML and CSS works right.

They don't need you to put every single thing down on there only put the stuff, that's relevant, the big important stuff. That'S it. No fluff focus on proving the skills that you have in the interview. The resume should just be to get them interested to call you back, get them to bed. Don'T lie, get them to call you back, because you seem like you're an interesting person with a decent resume and then in the interview.

That'S where you go: Okay, here's the projects. I'Ve worked on, like I'm, showing you firsthand. This is how I learned them. For instance, my resume included things like my old YouTube gaming channel. Now I didn't put on there like. Oh, I made Minecraft videos because that's kind of pointless, but I did put on there that I created a business

You know I created content online, which is like this business that made X amount of dollars in revenue, and I even framed it in a way that, like I made because I did this when I was a teenager, mostly, I made X amount of dollars in ad Revenue before I'd even finished high school see now I'm turning something like you know, making dumb game videos and turning it into something. That'S actually quite impressive from a more of a business point of view or framing something in a way that is actually relevant to your job and to top it all off. It kind of makes you a little bit more interesting.

Most people are going to be coming in with I studied this degree, and I got the degree and now I want to work in the job and that's it sure who you are as a person and do it without just listing. I like to play basketball and draw things, and I play video games, don't put that on your resume, put things on your resume that that tie to the skills that you might have or abilities that you feel confident in. I don't know how to finish that sentence. Yeah there you guys have it five core tips to help. You guys kickstart, your careers as programmers I'll, be answering any and all questions that you guys have in the comments down below so don't hesitate to ask something.