patrickmcginnis59 10839 (6/13/2016)
Jeff Moden (6/10/2016)
patrickmcginnis59 10839 (6/10/2016)
Besides, if you have to prepare for an interview, then you're not ready for the job.
Disagree. It never hurts to review the basics even though you know them to ensure you can state them succinctly. I know what ACID is and what the normal forms are, but if I had an upcoming interview, I would review these topics and others to refresh my memory and ensure that if a question hit on these areas I would answer with no hesitation.
Have to add my vote to that. Its good to prepare for the specific interviewer also, like show interest in the company by researching it if possible. If you feel theres a chance of questions in areas you don't routinely work in might want to be at least read up on them. Don't invent experience that doesn't actually exist, but knowing something is always better than not knowing something in my opinion.
ACID, normal forms, isolation modes, declarative versus procedural code, those are always good topics to refresh up on, even if at your previous job your vendors used nolock LOL, heck for that matter study why nolock is a bad idea even if you've never used it. Never know what question you might get right?
But, if you got caught flat footed and had to submit to being interviewed in the next 10 minutes, would you fail the interview just because you didn't have time to prepare for the interview? Probably not and that's what I meant by if you [font="Arial Black"]HAVE [/font]to prepare for the interview.
Its a good idea to prepare for interviews in my opinion. It shows interest in the company, and you are never harmed by reviewing and practicing on some questions and topics like I listed, and researching the company for the interview. It builds confidence and psychologically prepares you to participate in interviewing tasks.
Normal forms for instance is something I don't regularily use, but its a convenient question for an interviewer. While your job hunting, why not make sure you have them down? Do you think that's somehow cheating?
Obviously if a company demands I arrive in 10 minutes for an interview, I don't have advice in general for everyone, but I personally would probably give that one a pass, a company that lacks logistical ability to schedule interviews sort of fails one of MY interview questions, ie., can the company schedule meetings in a reasonable manner?
I absolutely agree... you're a fool not to prepare for an interview... especially if you want or need the job.
Just to be sure, though, my point is that if you HAVE to prepare for an interview, especially when it comes to what may be asked concerning the primary skill required by the job, then you may not get the job even if you do prepare because you might not actually know enough about your primary skill.
Heh... and to your point, I'd keep an eye peeled for cultural problems of any company that required a "show up right away or forget it" type of interview. It may be a warning of bad things to come or it may be that they want to scarf you up before anyone else does (which may or may not be a bad thing).
There's also what I refer to as an "Accidental Interview" that starts with your next breath. These are happenstance interviews that could have their start in a chance meeting just about anywhere. There's no time to "prepare" for such a thing if you're not already prepared. Either you know what you're talking about or you don't.
is pronounced "ree-bar
" and is a "Modenism
" for R
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.
"If you think its expensive to hire a professional to do the job, wait until you hire an amateur."--Red Adair
"Change is inevitable... change for the better is not."
When you put the right degree of spin on it, the number 3|8
is also a glyph that describes the nature of a DBAs job. 😉
How to post code problems