Weekly thread for any and all career, learning and general guidance questions. Thinking of taking a training or going for a cert? Wondering how to level up your career? Wondering what NOT to do? Got other questions? This is the time and place to ask!
What do you guys think about a projects section on a resume instead of a skills section for someone early in their career? The idea would be instead of just listing Python & Nessus you could list something like “Used Python to start a scan against a target system with Nessus API”.
That is generally what I’d recommend, and have liked seeing in a resume.
My thinking is that seeing projects tends to showcase not just a particular skill like with a language you used, but shows an understanding of the problems facing some area that your project is trying to solve. I’ve never really been a fan of skills listings just because they offer basically no context. Whereas projects give me something to bounce off of in an interview, and hopefully get the candidate talking.
I will say though that I wasn’t the person reviewing resumes deciding who got an interview, I’ve just been an interviewer after someone made it through the screening.
I am by no means a hiring manager. However software engineering is project based work , so I would be biased towards this as a good thing
I think you would want to have both. Have a summarized section where you list skills you have still but if there’s something notable you know how to do, such as programmatically control Nessus using Python (as you have suggested), I think it’s worth making the connection in a separate section.