Resume Critique

Blade3D

I'm currently trying to brush up my resume, I've been applying for a few jobs but not seriously looking yet. I am planning on obtaining the CISSP early next year as I hit my 4 year mark in May.

I'm still in my first professional job, but I am looking to pivot into something else. Based on my experience and certs (assuming I obtain the CISSP), what jobs could I realistically get?

I've been applying for positions like Data Security Analyst, Network Security Analyst, IT Security Analyst, Information Security Analyst, etc.

Dice.com estimates my pay at like $83k which I think is ridiculous, I don't get paid anywhere near that. However, if it's even 75-80% of that I definitely need to pursue other options.

Please leave any positive feedback or constructive criticism. Thanks

cyberguypr

- I personally do not care for this format
- "targetting IT positions" sound to me like "i don't care what it is, i'll take anything IT related". I would rebuild this session as a profesisonal summary
- Too many bullets. Experience should be a paragraph of duties followed by 2-3 bullets with KEY accomplishments. Right now I don't see anything that screams "wow, this sguy has something to bring to the table". Agian, this is due to lack of specificity. As a hiring manager I don't care that you deigned A system, network or infrastructure. I care about which specific system you designed and what business problem it helped address.

Remember two things:
- It's about standing out and showing how you bring value
- Always customize resume to the particular position you are applying. If I see a generic resume that makes me decipher how it applies to the position I have open, I lose interest really quick.

Blade3D

Thanks, that's definitely helpful, I wasn't really sure what to do. I was considering changing that top part to an executive summary, I'll definitely be making that change now.

So I have a "resume" we use when submitting for RFPs and so forth. Should I be grabbing information from those on the projects I've worked on?

Here is a few examples:

Designer of an automated exit portal at the Terminal Security Checkpoint location to provide security against unauthorized access to the sterile area. Designed the electronic systems associated with the automated exit lane including developing plans indicating system device locations, developing device logic interactions and integration with the Airport’s VoIP Phone System, Access Control System, and Video Surveillance System.

Designer of a new wireless data network to support multiple airport departments to include Operations, Facilities Maintenance, and Public Safety. Conducted wireless surveys of the Airport terminal buildings, support buildings and outdoor areas using Wi-Fi analysis and design software tools. Provided predictive wireless coverage for access point locations.

Designer for the security and communications expansion at the facility. Design work included camera coverage for the added parking area, additional assistance stations, and outdoor paging system. Designed underground communications and electrical conduits and connectivity of the IP-based paging, video surveillance, and access control systems to the existing data network.

Or is that still not specific enough? I just figured that was too much information to list for each one.

CE1028

cyberguypr wrote: »

-
- Too many bullets. Experience should be a paragraph of duties followed by 2-3 bullets with KEY accomplishments. Right now I don't see anything that screams "wow, this sguy has something to bring to the table". Agian, this is due to lack of specificity. As a hiring manager I don't care that you deigned A system, network or infrastructure. I care about which specific system you designed and what business problem it helped address.

Remember two things:
- It's about standing out and showing how you bring value
- Always customize resume to the particular position you are applying. If I see a generic resume that makes me decipher how it applies to the position I have open, I lose interest really quick.

I've been rewriting my resume and I agree with the first part. I like the experience should be a paragraph, followed by a few bullets. It makes more sense to me. I personally haven't figured out the proper wording of that paragraph. Right now, I have a ton of bullets and I hate it


The last point, I don't really get when people say this "Always customize resume to the particular position you are applying". Every time I read a statement like that, I picture people just making up things on their resume.

cyberguypr

As a hiring manager, assume I get two resumes. First one is a guy that does desktop support. He writes how he installs all kinds of stuff and resolves all sort of random problems. The next guy is the same desktop support type, with more or less the same experience. He then decides to highlight how his experience relates to the duties I listed in my posting. No need to make anything up, just pick and choose from your arsenal and show how you can help me solve my puzzle. Guess who has the upper hand? Hint: is not the guy who didn't mention how what he has done translates to what I listed.

If you ever do the workshops that OPM does on how to write your federal resume you will see this is strongly advised. Also, it helps with a candidates biggest and strongest nemesis: resume scanners.

Edit to add that the goal here is to make the job search as efficient as possible and increase your chance of landing an interview. This is why people get degrees, certs, etc. that are not necessarily required for most positions. Heck, I never needed a BS and ended doing it, plus my Masters, and soon to go to a doctorate. It's just about keeping your universe of options wide open.

CE1028

Absolutely, when you put it this way, it makes sense 100%. I've done so many interviews where people have tailored their resume after the job descriptions, but when tested, their responses prove otherwise.

I totally agree with you though.