 What's going on everybody? Welcome back to another video. Today we are going to be reviewing your resumes. Now if you didn't know this already, I'm about to drop a pro tip on you. Your resume is really important in order for you to get a job and that is the high quality content that you guys come here for. So today I'm going to be reviewing some of your resumes and there's going to be a little bit longer video than normal because I will not be doing a lot of cuts. I'm going to be starting from the very top of the resume, working my way down to the very bottom of the resume. I'm going to be marking up the resume as I go along with my thoughts and critiques, things that I like, things that I don't like. This is going to be completely anonymous. So I'm going to take all of the personal information out of these resumes so that I can critique it without anybody feeling bad. So if your resume is completely terrible and I call you out on just about everything, there's no hard feeling because it's completely anonymous. Without further ado, let's jump into our very first resume. So here's our very first resume. Like I said, we're going to be starting from the very top, going to the very bottom, and I'm going to be marking this up as we go along. So let's start at the very top with the header section. So he has his first and last name, phone number, an email, location, and then his LinkedIn. All good things. You can also add any type of website or any type of portfolio there as well. But how he has it looks totally fine. So I don't really have any feedback on this top section. Let's read this professional summary really quick, analytically driven financial analysts with two years of experience focusing on error-free reporting and analyzing trends on actual versus forecast revenue and indirect rates, managing an average of 12.5 million worth of direct projects each month as corporate FPNA mid-level associate. So, you know, a lot of people have a lot of different opinions on what you're supposed to do in this section. Some people take it truly as a summary. Some people will have bullet points and say kind of highlights of their career about them as a whole, like their education and different things. I have my own opinion on this and my opinion is that this is supposed to be kind of like a sales pitch, an elevator pitch, if you've ever heard of that. So imagine you get on an elevator with Elon Musk and you want him to know who you are and what you're, you know, you say you want a job with him, what you're looking for within those that 30 seconds that you have before he gets off the elevator. That's kind of what I imagine in this professional summary. And so it's hard for me to say that there's one right way to do this. So I'm just going to give you my opinion, what I think should be changed. In my opinion, I don't think you should be throwing around that you're working with 12.5 million of indirect projects. I don't think that's really, that really makes sense to be in a professional summary. The first part isn't bad because you say who you're a financial analyst with two years of experience and these are some of the things you worked on. In my opinion, after that sentence, you should be saying like what you want, you know, here's who you are. Here's what you're looking for. And that's just my opinion. So again, I hate to, I hate to say that this is wrong because this area specifically is taken in so many different directions on so many resumes. So I'm not really going to mark that up. I think you can, I just would take out the 12.5 million worth of direct projects to me that just, I don't know, doesn't, doesn't rewrite feels a bit like showbody almost. I don't know if that's the right word. That's just my opinion. Let's go into the skills section. This is probably one of the more important sections. And let's look some of the skills that we've got. We got Cognos, Excel, Python, R, Microsoft Power Query, cost point, Power BI, SQL, Hyperion, SmartView, Java Tableau. Some of these things I have not heard of. And so this may be domain specific for financial analysts like cost point and Hyperion. I've heard of Cognos, but I don't use it. Normally how I would like to do this is kind of order it in the level of importance. If they're skimming this, they should see the most important ones right away. To me, things like SQL, R, Tableau, Power BI, Python, Excel, these are the things that I would be putting first so that when they are glancing at this or just looking at it, they see those things first and put things like Java, which not a lot of analysts are going to be using Java, Hyperion, SmartView, cost point, all these other things I'd be putting at the back or maybe even separate into two sections depending on the financial analyst role that you have. Then there might be two different skill sets. Some are domain specific, some aren't. So you can separate them out. But I would just be putting those first. Another thing that I really wish was on here, and let me get rid of these really quick, is after Python, if you just do a parentheses and you put some of the things that you know within Python, I find that to be extremely helpful. Because when you put Python in your skill section, to me, I don't know what that means. What do you know in Python? Do you know web scraping? Do you know how to build machine learning models? What are you doing with Python? I don't know. For me, I like seeing Pandas because Pandas is, of course, an analytics library in Python. It's extremely popular. It's used by a lot of teams. It's used by our team. I like seeing that where people have parentheses and have a subset of skills within that, or libraries or whatever it is. That's not only used for Python. You can do the same thing with Excel. You probably don't need to do it with something like SQL or Tableau. Those are pretty standard, I feel. I wouldn't be going in and putting SQL in parentheses, joins, unions, store procedures. That's just not something that I would do, but you can do that if you'd like. That's up to you. Overall, the skill section isn't bad. It says the skill, and that's what it does. If that's what you're going for, it was good. I would add more to it. I'd organize it a little differently. Let's look at this work experience. First off, right off the bat, this work experience section down here looks really odd to me. There's some really relevant stuff in here, but it doesn't elaborate on any of this. You have things like system admin intern, customer care analyst, data center technician 2, accounting intern, and then you have your current role, which is the financial analyst and financial planning. To me, it just feels really odd, like really cramped. I would choose maybe just the top one or two jobs that you feel are the most relevant or the most recent and include bullet points on those as well, because it just feels like you only have this one role that you're trying to put on there. This is really quick. Then there's this additional experience down here, which just feels even more strange. Again, I would cut out this additional experience. A sales consultant really doesn't have much to do with it. What I would personally do is I would trim this down to the top three jobs maybe, and then I would elaborate more on those. Let's really quick, going back up to the top. You don't have to have six, seven, eight, nine, 10 bullet points per job. I think five is like the max. You don't need more than five bullet points. I don't think you should put more than five bullet points. You should be able to condense your role, your main tasks that you feel are going to give somebody a good understanding of what you've done. I would trim back this first one right here, and then I would elaborate on maybe the last two jobs. Again, I don't know what these jobs, I don't know what you're doing in these, so take it with a grain of salt. I don't know exactly what you're doing in all these jobs, but it's really cluttered. There's a lot just going on right over here. This isn't how I would personally do it. Again, this is all just my opinion, you don't have to take my advice. This is just what I think. Let's take a look at some of these job descriptions within this role. Performing ad hoc analysis, special project as requested, assisting in planning, development, and execution of long-range deliverables. I'm going to skim really quick. Creating reports to help analyze in actual, help analyze actual and forecast potential areas of risk, contribute to monthly processes, prepare timely and insightful monthly variance reports, and create and execute. So everything that I'm seeing is really high level, which is not a bad thing. You have some action items like you're performing, you're creating, you're contributing. Good stuff. Something that I would be adding is if you can, and not everybody can do this, and not even everybody has even made that huge of an impact in their role, which sounds terrible, but if you can quantify any of this, any type of numerical information like I performed ad hoc analysis and special projects as requested, working with 20 different vendors or working with banks or whoever you work with, just something to quantify some of the work you do because when you say that, it can mean very little or can mean a lot depending on some of those different variables. Anything including like if you got your company a grant that got them a million dollars or something like that, you can throw that in there and it's very quantifiable and they can really understand it better, I think. And so yeah, that's the only thing that I think it's missing. I don't think anything that you have on there is terrible. That's just at a quick glance, that's what I think. And then I would again, I would redo this section a little bit because I feel like you just included too much. It's all the way back to August of 2010. I mean, it's 11 years ago. I don't think you need to go that far back. And so let's go down a little bit further. Let's go look at the education. So in 2019, graduated from George Mason University, double major in accounting and information systems and operation management. That's really cool. GPA three out of four. Boston University Masters of Science and Applied Data Analytics. Very nice. So good education. I'm not a person who wants to put the I think I had like a three, four or something. I don't I've never felt like the GPA was something that I should put on there or supposed to put on there. And I think that's I think that's really location based like that's like, like some people in certain countries or certain locations do that. I have never done that. I've never really cared if somebody had like a 4.0. You know, that's just not something that I personally have cared about. But I do think that sometimes in like internships, or if you're getting like an entry level job right out of college, it may be worth putting on there. Sometimes they require it is what I've been told. Again, I didn't do any type of internship. I just dove straight in and I didn't have that on my resume. So, you know, my opinion is just not to have it on there, but there are some cases where people want it on there or need it on there. So let's move on to the year up awards. And yeah, let me just I would just remove this. That's really all my feedback on that. So the year up a year up awards. I don't know what that is 2014 or 2015. I'm sure that's it might be like a company based thing. This is under his achievements. Excellence of leadership, engagement, embrace diversity, perfect attendance, intern of the month award. What is there to say? Won some awards, added them to your resume? I don't necessarily see a problem with it. Again, I have a lot of really I don't maybe maybe I'm just unique in the fact that that's not something that I would put on mine or care about. But you know, honestly, I could see people wanting to see stuff like this. And so I don't have a problem with this being on here at all. I personally just that's not something that I would be adding. I think things like scholarships and you know, awards for I guess maybe for for leadership and stuff like that is not bad to add. It's just not personally something that I would be adding to mine, just my opinion. So overall, I think this resume was not bad at all. You know, good education already has two years of experience, really good skill set just needs to be reformatted in my opinion a little bit. The layout overall is really good. I really like the sections and the layout and the way it's organized. Some people will put this skill section like way down here, even under education sometimes, I like that the skill section is right there. The glance factor is good on this resume. If you don't know what the glance factor is, the glance factor is the 15 seconds that a hiring manager or recruiter is going to look at your resume. And within those 15 seconds or however long they spend, you want them to really see who you are, the skills you know, the experience that you have extremely quickly. And this has that glance factor. I can really quickly skim this resume. And it's not super cluttered. It's not it's not a ton of reading. It just it tells you what it needs to know. So overall, I think this is a really good resume. I just had a little bit of feedback. But you know, I like this resume. So let's move on to the next one and see what that one is like. Alright, so we are on to the next resume. This one is definitely very unique. I'm going to scroll down really quick and just show you. It has the resume but also has some scripts as well. If you've seen my video, I used to do this when I was first starting out is I would send scripts with my resume, very similar to this. It was actually a separate file, but he just included it on his resume. So I am really looking forward to actually looking at these scripts and telling you what I think of those. If they, you know, make them look good or, you know, don't make them look good. You know, you can tell a lot about a person by how they write a SQL query, just so much. No, not really. But we're going to look at that in just a little bit. Let's look at the resume first and then we'll go on to the the SQL scripts. So right off the bat and I'm going to maybe zoom out a tiny bit. Maybe I shouldn't have done that. Let me go back. Right off the bat, my first impression is this isn't my favorite layout I've ever seen. Is it bad? It's up for interpretation. I don't hate it. I don't love it. And maybe that's just as bad as not like not loving it. Like it's just bad. To me, this kind of resume, I don't know, it just feels weird. I don't know how to explain it. I am a classic. Keep it simple for those automated processes on LinkedIn and stuff. Keep it simple to where the machine can read it. That's what I like. Again, personal preference. But let's start at the very top first name and last name. He says aspiring data scientist with BI and inventory background. Okay. I guess that's cool because there's a contact section right here. Let's take a look. The phone number, LinkedIn, hotmail. Okay, real quick. Oh, do I have this pulled up? Give me a second because I've been using this is what I'm using to get on here. Hotmail. Who uses hotmail? Because I didn't know hotmail was still in use. I thought they like discontinued that like 20 years ago. I'm obviously joking. But I mean, come on. Like just get like a Gmail account. It looks more professional. Hotmail makes you look old. I don't know how old you are. I really don't. Let me look. I'm not trying to be mean. Okay. So you graduated. It looks like with a bachelor's back in 2000. So you're so you are a little bit older with with many years of experience under your belt. I'm sure it shows age quickly. I personally recommend trying to stay up to date on I don't know. I don't want to say current technologies. But a hotmail has been, I mean, I don't know anybody who uses hotmail anymore. Just something I would take into consideration. It kind of shows a little bit of age on that one. And they also have a GitHub contact section looks good. So lots of good stuff in there. Let's look at the profile, an analyst background, oops, an analyst backgrounded in statistics and business operations with a strong passion and identifying patterns with seas of data, helping businesses make better decision by translating data into meaningful details interested in opportunities for gaining experiences in the areas of data sciences. Identifying patterns within seas of data. That's some that's some imagery right there. I'm not a big fan of poetry and imagery in a profile section. Also, I feel like it's super vague. Everything in this was vague, especially this part right here. So interested in opportunities for gaining experiences in the area of data sciences. Data science is so broad. I'm a data analyst. So of course, I know more about the analytic space than than this, which looks to be like a data scientist one. I'm just saying that that's super broad. And there's 100 different things that, you know, you could be looking for and we would have no idea. Just the area of data science. My advice is keep it simple. Two sentences, who you are, how many years of experience, the skills that you have and what you're looking for. This what you're looking for is just not beneficial. I feel like you need to be a little bit more specific. Yeah. And the seas of data thing, you know, maybe that just really shows your personality. I do not know you personally. And so, you know, maybe that's something that you really like and you want to keep in there. By all means, keep that in there. Gosh, I got this nose itch. I apologize. By all means, keep this in there. But it's just, it's, it doesn't come off as like, I'm a, I'm a super professional when, you know, you aren't being super specific on what you want. And you're adding, I don't know. And it just doesn't seem, this doesn't read super professional. That's my opinion. So let's move on to the skills. I feel like I've talked about that one enough. We have SQL, Python, SSRS, Microsoft, Excel. So you hit a lot of the core stuff. SQL, Python, SSRS is for like reporting in SQL server and then Microsoft Excel. All good skills. I feel like it's a very small list. Let me see. So you're a BI reporting developer. Yeah. And maybe you just don't have any other skills. I would recommend, and this is just me, because this is a very small list of skills after how many years of experience back to 2011. Going back to 2011, I feel like you should have more than four skills. And maybe I'm wrong. I feel like you could pick up some skills on the side. I don't know your personal life. I don't know how much free time you have. But over the course of 2011, the past 10 years, I think you should have at least more than four skills. Try to pick up a cloud platform like AWS or Azure. Maybe try to pick up R or try to pick up. There's lots of other skills that you could be picking up. And I feel like only having four skills on resume is just kind of sad to look at. Again, I am not trying to destroy your resume in any way. I'm just trying to be honest. It makes me just kind of sad that there are more skills on there after 10 years of employment. Being an analyst and being an inventory analyst and a BI reporting developer, I just, that's what I think. Let's go on to the experience really quick. So we have BI reporting developer slash inventory analyst has been working there for six years. Really quick, just something that's jumping out of me is we have some quantifiable stuff right here. So I want to really look at this just really quickly reduced 50% of labor cost and 30% of count time of annual inventory count by developing a Python programmed data capturing application with barcode scanners, which replace the manual paper and pen process. Whoa, that is fantastic. Just reading that is like, that's impressive. I mean, I don't know how to do barcode scanning stuff. But if I read that, and I was like, well, this guy knows how to either he's really creative or is really inventive or he's a problem solver. That's really cool. That's a really interesting thing to put on a resume or job, you know, like your job description. Then there's an inventory inventory control coordinator. And this looks like kind of a management position. And then before that, an operations inventory analyst, logistic planner. And so obviously the highlight is on this first one, because that definitely has the most relevance. Development manage over 200 SSRS reports with Microsoft report builder and SQL servers. And I'm going to read the middle one because there's only one left though I want to read it reduce time needed to plan for cycle count schedules improvement from an average of three hours of planning to only 30 minutes by using Excel and Python periodically analyze sales data and classifying inventory. Oh, this is getting too long. Look, keep it simple. It needs to be like one sentence. It should not take up four rows. It was just a lot to read. They call it a wall of words. Wow. Because it was just it was long. It was too much to read. Of course, if I had a ton of time and I was really invested in your resume as a hiring manager or somebody, they might read every single word. But, you know, the glance factor on this one is not solid. Just for this section for other sections, it's fine. But overall good experience. It looks to have a good some good really good information. I really liked that first one. Although it was a little bit long. It's still told a really good important thing to know. Definitely a problem software, which is great to great to have. So overall, not bad at all. I would just reduce these in length a little bit, but a pretty good pretty good job description and good experience. Let's move on to the education education. Simon Fraser University statistics and mathematics of bachelors. And that's awesome. And then British Columbia Institute of Technology business diploma operations management. So you went first got the kind of more, I would consider more technical statistics and mathematics background and went back for the management. So I think that's how, you know, that coincides with some of his management experience. Really good stuff. I wouldn't change the thing. Education looks totally fine. Um, overall just the resume part. I personally would change the format of this entire resume to make it more easily readable, more clean, similar to the last one that we looked at. I just prefer those formats better because they're just when you are reading a lot of these and, you know, they come in like this and then, you know, there's different. How do I say this? It doesn't look as professional as those, the ones that we looked at last one. It doesn't look as professional. It doesn't look as clean. It looks kind of outdated is how I would say it. It looks a little outdated. Okay. So let's, and before we, before we move on, again, this is anonymous. So I'm, I'm just being completely honest. I'm not trying to hurt whoever's resume this is. I know who's resume this, but I'm not trying to hurt your feelings. I'm trying to be as honest as I possibly can be. So I hope you know that. I care about you. Um, but, you know, if something's off, I want to, I want you to know it. I'm trying not to do that in a hurtful way. Let's look at this SQL script because he provided, he or she provided this SQL sample and he included some notes in it. Um, but I'm not going to read that's a lot of notes, but it just says one of the first SQL script such reports that I developed as an inventory analyst. My question is, why would you include one of the first scripts you wrote as an inventory analyst? Why wouldn't you do one of the, you know, last scripts that you wrote that's much more impressive, much more clean, much more, I don't know. And maybe I'm wrong. Let's take a look at it. Uh, I don't know. I wouldn't be, I wouldn't show anybody my first scripts. They were terrible. Just absolutely awful. I would show people my really good scripts that I write now. Um, okay. I'm just, I'm just skimming it really quick before I kind of start giving feedback. So there's nothing, there's nothing really wrong with this and I don't have a problem with it. Um, there's not much, maybe it's up here and I'm just not reading it. There's not much explanation to what's going on. Um, what this data is, what these tables are. Um, I can, I, it really does look like he knows what he's doing. Um, the format is kind of funky in my, from, from, you know, it's just like, maybe this is how to develop. Oops, what am I doing? You know, maybe it's just how developers do things where I have like this huge space right here. Uh, I don't work with anybody who writes like that, but, um, it's very possible that that's just like a commonplace thing. Overall, he's doing a lot of good stuff using things like get date, case statements, um, joins, trimming row number, um, window functions, different types of joins, sub queries. I mean, there are lots of good things in here. So overall, I would, I don't, I would include this. I don't think there's anything wrong with it. I think there's just a lot going on and it's not formatted in like a super easily readable way. That's what I think is bothering me is because the format is just kind of funky and I don't, I don't know how to exactly say that, but like, when I look at this, this is not how I would write a case statement. It just, it's just not how I write a case statement. So, uh, overall though, I like it. I would keep it. I would just maybe even clean it up a little bit, organize it a little bit differently, but you may be writing it exactly how you want it and this is perfect to you. Totally fine. That's just, I have preferences. You have preferences. We all have preferences. Uh, so overall, not a bad resume. I think between these two, I preferred the last resume more. I like that one a little bit more. I think the skill section looked better. It looks cleaner, had more skills. Um, I'm not trying to compare. No, nobody does. He's, this person isn't worse than the other person. Just the resume, I think could use a little bit of updating. Um, anyways, I'm not going to harp on that any longer than I have to get a Gmail. Let's move on to the next one. Uh, and see what that one looks like. All right. So let's jump into this resume at the very top. The first thing that I'm noticing is that it is very barren. Um, it has the first name, the last name, and then just one email. Um, I would provide a little bit more information than this. I provide a location because if you are applying to somewhere and they don't know what your location, you could be from across the country for all they know. Um, but if you're a local, they might prioritize you over somebody else. Uh, and so I highly recommend, you don't have to put, you know, one, two, three, here's my address. You can just put, uh, Dallas, Texas. Uh, that's what I have on mind. And so I recommend putting some type of identifying location, um, on there. I also would recommend putting either your LinkedIn or some type of portfolio or website, something that they can go and look up if they choose to. And then, of course, um, if you want to include your phone number, uh, I recommend that as well. I just feel like there needs to be more up here. It's super barren right now. Um, there's not much, not much on there. I'll give you one second. Um, so, all right, I'm back. So the additional skills, um, additional skills. Is there another skill section? Uh, so I don't think these are additional skills. I think these are just your skills. Uh, so I'm not sure why they're called additional skills. It also feels, uh, it just feels weird not having, because every other one had like, uh, a summary. Yours has no summary. I don't have a problem with that. I think the summary section of a resume is kind of normally redundant. You're just repeating things out in your skills, in your experience anyways, or in your education. So I don't have a problem with it not being on there. Um, personally, I've thought about taking mine off because I feel like it makes no difference. But, uh, it just feels weird now looking at those past two resumes. So let's, let's forget about everything that I'm saying. Let's look at the additional skills. Again, I don't know why it's called additional skills. Uh, those are kind of, those are your skills. Those are your main skills. So I just might call it skill section, uh, and just get rid of additional. So you have Python and SQL, Excel, SPSS, and Amos. I don't know why Python is, is grouped right here with SQL. Um, and I don't know why this is grouped either. Why not put, you know, Python and SQL and Excel on the same line if you're gonna do it that way. Um, I feel like there's a lot more that can be said and shown in this skill section rather than just putting Python and SQL. Um, like I said in one of the previous ones for Python, I don't know what you know in Python. Uh, I really just don't. Python is so broad. So if you can specify, you're using NumPy or using Map.lib, etc, etc. I would put that in parentheses and specify that because right now I just know that you know what that is. Um, and maybe down here you'll, you'll, you'll tell me later. Um, but as of right now, I have no idea. And that's your first thing you're telling me. This is my skill section. These are the things I know. Um, you know, uh, that's something I would work on. I don't know if you guys have noticed, but there's a weird font going on. It's called Georgia apparently. Yeah, I, I say keep it simple. This font, this font is like really weird. It's like it, it feels completely normal, but compared to the last ones, which were like normals, like times, times new Roman and what's the other normal one, this one just feels really weird. Um, you know, in, in general, I, I just recommend keeping it as standard and as normal as you can. Some people like to do, go crazy out there and do different fonts and add their picture and do all these things. I don't recommend doing those things. I feel like most people in this profession, unless you're doing maybe like marketing analytics or something where you can showcase your, yourself in a different way and be creative with it. Um, but, but I in at least my line of work or, um, in my domain, that's not really something that people do. So I'd recommend keeping it super professional, the regular stuff. Um, you guys might find that boring. I just think it's smart. Um, so that's my feedback on the skill section in the font. So weird font to me. Um, here's relevant experience. I'm gonna skim this really quick. Uh, okay. Project leader, project leader, researcher, researcher. Let me go back to the very first job. I'm getting, I'm getting kind of confused at what this person does or what this person's like background is. Okay. So there's a Soul Pine International Restaurant Project. Collaborate with group members to ensure it is you. This is like a school project. Analyze data using linear regression to determine relationship with the data. Launch a new pathway service. Increase social limit. So I can't tell, I can't tell if this is a project and it says project on here. I think this might have just been like a school project, project leader. This may have just been like a project that they did in school, but it's really hard to tell. It says relevant experience. And then this one is a researcher and researcher. And I'm, I'm just reading some of these things because I'm, I'm genuinely confused at what I'm looking at. Developed. So the very first one says consumer research in restaurants during COVID-19 development online survey to measure consumers' perception, information seeking process based on theoretical models. Okay. Here's my, here's my thoughts on this. I'm really confused because it says relevant experience. You're saying project leader. I'm guessing this is a school project. Let me see what, when they were in school. Yeah. So maybe this is like the first year of their undergrad. It's very possible. Here's my feedback on it. The relevant experience and maybe it's just how I'm reading it. It doesn't seem like, it seems like the way you're, I guess, portraying or saying these things is really confusing. I would be breaking this up into two different sections. The first two, which look like actual jobs, which are as a researcher and a researcher, that would be my job experience. Whereas the projects could go in a project section because right now, maybe, and everyone watching this may make things completely normal. I'm just, I'm confused by the project section. And so, so yeah, so that would, that would be my biggest feedback would be separate these and make it more clear on what these are. You have some good stuff. I mean, you're talking about, you know, doing some modeling, you know, you're doing some online survey to measure consumerist perception. I mean, these are all good stuff in, you know, predictive segmentation. Like this stuff sounds really good. It's just hard to really understand the context and how you're, what you're using it for and what you're doing. It's hard to give feedback on it just because it's kind of vague. I don't really understand everything that you're doing in your position or what your job entails. I don't know what kind of tools you're using or anything. My recommendation would just be more specific. Be more specific in your job. I feel like you're, you are saying some good stuff. It's just, I don't understand how it applies to your position, what impact you had, those types of things. And so, and there's no, there's no type of quantitative information. Like I keep saying that word, but it's just numbers. I'm not saying any numbers to quantify the kind of work that you've done and the impact that you've had in your job. I feel like I said that really so fast, but I'm going to go to the next section because I don't want to keep harping on this. And then there's education, bachelors of food service management in South Korea, very cool, masters in food service management. So you're definitely in the food industry. I can tell you that, you know, how you know these things or worked on these things or why you're using these things. I kind of have an idea. It's just hard to tell. It really is hard to tell how you're trying to use your degree with these tools and you don't have any of the tools within your job description. Like how are you using Python? How are you using SQL? How are you using Excel? You can specify that in your job description so I can understand how you're using those things better because maybe you are using a bunch of Python for like this predictive segmentation. Maybe you aren't doing that. I just don't know. So yeah, so big takeaways from this resume for me is be much more specific for your skills with parentheses and adding those sub-skills. Be more specific in or separate those out those two columns or two areas for job experience and then projects. And then be more specific in what you're actually doing and the impact that you're having. That is for this resume. That would be my biggest feedback. And then the fonts. The fonts as well. I would personally just keep it standard and traditional. That's just me though. So that is this resume. So that is all the resumes that we're going to be looking at today. I hope that I wasn't too harsh on this one. I feel like in previous videos where I've done reviews on people's resumes, I was actually too, I guess, gentle. I didn't really speak my mind 100%. Whereas today I felt like I spoke my mind. If I didn't like something, I wanted you to know it and know why. So I tried maybe I tried a little bit too aggressive. We'll see. We'll see what you guys think. But honestly, I was just trying to be really honest. And these were all anonymous. And so I hope that I didn't hurt anybody's feelings. I was not trying to do that in the slightest. I am just trying to give you guys a glimpse into what I think of and what I'm trying to do. And when I review a resume, what I'm looking for. And so that when there's extra stuff or things are said in a certain way or there's certain fonts, I want you to know what I think of them. Take everything that I'm saying with, you know, just a grain of salt. I am just one person. There are many people that may disagree with me or see things in a different way. That's totally fine. I just hope that this video benefits you in some way that you go back to your resume and maybe make some updates or some changes that improves it and gives you a better chance at landing a job. Thank you guys so much for watching. I really appreciate it. If you liked this video, be sure to like and subscribe below and I will see you in the next video.