You Are What We See: A Guide to Relevant Resume Information in Your Job Hunt
The most common message in my inbox, PMs, and DMs is something to the effect of: “I was declined for this role, even though I know I’m a perfect fit. Why?” If you’re wondering why you haven’t been moved forward for an interview, the answer might lie in what recruiters do not see in your resume, application, and/or Gun.io profile.
For all the minutes that you put into updating your work experience, know that you have seconds, and repeat: seconds!!, to make a good impression. Hiring managers look to see your potential within 6-8 seconds. If the relevant information isn’t there and visible immediately, no one will care about the rest of your application. Make those minutes you spend applying count.
If you’re on the job hunt, know that I’m rooting for you! So I’m going to drop a few pointers.
The Job Criteria
When a new role is posted, what should you look for? I always recommend that folks carefully read a job description. Understand not only the minimum requirements but also what a company is actually solving for, what it does, and how that aligns with their interests and background.
I’ve seen a lot of applicants see a role title and tech stack in the header and call it a day. The danger to that approach is well… we can tell. Almost every engineer applying is going to have experience with the main required tech stack – all will be a technically good fit. What we, hiring managers, clients, etc. are going to look for goes beyond that. Understand how your previous work can be applied to this new role and update an application accordingly. The nice-to-have skills, the industry experience, the environments you’ve been a part of will end up what makes someone the best fit.
Focus on Relevant Information
Cut the fluff. Seriously. Prioritizing relevant information demonstrates that you are strategic and intentional about how you present yourself. It shows that you understand the importance of aligning your personal narrative with the job’s requirements and there’s true interest in the job and/or company itself. Here’s what to focus on:
- Role-Specific Overview: In your application overview, directly address the role’s expectations and requirements. Think of it as an elevator pitch where you have the luxury of time to craft a clear, compelling narrative about why you’re a perfect fit.
- Avoiding Information Overload: Be Concise but impactful. Avoid lengthy paragraphs and irrelevant information. Including every detail about your work history or skills can overwhelm or distract from understanding your work. Margin-to-margin 9pt font? Sorry, most hiring managers are not going to read every word. Focus on what directly contributes to your ability to perform the role you’re applying for; this allows anyone hiring to know your background without sifting through less pertinent details.
The Importance of Specifics
I’ve talked about the Power of Specifics before, but I don’t know that it can ever be stressed enough. Work experience entries with vague one-line overviews…c’mon, y’all…not going to cut it. Open roles are inundated with applications, and applicants get sorted quickly to find the ones that stand out (must I repeat: seconds!!). To improve your chances, focus on the specifics that align directly with the job you’re applying for. Here’s why being specific matters:
- Tailored Work History and Cover Letters: Your work history and cover letter should not be one-size-fits-all. Customize them for each position by incorporating keywords and phrases from the job description and your demonstrated experience in those areas. If the job requires experience with a specific software or skill, make sure that’s prominently featured in previous work.
- Clear and Direct Language: Use straightforward language that clearly conveys your skills and experiences. Avoid jargon or complex language that might obscure your message. Not everyone looking at your work application will be technical.
- Quantifiable Achievements: Rather than simply listing responsibilities from previous roles (and let’s be honest, there’s a lot of general overlap), highlight your accomplishments with quantifiable data. Instead of saying “managed a team,” say “managed a team of 10, increasing productivity by 20% within six months.”
Getting Feedback
Easier said than done, but if your applications are not moving forward, don’t be discouraged. Request feedback where you can. Sometimes, feedback can provide valuable insights and you can use it constructively to refine your approach.
If you want some extra eyes, reach out in the Gun.io community. We’ll be happy to help!
