How to find a good DBA<\/p>\n
You are stupid until proven otherwise<\/p>\n
Creating Job Wrecks (Requirements) – Be reasonable, honest, concise specific<\/p>\n
Reading resumes – look for job hoppers; red flags things that are impossible; look for language that are trying too hard; Beware “experts”<\/strong><\/p>\n After 10+ years – if they are listing things like index tables and other basic things, they are trying too hard – they should be doing a lot more than this.<\/p>\n Expert, Proficient, Master – key words to explore what they claim to be an expert in<\/p>\n Question – How are you continuing your education?<\/p>\n Phone screens – initial litmus; measure communication skills and basic knowledge; decide whether or not to bring them in.<\/p>\n Passive interviewing – less you talking, letting them think they should keep talking; when you are being interviewed you can turn this around.<\/p>\n Interview pre-questions – first impressions; small talk before the actual interview; can be used to trip them up later<\/p>\n Questions –<\/p>\n You can get on a call with 70 users and say anything, but you’d better be right.<\/strong><\/p>\n Before everything else – explain the format<\/p>\n Say the answer and shut up; If you don’t know say you don’t know.<\/p>\n Question types<\/p>\n Labs<\/p>\n Good: Labs incorportated into the interview<\/p>\n Bad: they have to sit in a room and do stuff<\/p>\n Contract-to-hire is your friend!!!<\/p>\n","protected":false},"excerpt":{"rendered":" How to find a good DBA You are stupid until proven otherwise Creating Job Wrecks (Requirements) – Be reasonable, honest, concise specific Reading resumes – look for job hoppers; red flags things that are impossible; look for language that are … Continue reading \n
\n
\n
\n