Depends if you are employing a production DBA or a development DBA, one DBA said to me once that all DBAs should be developers but in my experience the worst production DBAs are developers who are having a go at being a DBA but this is another discussion.

I've been a production DBA of many years, I've got an MCITP, I'm very proficient at what I do, I'm not an expert as no one is an expert (If you call yourself an expert you're obviously not as there is always more to learn which is another good subject for an interview question), I do some coding for the maintenance of the server and the odd bit of troubleshooting but if at an interview for a DBA role and I was presented with two pieces of code I think I'd turn the job down and explain that they were looking for a developer.

The interview should ideally be a practical test where the interviewee should fix a problem on a server coupled with a written exam and some tough interview questions. That's hardly ever the case though!!!

As the interviewee though you should be asking questions, you should also be interviewing the interviewer, ask them why they work there, ask them what they are looking for in an employee, at the end of the interview ask them if they have any reservations about yourself then you can clear up any misunderstandings, think of ten or so technical questions you can ask them, even write them down and take the questions with you, it shows you have been thinking about the company you might work for, don't ask all of them but ask the relevant ones. You might ask questions and the answers you get might put you off and save you from working from somewhere you won't like, treat the interview as an opertunity for all parties involved.

Answer... 'Why did you ask me for the interview in the first place then?' 🙂