I used to have a lengthy CV but I dropped it down to only very brief summaries. I don't really have a matrix of skills; more just a on-topic quick review of what I used. Seems more correct to me, but is prone to errors in that you may need to list things that would be trivially obvious to programers.
It's hard to say if it "works", but you can check it out here for comparision to others: < http://www.mirios.com.au:8081/images/c/c0/ProgrammingCV.pdf> On Wed, Mar 9, 2011 at 3:07 PM, Simon Kuldin <[email protected]>wrote: > Hey everyone, > > > > Any advice on the best way to structure a resume for the I.T. industry? > I’ve not needed a resume for a long time so I am a bit rusty J > > > > I do remember having a skills matrix at the beginning is very useful. > > > > > > *Simon Kuldin* | Senior Technical Consultant | *PRISM* > > Suite 3, 214 Bay St Brighton, VIC 3186, Australia > > *P:* +61 3 9596 8633 *M:* 0408 310 957 *W:* www.prism-solutions.com.au > > > > [image: prism-v5.jpg] > > *People. Responsive. Innovative. Simple. Methodical.* > > > -- Noon Silk http://dnoondt.wordpress.com/ (Noon Silk) | http://www.mirios.com.au:8081 > Fancy a quantum lunch? http://www.mirios.com.au:8081/index.php?title=Quantum_Lunch "Every morning when I wake up, I experience an exquisite joy — the joy of being this signature."
<<image001.jpg>>
