sql dba resume

Question

Post reply

sql dba resume

Diyas

SSCarpal Tunnel

Points: 4851
More actions
May 17, 2010 at 6:39 am

#224524

hey
i am planning to prepare sql dba resume..i dont know how to prepare it.can any one send sample resumes to my mail divyap01@gmail.com

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

PaulB-TheOneAndOnly SSC Guru Points: 66772 More actions · Answer 1

Do you mean... format or content?

For format... search the web -different cultures do it different.

For content... only you know about your credentials including education and working experience.

Try to keep it short, no more than two pages.

_____________________________________
Pablo (Paul) Berzukov

Author of Understanding Database Administration available at Amazon and other bookstores.

Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.

Steve Jones - SSC Editor SSC Guru Points: 736270 More actions · Answer 2

Build a resume like you would for any job. Focus on your SQL skills.

Here are some hints. http://www.groovejob.com/resources/resumes/tips.html

Jeff Moden SSC Guru Points: 1004363 More actions · Answer 3

The two things that I've found work really well on a resume are...

A properly written objective... leave out the gooey stuff about how well you play with others and how you want a job that will be challenging. A simple list of the things you want to and can do will normally suffice because it's the first attention getter.

The next thing should be a list of accomplishments. What have you done that will put you ahead of the rest and what tools did you use?

Anyone can list a job history... get their attention! Remember... well written Objective and well written List of Accomplishments relative to the trade.

Then... be prepared to backup everything you say on your resume because you WILL be interogated about those things and more. 😉 The worst thing you can do is exaggerate what you've done.

The other thing is... if you make a spelling error, you're dead. A lot of folks won't even consider a person if they find a spelling error. There's really no excuse to have a spelling error on your resume.

--Jeff Moden

RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

Change is inevitable... Change for the better is not.

Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)

LutzM SSC Guru Points: 107049 More actions · Answer 4

Another strong hint: you might want to remove your email address. If people feel the need to provide you with a sample they can drop you a PM...

Lutz
A pessimist is an optimist with experience.

How to get fast answers to your question[/url]
How to post performance related questions[/url]
Links for Tally Table [/url] , Cross Tabs [/url] and Dynamic Cross Tabs [/url], Delimited Split Function[/url]

SQLRNNR SSC Guru Points: 281334 More actions · Answer 5

Jeff Moden (5/17/2010)
The other thing is... if you make a spelling error, you're dead. A lot of folks won't even consider a person if they find a spelling error. There's really no excuse to have a spelling error on your resume.

I would also add that grammar errors are a big knock on resumes.

The other suggestions made so far are the same sorts of things I would recommend.

Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events

DNA_DBA SSCrazy Eights Points: 9117 More actions · Answer 6

We had a load of CVs for a job we advertised. Some just listed the skills they had without any information on where or how they were used (did not get interviewed). Some had pretty much the same description for each job they had been to (did not get interviewed). The best ones list their skills at the top, then show how those skills were used in the jobs they have done - you can then see how they have progressed and if the skill listed ties in with the jobs they have performed. Don't put things on your CV just because they sound good - you'll get caught out in the interview!

barsuk SSChampion Points: 12280 More actions · Answer 7

Hate to say, but did you try to google it: sql server dba resume