hitting the high points

full transcript

auto-generated from the audio, so expect a few typos. the audio is the source of truth.

Let's dive into the first thing. So I want to go over, um, I want to go over resumes. I want to go over resumes. So I'm going to pull up. I'm going to share my screen. Um, let me pull it up real quick. My resume template. And again, the whole thing is I want you to ask questions, right? That's the reason why I do this. So I'm going to share my screen. Um, resume templates here. Share screen. All right. Here we go. Sharing the screen. All right. Hey, Seth, what's going on? Man, it's good to see it. Hey, hey, Seth in the house. Seth, uh, I was very disappointed.

I was very disappointed. You hung out with the evidence care crew, the old evidence care crew. Um, and I was not invited. I hung out with Alan the other day. Um, I miss you all. I just need to get a group of people. I actually, I may do that. I may do that. Nashville. We're just going to throw kind of an open bar or party. So I'm, I'm going to do that. I'm going to do that when, when, when, uh, here in the next month, I am going to, uh, uh, I'm just going to have an open tab and all the engineers weren't coming out in Nashville and just party it up together.

Um, because I miss you all very, very much. Robert Good morning. What's going on? Winston just stumbled on this. Glad I did. Winston. I'm glad you're here. Man, y'all, y'all, everyone go connect with Winston, go connect with Winston. He's a new part of the family. Um, and then resume Hones knows Ben. I don't know what that last word means. Micah. Thanks, man. Hey, having got started. I haven't got started. All right. Cool. All right. So let's talk about, let's talk about resumes real quick. So, um, hey, also, by the way, if you want this resume template is on my website, TaylorDess and dot com. This resume template is on my website.

So go check it out. So here's what I like to see on resumes. And as you can see, it's very, very clean. It's very, very simple. Um, I am not a designer. I know there are designers that have gotten into arguments with me with my fonts, et cetera. I love Garema. I think is what it is. That is what this is. I love the way this is set up. Um, I actually shout out to the Vaco Raleigh crew. I got this resume template with Vaco Raleigh. Um, and I've used it ever since. I do not guarantee a job offer. And I would say I would not guarantee an interview, but I would 95% guarantee an interview if you use this template and you write it the way you should write it.

You will be very successful getting interviews with this template. And so, so let's go ahead and dive in. So the first part is the summary. So the summary is incredibly important. Uh, incredibly important. Um, I need to see bullet points or no paragraphs. And I also want to see summaries of what you've done at a high level. Right. So for me, this is honestly one of the most underrated parts of a resume. And if you have a good summary, I'm not reading the rest of your resume. I'm calling you immediately. So, so I don't know if you guys remember when, when I don't know in grade school, if they taught you how to write a, like a paragraph, but like you start really broad, it's basically like a B, right?

You start really broad and get very specific. And so that's how I'd write your summary. So again, coming from a software engineer perspective, let's say you have 10 years to software engineer experience. You've, uh, have five years of dot net experience and three years of angle experience, right? And obviously if you have 10 years of experience and engineering, you probably have a lot of different skills. And so that is, but I would put the summary of the, or I'd like the skills that you want to find a job for, right? So if you're a dot net angular developer and you're targeting dot net angular gigs, and what you want to do is be very specific in the summary.

I have 10 years of software engineer experience. I have a BS in computer science. I have five years of, um, I have five years of dot net experience through years of angle experience, right? That's what the summary needs to be. Super high level hitting the main tech and the most important tech in tech right now, if that makes sense, right? So if you have some Azure thought up there as well. Again, if you have any questions as I roll through this, ask me, ask me, throw it up on comments. All right. So the experience sections and credit point, I'm going to zoom this in a little bit more so y'all can see it.

Um, so I would write it very project oriented again, project X, right? I would list out your major projects at each company where the X marks, I would just list the application name of the project name. I would also describe what the application software feature that you wrote or does and then bullet point out responsibilities, right? This is, this is incredibly, incredibly important. Um, so Edson comes in real quick, come back to the summary. How many bullet points is a good summary? Of course we can't put a lot. Yeah, I would say, I would say up to five, five or six. Again, you're going to ask me where you're going to come up with that number.

I don't know. I just think that sounds good. Um, Elliot goes. Elliot, what's up, buddy? It's good to see you. Hey, thanks for, thanks for chiming in on the career, thank you other day. Buddy, I appreciate you. You were time. I appreciate your support with the pitch section. Pretty much be the same as your elevator pitch. Yeah, basically. Yeah. Hey, Elliot, tell me about yourself. Well, I got two years of engineering experience. I got one years of reacting experience. I'm currently at Lowe's developing a really, I don't know, lightweight, react framework UI, blah, blah, blah, blah, right? Very, very, very high level. Um, and so again, project experience, project, right?

Don't give me a bunch of dang tasks. Also, people have problems writing their, writing. So if they've been at the same company for multiple years and they've grown within the organization, they have a hard time writing it a certain way. This is how I would do it right here. It's the more junior position held, right? Start date end date and then obviously your main position is right here. Actually, what you need to do is, is you need to do. So what I would do is current position held. Then I would do, then then I would do month. Yeah. So I would do that. Does that make sense?

Everyone makes sense for that. I feel like I'm live coding. I feel like I'm live coding on the fly. No one or why developers. Y'all terrified of doing it. I don't mess enough backspaces and stuff. Um, all right. So any questions there? Let's see. I got some questions coming in. Uh, it's just so Connor. What's up, Connor? I hope you're well, hope ever note is true. You well, shout out, ever note. Hey, Connor, I want to work with Evan. No, ever note. Can you help me up? I want to staff forever note. That'd be sick. I just want to, I listen, I just want to staff for cool companies.

That's all I want to do. Netflix, if you're watching, want to staff for you. Right. I just want to work with cool companies. Um, I love the project based structure. But when I do this, my resume runs like four pages, just two to three projects per organization, three or four bullet points, you tend to run. Remember, okay. Yeah. I mean, this is where for me, I would just highlight the main projects, right? Again, two to three pages, Connor, you have enough experience. You've been doing this thing for a bit now. It's okay to do three pages, but that's where I would be. The summary would be really key.

Right. Highlighting what you do. Um, you know, in the summary section thingy and then two, three, two, three main projects that move on. Right. Um, and, and, and again, you highlight the stuff you want to be called for. Does that make sense again? Your resume and your LinkedIn is not for you. Your resume and your LinkedIn is for hiring managers and recruiters to find you. Right. So that's where I would really put when it comes to specific things. I would really just put project wise that you want to get called about. Um, Elliot always fun hanging with you cross platforms. Yeah. I love it. Man, no, it's cool.

That's cool. The community's awesome. I love this. Uh, Casey, any tips for resume, transition from different field of the tech. I have a portfolio, but haven't gotten to the first gig. Yes. You need to write. You need to write your resume. If it isn't a non, if you're transferring industries, you need to write your resume. Like somebody not in your industry knows what you're doing. Right. So like, for example, I use this a lot of times. So I used to serve tables at Outback Steakhouse, shout out Outback Steakhouse. I love that restaurant. My dad owned the Outback Steakhouse at my hometown for 25 years. Fun low fact.

And so, um, so for me, Casey's like, for example, so Casey, let's say I was interviewing or write my resume, I'd be like, you know, serve it out back Steakhouse here, the durations. And I would say, um, made sure customers, you know, had a high satisfaction. Um, you know, delivered food on time. Um, well, you know, uh, made sure, you know, tables were cleaned. Right. So I mean, like that's what a server does. But Casey, what if I told you, um, worked for one of the top 10 restaurants and sales in North and South Carolina at a 300 restaurants? Um, I hit six sales awards.

Um, Outback, I hit six sales awards that I've never hit that usually most servers only hit three. Um, I did up to $1,500 in sales a night. Most people average 500. You see the difference in that. Like that's how you need to write your resume. You need to write your resume as if somebody who has no idea what you do. You need to brag about yourself in that way. Right. Get quantitative. Right. If you're a forklift driver and you, I don't know. Like, it did some pretty cool stuff that no one else has done. Like, I like that. Right. Um, let's see here. Good evening from Pakistan.

Hey, we are international Kenya, Brazil, Pakistan. I love it. Uh, chio for non tech business jobs. Should we have bullet points for them or just a less company position? So if you are in your first job or two in tech and you want to show like consistent work history, I would just put your job bullet points. Uh, or just position company employment dates. If that's all you have, then no, I would not do that. If that makes sense, Connor, we can see. Uh, Edson, if I'm specializing in some specific cloud, like cloud, microservice, it's a summer. Yeah, absolutely. So I would say like two plus years of AWS, specifically with Lambda and S3.

Um, uh, six years of microservice architecture experience. At Disney, Netflix and YouTube, you know what I'm saying? Like, like, highlight that stuff out, but that's a great experience. So brings comes in and goes, I have no prior experience. Can I put portfolio projects there or so if you have no prior experience and I'm assuming in your resume brings, um, again, this is where you need to write previous employment in ways people can understand. Um, ishmael, I've been applying a ton of broad, but think it response. I'm changing careers. Yeah, again, you need to make sure your resume is written really, really well. So where people can understand what you do, that's not in your industry.

Right. So like, for example, one of my wife's friends runs a vet. Like they run a, she runs a vet and or like a place where they house animals. But like, there's like a bunch of cool stuff that she's done that no other vet provides. Right. So like you need to highlight that stuff brand and what's going on. It's good to see you. Elliott, have a generic one or two page or bid you advise clients to have a long form resume to cherry pit content for a laser focus one off resume to a specific role. I think you need to have no generics. I think you need to have one to three specific resumes based off the type of jobs you are trying to find.

Right. So if you're a react, no developer and you want to find react positions and node positions and you have two resumes, one highlighting more react positions or projects you've done and one highlighting more node projects you've done. You don't want to have generic resumes that will not help you. And so I'm 20 plus years experience almost for five to do companies to do okay to include all companies in a professional experience. Sure. Absolutely. If you have done, like let's say you've done microservice experience within all five roles, then I would just say maybe just say, you know, six plus years of experience that yeah, that's fun.

I like that. Like that. Connor, where would you put things you do outside of projects? Uh, I hate to say it. So I would put that in maybe the summary. So if you scroll down here, I forgot this was even open. So there's certificates right here. I really need to change this to like, we need to change just to like projects. Right. And then here is where I would put it. But at the end of the day, Connor, and I'm only one recruiter and I, I don't have a lot of time to look at resumes. I don't really care about projects. But again, I know some HR people like to see you have other interests.

So, uh, Ellie, is it if I'm going for a tech role, do you think that someone could combine all non tech roles into specific domain into specific? No, I would just keep it. So if you are going into a tech role, show continuous employment history, make sure that information is written out. But again, write your resume to where people know what you do, not in your industry, but I wouldn't like lump anything together. Um, Connor Bush, I have a section that's called Community Open Source Involvement. I love that. Seth, I love that. I love that. So much. Love that a ton. Um, all right. That's it.

By the way, check out Libruk, L E B R Libroc. That's just some 80s vibes. All right. Awesome. Seth, I love that so much. Thank you all again for coming out today. Um, I have to go eat breakfast real fast before my 10 o'clock central call. Um, if y'all need me at me, comment me again, join, join my, join my text messaging community, 615-235-5650. Um, go to my website. It has my resume template. Um, and thanks for coming out. This was great. I'll, I'll do LinkedIn next week. I'll do LinkedIn next week. So y'all come out. Um, and again, if you have any questions, text me, I will try to respond to them.

So leave comments on this and I'll get back to it. I appreciate y'all ton. Y'all have a great July 4th weekend. And I'll see y'all Tuesday, because I'm off all Monday. I appreciate y'all ton. Go America. Just kidding.