Hi Josh, This is Michael from the SANS Mailing list. Interesting post as usual. Could I send you a copy of my résumé for you to have a look at and share your thoughts. Regards, Mchael
Sent from my iPad On Jan 31, 2013, at 9:58 AM, Josh More <[email protected]> wrote: > A resume won't get you a job. You can certainly put some focus there, but you > need to consider it "necessary but not sufficient". It is a story-telling > tool. The stories you tell get you the job, the tool, by itself, does > nothing. > > I've written up my process here: > http://www.starmind.org/2012/04/07/so-you-want-a-new-job-adapted-from-a-presentation/ > , and the book based on this should be coming out this summer/fall. (Not > entirely certain about the schedule quite yet.) > > Your questions are sorta answered in the resume section in the link above, > but to keep things in the thread... > > 1) By all means, list community involvement. However, do so in a way that > optimizes for search engines and HR filters, but does not provide a wall of > acronyms that make people glaze over. This can be hard and involve a lot of > parentheses. > > 2) List conferences if you have nothing else to put in an education section. > The more active you've been, the better. > > 3) Experience matters the most. Then lab experience. Then degrees. Then > certifications. Aside from the resume header, which should show all pertinent > information in the top four centimeters, everything should be sorted by this > priority. > > 4) Follow the two page rule unless you're a consultant. Then aim for 10. > It's stupid, but the consulting world is heavily tilted in favor of project > exposure and long resumes make people look better. The employee world is the > exact opposite. > > But really, even with the perfect resume, a bit of story-telling skill and > being able to work the process to your advantage is going to be far more > effective. > > -Josh More > > > > > On Wed, Jan 30, 2013 at 10:17 AM, Bacon Zombie <[email protected]> wrote: >> Hi All, >> >> I'm looking to move from Network/System Admin role into pure Security >> and in the middle of updating my CV. >> >> I would like to see if the hive mind has any opinion on what should >> and should not go into a CV and should a CV for a Security Job be >> different from a standard Tech CV. >> >> Soon difference that come to mind are: >> >> #> Do you list conferences you have attended and if so what section do >> you list them under or do they deserve there own section. >> >> #> Do you list projects and CTF. >> >> #> Do you list that you are a member of your Hackerspace, DC or 2600 >> group and what do you put it under. >> >> #> Do you follow the no more then 2 or 3 pages rule or has that >> changes now since most people will read your CV via TXT/PDF/DOCX and >> not a printout. >> >> What are some thing really should include and also really should not >> include on my CV. >> >> Thanks in advance, >> >> P.S : Just realised CV may not be a common term for all; CV = >> Curriculum Vitae or Résumé. >> >> -- >> >> BaconZombie >> >> LOAD "*",8,1 >> _______________________________________________ >> Pauldotcom mailing list >> [email protected] >> http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom >> Main Web Site: http://pauldotcom.com > > _______________________________________________ > Pauldotcom mailing list > [email protected] > http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom > Main Web Site: http://pauldotcom.com
_______________________________________________ Pauldotcom mailing list [email protected] http://mail.pauldotcom.com/cgi-bin/mailman/listinfo/pauldotcom Main Web Site: http://pauldotcom.com
