A couple of things that were very successful on my resume last year:
Summarize the "good parts version" right at the top. I have a list of 5 or 6 items I'm most proud of as a DBA right below the contact data. Like "Articles published on SQL Server Central", that kind of thing.
Right below that, the things I do and don't do, and how good I am at the ones I do. Nobody wants to dig through your resume to figure out if you have ever worked with SSIS (for example), so list the basic features of SQL Server and whether you know them or not.
Sample (not my skillset, just made these up for an example):
T-SQL: Good (Moderately complex queries)
MDX: Excellent (high complexity queries)
SSIS: No experience
SSRS: Excellent (over 150 custom reports built this year)
SSAS: Excellent (10 years experience)
OLTP Architecture: Okay (some experience)
OLAP Architecture: Excellent (10 years)
OLTP Performance Tuning: No experience
OLAP Performance Tuning: Excellent
.NET: No experience
Something like that, with just those points, modified to match your experience and training, makes it very easy for a manager to see exactly what you bring to the table. Modify it to highlight the points most relevant to the job you're applying for
Follow that with your detailed work/education history, as usual.
Keep in mind that what the human eye sees and the mind judges first is the top 1/4 of the front page and the bottom 1/4 of the front page. Grab attention in those two, and they'll read the rest. Lose attention in those two, the rest will never be read.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon