CVs - an optimal approach...

[DaveB]

I think you'll find that, in fact, pimps and Clients like my approach much better. I win.

Yes, but threatening to exterminate them if you don't get the gig doesn't really work for me

[Bob Dalek]

Yes, but threatening to exterminate them if you don't get the gig doesn't really work for me

It can help close a deal!

[TimberWolf]

Here's what you need on your CV:
Name at the top. (Never put "CV" or "Resume" on your CV - it's just crap to do so).
Sexy & snappy description (profile) of what you do and why you are a god.
Examples of how you have saved planet Earth on a few occasions.
Work history. Bullet points of Problem & how you fixed it. Include any meaningful pats on the back you received. Use the past tense, and stick to it. Don't use "I", and NEVER, EVER "we". Play the Team-Spirited-Yet-Capable-Of-Working-On-Own-Initiative card.
Qualifications, if relevant.
Do not mention your bronze swimming badge award - always looks a bit silly.

Hmm, interesting tips. How do you go about not using 'I' in a CV? Mine is probably littered with them.

[Bob Dalek]

Hmm, interesting tips. How do you go about not using 'I' in a CV? Mine is probably littered with them.

"Investigated and fixed poorly performing SQL by analyzing Wait Events and the Shared Pool. Discovered non-reusable SQL that had led to Library Cache Latch contention. Rewrote the offending SQL to use bind variables. Resulted in faster execution times, allowed the Shared Pool to be resized, thus freeing-up server memory and reduced CPU utilization."

Basically, punchy, past tense and no him, he, I, we, etc.

[TimberWolf]

"Investigated and fixed poorly performing SQL by analyzing Wait Events and the Shared Pool. Discovered non-reusable SQL that had led to Library Cache Latch contention. Rewrote the offending SQL to use bind variables. Resulted in faster execution times, allowed the Shared Pool to be resized, thus freeing-up server memory and reduced CPU utilization."

Basically, punchy, past tense and no him, he, I, we, etc.

I see what you mean. I might have written <shoot, I've used too many I's already>: "This resulted in faster execution times, allowing the Shared Pool to be resized"

'This' and 'allowing', being present tense and hence leaving one open to a nasty case of switching tense. I may be inadvertently switching tense quite a bit, so yeah it might be something to be wary of.

[malvolio]

To summarise, based on my own CV and what I look for in others'...

1. What do you do
2. What have you achieved
3. Who did you do it for and when
4. What else have you done
5. How can I contact you.

It helps greatly of (1) above directly relates to the job in question; that way it gets past not only the agent but also the Human Remains drone who will be filtering the applicants.

Only other parameters are a) precise and accurate grammar and spelling, b) nothing over five years ago has much relevance c) use Word, 11 point Arial and d) stop at three pages or I stop reading.

HTH

[Bob Dalek]

I see what you mean. I might have written <shoot, I've used too many I's already>: "This resulted in faster execution times, allowing the Shared Pool to be resized"

'This' and 'allowing', being present tense and hence leaving one open to a nasty case of switching tense. I may be inadvertently switching tense quite a bit, so yeah it might be something to be wary of.

Best way: write it in any old tense mix. Then review and correct. Leave it a day or two, then review and fix. I review my CV once a month, at the least. Always have it ready to use and up to date. Fiddling with one's CV when a job goes pop! is not "a good thing".

[donny]

It's NOT a CV - it's a promotional guide to the services your company offers!

Denny

[SandyDown]

It's NOT a CV - it's a promotional guide to the services your company offers!

Denny

Denny is that you ??

[EternalOptimist]

Denny is that you ??

give her time, she'll be back as dunny