Listening to @spacerog tips on writing the perfect resume for those starting out in #infosec. Just experiences based on an internship program he and a co-worker started several years back. (Note: Spacerog is NOT an HR person 😉.) [I added a few comments in brackets.] #ShmooCon
@spacerog Here are his DON’Ts…
- Don’t list all the individual classes you took (see DO’s below)
- Don’t go over 2 pages (1 if possible).
- Don’t list references (takes up too much space and he knows he can always ask you for reference later if needed). #shmoocon
@spacerog
- Don’t listen to your professors (When was the last time they’ve written a resume or reviewed ones to hire someone?) [Those professors are ok I guess. 😉]
- Don’t follow your school’s suggested resume format. [Yeah, it’s a good place to start but MAKE IT YOUR’S — not you school’s. :)] #shmoocon
@spacerog
- Don’t be a graphic designer … nothing fancy (ex., no animated GIFs, fancy colored fonts, etc. as well as no photos - you’re not applying to be a model).
- And just some general ones about not listing fraternities/sororities or including a cover letter (don’t not enough time for a reviewer to read them all). #shmoocon
@spacerog
And now for the DOs…
- List the projects you did in your classes.
- List any job experiences (put down at least something - even if it’s babysitting)
- Properly format your resume (just don’t go overboard like mentioned in DON’Ts)
- List any hacking competitions (CyberPatriot, CCDC, etc.).
- List bug bounties you’ve participated in
- List volunteer work (no long explanation; wants to see a well rounded person)
- List any involvement in any infosec cons
- List military service
- Other things like your GitHub repo, etc. #shmoocon
@grecs @spacerog that final post with the Do's in particular is great. (Source: me, 20+ years of projects as hiring manager)