Blogs Resume building

Writing a Technical Resume

Hey guys, it’s great to see you again. In today’s article, I’m going to talk about the technical resume. In fact, from a 5,000 foot perspective, I’m going to go over the steps of creating a technical resume example or template that, for many of you, that’s all you’re going to need to move forward. For some of you, you may need some additional supports. I also want to let you know about an online course that I have called Finding Work That Fuels Your Passion. In this three and a half hour course, I cover not only the resume in detail but also get into making sure that your LinkedIn profile is working for you 24 by seven, understanding the most common interview questions and best practice answers to those and even creating job search strategy. Again, for today’s video, we’re going to talk about the technical resume so let’s dig in.

All resumes are going to start pretty much the same; with your name, and your address, and your phone number, and your email, and your LinkedIn; but with a technical resume I would also encourage you to add your GitHub link, if you do have one. Hiring managers, technical recruiters, will often scan GitHub, looking for quality code and candidates that are behind that code. What is also very common, in just about every resume you see, is going to be the summary or the professional summary or the professional profile or the profile, however you want to call it. Essentially, the summary is two to four sentences to tell the recruiter who you are in the present sense, maybe add a value-added statement, talk about your strength and your skills, and what industries and environments you’ve worked in.

Just keep it to two to four sentences there. The main thing is, please do not put something like a job objective. Job objectives have not been used for probably 15 or 20 years. There’s no better way to show your age, if you’re an older worker, than to be using something that old which is a job objective, again, a summary. For example, I’m a certified professional coach. Certified professional coach, primarily working with people in mid to late careers, helping them find jobs that field their passionate. You could be a a full stack developer with a passion for leading edge technology. The key is, is who you are, in a present sense, with a value added statement. If you are … Now, I’m talking about a young person who may bebreaking into technology for the first time and they were previously a warehouse forklift driver. You would not be putting on there, warehouse forklift driver because right after that, your resume is going to be eliminated altogether. You want to start out with what it is that you’re going after. It could be a web developer with a passion for user experience but the bottom line is two to four sentences for your summary.

Now we start moving into what makes the technical resume a little bit different than your standard typical resumes, and that is your technical skills. You’re going to want to list your technical skills. These are going to be keywords out there so what are the languages that you know? What are the libraries, the frameworks, the development tools, the methodologies, the databases, anything else out there. Let me give you an example of what technical skills would look like if it was filled out on a technical skills resume. Well, in this case you can see where we have languages. We have Java, and Python, and JavaScript, and libraries. We have Mongoose and Bootstrap frameworks, different frameworks there, methodologies that somebody may use. This is actually alive example or a true example of some of the students that will come out of the BootcampSchool. Let’s say you’re not a programmer. Let’s say that you’re on the network engineering side of things. Well, then you’re going to want to have your Cisco routers and the versions of servers that you’ve worked with. Are you working with Microsoft Exchange or active directory?

These are going to be your technical skills if it’s not on the software side but whether on the programming side, but you’re going to have this right underneath your summaries. Now, if you’re new to the game of coding or maybe you’re within the first six months or one year, I would definitely encourage youth add some projects, two to three projects. One project is not going to be enough. Well, it might be enough if you’ve worked with, you have exact experience in this industry for six months to a year but, really, you’re going to do a lot better with two to three projects. Your projects, what you want to do is you want to have the project name, and I would make sure that that name is clickable so intakes you to your portfolio. List the technologies that you’ve used in that project and then two to three sentences that really precisely describe the project. Let me show you how that might look. Here you can see I did an example of a project. You have the technologies used, JavaScript, HTML, CSS, Bootstrap, et cetera.

Then, I put a description of the project itself, develop app to showcase cred design philosophy, dashboard displays, list of animals, action menu, mirrors, cred functions, app employs, Mongoose. Exactly two to three sentences listing your technologies used, and I just kind of highlighted these in blue just to show that I’m making these a clickable link. Now we can go back into what I would say the typical format resume, which is the work experience. This is going to be pretty much the same. It’s going to be the standard across all resumes from here on out, which is you’re listing your work experience, the company name, city and state. Put the dates over there at the right hand side, right align them. One to two sentences, scope of your responsibilities, and then list several accomplishment statements. Essentially ask yourself, “Okay, how do I know I did a good job with these responsibilities?” That’s what your accomplishment statement is .As you can see, I put two positions there, it depends on what you have with your work history.

Then finally, we’re going to end it with the education, what your college degree is. There’s one caveat here that I want to mention. That is, if you are a recent graduate of the last, say, two years, I would suggest that you move education to directly below projects and above work experience. The reason why is because you want to show the recruiter what you’ve been doing during that time and, if there is a big gap there between now and what your work experience was, that could be a red flag for them. If we immediately show your education was your most recent work experience, then that’s going to resolve the question. Keep in mind that when a typical recruiter is looking at your resume, and they’re only going to spend about six seconds on it, and this was actually validated by the job board, the ladder, several years ago when they videotaped the eye movement of recruiters.

What they found was that the typical recruiters only spending about six seconds on the resume and they’re going to be spending the most part of the resume in the upper part of it, which is going to be your professional summary as well as your technical skills. If you’re new to the game, the problem … Again, this video is from a 5,000 foot perspective of creating a technical resume template. For many of you, this may be all that’s needed, but if you are looking for some additional support, once again, make sure that you checkout my online course in the note section below, Finding Work that Fuels Your Passion. I hope you found this video informative and useful and, if so, make sure that you subscribe to his channel and hit the bell notification, as I do upload new career tips and strategies every Tuesday and I’d love for you to be part of the family. Thanks again and I’ll see you next time.

Leave a Reply

Your email address will not be published. Required fields are marked *