One nit from a perspective of a SWE is that I wouldn’t quantify your coding experience in terms of lines of code written. More lines of code does not equate to more experience and is often a con for organizations as it just means more lines of code to maintain. Quantifying impact in terms of lines of code written is something that makes your resume read like that of a novice to me. Maybe here is an opportunity to reframe your experience in terms of projects. How many projects did this code span? This could’ve then read: Supported xyz projects by writing code, designing unit tests, and fixing bugs in Python. Improved the maintainability of the codebase by creating additional documentation on these projects. If there aren’t many projects, you can enumerate the objectives of the code you wrote.
There was some great information by the recruiter and sounds like the nightmare I currently live: I keep getting interviews for the job I want to get into (Systems Administration) but haven't gotten over the finish line. At least she illuminated how recruiters might think (Good resume, poor fit) when they select you for an interview anyway.
Can we have a résumé example that has specific product and analytics product marketing working on the actual product because I see where she said it’s your résumé is more related to proficiency and teams and not working on the product so what would a résumé look like read as someone who worked directly on a product or to be digital or physicaland can you please have the recruiter in the video for this idea?
One nit from a perspective of a SWE is that I wouldn’t quantify your coding experience in terms of lines of code written. More lines of code does not equate to more experience and is often a con for organizations as it just means more lines of code to maintain. Quantifying impact in terms of lines of code written is something that makes your resume read like that of a novice to me.
Maybe here is an opportunity to reframe your experience in terms of projects. How many projects did this code span? This could’ve then read: Supported xyz projects by writing code, designing unit tests, and fixing bugs in Python. Improved the maintainability of the codebase by creating additional documentation on these projects.
If there aren’t many projects, you can enumerate the objectives of the code you wrote.
This is a fantastic suggestion - thank you! The rest of the internet agrees with you that one should NEVER put lines of code produced in your resume
This was REAL and RAW 🔥 Thank You for transparency 🙏🏽💕
There was some great information by the recruiter and sounds like the nightmare I currently live: I keep getting interviews for the job I want to get into (Systems Administration) but haven't gotten over the finish line. At least she illuminated how recruiters might think (Good resume, poor fit) when they select you for an interview anyway.
So helpful! Thanks for sharing 😊
Can we have a résumé example that has specific product and analytics product marketing working on the actual product because I see where she said it’s your résumé is more related to proficiency and teams and not working on the product so what would a résumé look like read as someone who worked directly on a product or to be digital or physicaland can you please have the recruiter in the video for this idea?