Building your resume updates

getting_hired/applying_and_interviewing/project_resume.md

@@ -1,22 +1,41 @@
 ### Introduction
 
-The goal of a resume is to get them interested enough to start a conversation.  From there, it's on you to speak intelligently about the things you've done. So don't treat the resume as the catch-all repository of your whole life -- it's more of a focused marketing tool designed to make you seem worth taking another look at.
+The goal of a resume is to show the recruiter/hiring manager that you meet the minimum qualifications for the role in which you are applying for. From there, it's on you to speak intelligently and confidently about the things you've done. So don't treat the resume as the catch-all repository of your whole life -- it's more a document that gives the recruiter/hiring manager confidence that you meet the qualifications for the role that they are hiring for.
 
-A developer's resume is an interesting thing because so much of your value is demonstrated from your projects, which live in your GitHub (and are hopefully also deployed somewhere online).  Despite this focus on projects, you can't ignore previous work experience or education.  They are both important for showing the social proof that other people have worked with you before and you've met their standards for applying.  
+### Research And Creating A Plan
 
-It's difficult to come up with (or find on the internet) a standard resume type for a junior developer.  Most of the ones out there aren't particularly inspiring.  The keys to remember are the perspective of the hiring manager we talked about before -- that person wants to hire a developer who is highly capable and can get shit done (and will add value ASAP).  
+Before you begin writing all of your achievements and projects down, we strongly encourage you look around on LinkedIn or Glassdoor and see what some of the keywords are for the position you're interested in. These keywords or buzzwords as they sometimes are referred to are what recruiters and hiring managers will be looking for, the catch here is that you shouldn't just litter your resume with keywords. You need to place them in areas where they make sense, you also need to avoid repeating the same keywords in multiple bullet points. Your goal is to try and get between 60-70% of the keywords seen by the recruiter/hiring manager within 20 seconds.
 
-The hiring manager will determine these criteria in less than 10 seconds at first glance based on where you've been educated, who's hired you before, and if you've got any really interesting projects that stand out.  The hiring manager rapidly builds a story of who you are based on those headline items of your resume.  If you're lucky, that high level story will seem interesting enough for the hiring manager or HR person to look twice and actually read what you did at each job and then bring you in for an interview.
+As an example if you are applying for a frontend developer position you will likely see keywords like `HTML, CSS, JavaScript, React, APIs etc.`. So when writing out your bullet points you should keep this in mind. Having something that reads like: `Crafted a responsive Weather App using HTML and CSS that connected to external RESTful APIs using JavaScript to give real time weather information to the end user.` When the recruiter/hiring manager is looking over your resume they will be able to pick out those keywords quickly, then if they come back to make sure you didn't just put down some keywords they will see the what, why, and how you were able to build something with that technology.
 
-Knowing that perspective, how can you play to it?  It's difficult if you're breaking into a new industry so you'll need to emphasize relevant education, work experience and projects in a way that crafts a story of drive and capability.  What have you done that shows you're highly capable (e.g. your technical chops, any recognition you've received, leadership of teams)? And can get shit done (e.g. interesting projects, open source contributions)?
+Recently a trend has emerged where skill sections are used everywhere, either on GitHub pages, Resumes, portfolios, etc. While these may seem useful in the moment, they are anything but. From a hiring manager or a recruiters perspective they are all but useless, they want to know whether you actually understand the technologies listed.
 
-Remember: ONE PAGE.
+### Resume Building Tips
 
-- This Career Tool Belt article lists [6 free resume builder websites](https://web.archive.org/web/20230930114027/https://www.careertoolbelt.com/5-best-free-resume-builder-websites/)
-- [Novorésumé also has a free tier with templates available, as an alternate resource](https://novoresume.com/)
-- Formatting could use some work, but here’s an [example resume from CareerCup.com](https://www.gayle.com/resume)
-- [Another great (totally free) resume builder](https://flowcv.io/)
+When crafting your resume you will likely be going through different iterations. You may also be crafting multiple resumes to send out to different positions, for example like we discussed earlier, you may have a resume that is tailored and using keywords that focus more on a frontend position. Another that uses keywords, projects, and other information that is more backend focused. There is nothing wrong with having different resumes for different positions, it helps the hiring manager/recruiter to quickly identify the keywords that align with that position which will give you a higher chance of being successful in your job search. Another thing to keep in mind is that your resume is not supposed to win any sort of awards. Its purpose is to tell the recruiter or hiring manager that you are qualified for the position in which you are applying and to hopefully give them the confidence that you can come in and hit the ground running instead of holding yourself and the company back from progressing.
 
-### Optional reading
+One misconception is that you need to keep your resume one page, while in most scenarios it's easier to read and visually more appealing to have a one page resume it's not the end of the world if you have to go past one page. Just know that most recruiters or hiring managers may not make it to your second page. So keep as many of the relevant keywords, experience, education, and projects near the top of the first page.
+
+Within the assignment section we linked to a great resume guide written from an active recruiter who has years of experience on what other recruiters and hiring managers are personally looking for when they review a resume. Use it and apply it, you've worked this hard to get this far don't sell yourself short by using a lazy resume.
+
+### Do Not Get Discouraged
+
+The hiring manager will determine if you meet the minimum qualifications of the job listing in less than 20 seconds. At first glance, they will look for your education level if you have one, who's hired you before, and if you've got any really interesting projects that stand out.  The hiring manager rapidly builds a checklist to see if you meet the qualifications of the job listing you've applied for. If you managed to meet those minimum requirements along with some other factors you may receive a call to continue forward in the hiring process. Do not be discouraged if you don't however, there are multiple factors to account for when it comes to whether or not you are selected to move on or not. The best thing to keep in mind is that you continue to grow and build projects and try and gain any relevant experience in the position you're applying for. Remember to keep looking at those keywords and see where you are lacking and then go out and learn and build projects using those technologies.
+
+Knowing that perspective, how can you play to it?  It's difficult if you're breaking into a new industry so you'll need to emphasize relevant education, work experience and projects in a way that crafts a story of drive and capability.  What have you done that shows you're highly capable (e.g., your technical chops, any recognition you've received, leadership of teams)? And can get shit done (e.g. interesting projects, open source contributions)?
+
+### Assignment
+
+<div class="lesson-content__panel" markdown="1">
+
+1. This Resume Guide [Resume Creation Guide](https://static1.squarespace.com/static/655d4d0eee15a6053d4345f2/t/68598b9ff8194a1adc980c45/1750698912277/_How+to+Get+a+Job+by+Lee+the+Headless+Headhunter.pdf) was created by an active recruiter with the intention of avoiding common resume mistakes made in today's market.
+1. This Career Tool Belt article lists [6 free resume builder websites](https://web.archive.org/web/20230930114027/https://www.careertoolbelt.com/5-best-free-resume-builder-websites/)
+1. [Novorésumé also has a free tier with templates available, as an alternate resource](https://novoresume.com/)
+1. Formatting could use some work, but here’s an [example resume from CareerCup.com](https://www.gayle.com/resume)
+1. [Another great (totally free) resume builder](https://flowcv.io/)
+
+</div>
+
+#### Optional reading
 
 - [Getting Your Résumé Read, by Joel Spolsky](http://www.joelonsoftware.com/articles/ResumeRead.html)