Tag Archive: interview

SQL Server Interview Questions and Answers – Book Review

I read a lot of technical books – stuff on SQL Server, VMware, storage – and they all start to blend together.  Within the first few pages of reading SQL Server Interview Questions and Answers by Pinal Dave and Vinod Kumar, though, it jumped out and grabbed me because it’s really different.

Just kidding. When I'm talking to a recruiter, I read The Art of War

This is gonna be the year I get a better job, I swear. I'm outta this hole.

When buying this book, you need to appreciate it for what it is: a series of questions and answers.  No more, no less.

There’s almost no code, no syntax – and believe it or not, that’s refreshing.  It’s just plain English dialog.  That’s not to say the book is shallow, either, because it touches on topics that all of us could stand a refresher on.  This book works really well for its purpose in much the same way that Applied Architecture Patterns works; it doesn’t teach you as much as it just exposes you to subjects.  From there, it’s up to you to follow the trail if you’re interested in the topic, and that’s where Pinal and Vinod break new ground.

Check out this quote from page 50:

“What is a filtered index?  A filtered index is used to index a portion of the rows in a table.  This means it applies a filter on an INDEX which improves query performance, reduces index maintenance costs, and reduces index storage costs when compared with full-table indices.  When we see an index created with a WHERE clause, then that is actually a Filtered Index.  (Read more here http://bit.ly/sqlinterview27)”

The “read more here” part is actually in the book, and it links to one of Pinal’s intro posts about filtered indexes.  Just like all of Pinal’s posts, it includes clear, easy-to-follow script examples and screenshots.  Having said that, if you don’t like Pinal’s blog, you’re probably not going to like the book either.  The book has less technical details than the blog, and there are grammatical/editing issues.  That kind of thing doesn’t bother me as much with this book because of its intended market – it’s just a series of questions and answers.

Will The Answers Help or Hurt the Interview Process?

In my DBA interview questions and SQL developer interview questions blog posts, I went out of my way not to include the answers.  I wanted to give managers some starting points for questions that they could use to filter out candidates, but I didn’t want to give unqualified candidates a leg up in the interview process.  Those blog posts are consistently popular in Google searches, but based on the search terms being used, I know the candidates are looking for ways to cheat the interview process.  Therefore, my first concern going into this book was, “Are unqualified candidates going to sneak into jobs by reading this book?”

I don’t think that’s going to be a problem because the book is more of a refresher than a cheat sheet.  As I read the questions, I found myself nodding and saying, “Yep, that’s a great way to answer that question, but if somebody doesn’t understand the underlying concepts, they’re still going to fail the interview as soon as somebody drills down.”  An interviewer can see past the fakers just by asking, “And how have you used that concept in your work?”  The book also doesn’t stand alone as a complete interview process: managers still need to ask candidates to whiteboard concepts or reverse engineer a stored procedure to see what it’s doing.  Frankly, if somebody walked into an interview with this book memorized start to finish, and they didn’t have any other skills whatsoever, they’d still be more qualified than a lot of candidates I’ve interviewed.

My second concern about the book was that an incorrect or poorly-worded answer might cause a good candidate to miss out on a job.  If a non-SQL-savvy manager asked questions verbatim out of this book and expected verbatim answers, the book could lead to problems.  Some of the book’s answers are open to interpretation – for example, on page 41, the book asks, “What is OLTP?”  The book’s answer doesn’t match with what I would give, nor with Wikipedia’s definition.  Some of the answers are more clear-cut, though, like when page 54 says there’s a limit of 256 tables per query, and that’s wrong.  I’d recommend keeping the book’s online errata handy.

I get really nervous about the thought of a manager relying on this book’s answers as their only gauge of a candidate’s knowledge.  However, I’ve been through interviews like that myself – having a disagreement with a manager about the answer to a particular topic – and that’s a place that should be inside every DBA’s comfort zone.  We work with developers, project managers, and end users who have all kinds of incorrect assumptions about technology, and they’ve got books or blog posts to back up those assumptions.  We have to be able to back up our own answers, and sometimes that means saying to a manager, “We both believe we’re right – can you pop open a search engine and let’s check the latest documentation on SQL Server from Microsoft itself?”

Is This Book Just for Job Candidates?

I also bet that any of my readers will learn at least one thing reading this book, and it’ll drive you to go dive deeper into a particular topic.  I’d already learned something by page 34 when the book covers the order of the logical query processing phases: FROM, ON, OUTER, WHERE, GROUP BY, CUBE | ROLLUP, HAVING, SELECT, DISTINCT, ORDER BY, TOP.  I read that and a little light went on above my head – I’ve seen this kind of thing before, but I hadn’t thought about it in years, and it inspired me to go hit Google and learn more about the phases again.

The funny part about this book is that I like all of the questions, most of the answers for accuracy, and the rest for provoking thought.  I know that wasn’t the original intent, and it’s a hilarious thing for me to write in a book review, but there it is.

This book is a good starting point for MCITP test-takers, too.  The questions give you an idea of your qualifications because when an answer doesn’t feel natural to you, you can go drill down into the web to learn more about the topic.  If a topic feels like a no-brainer to you, then you probably shouldn’t waste time studying MCITP information about that topic either.

You can buy SQL Server Interview Questions and Answers for about $10 at Amazon, and Amazon Prime members with Kindles can read the Kindle version for free.

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

How to Get a Better Job

One of the most common questions I get goes something like this:

I’ve been working as an (insertJobHere) for a few years, and I’d like to start looking for another job as an (insertBetterJobHere).  How can I get started?

It depends on the phase of your career.

Phase 1: The Kindness of Strangers

When you’re just getting started – whether you’re fresh out of college or currently enrolled – you’re not going to know anybody.  You’re going to be cold-calling strangers, sending your resume to people you’ve never met, and hoping that you can knock ‘em dead in the interview.

Headhunter Company Car

Headhunter Company Car

Examples of hiring methods for Phase 1 are:

  • Newspaper and online ads
  • Recruiters
  • Consulting companies

There’s two problems with Phase 1.  First, you’re going up against complete strangers.  People in Phase 1 are desperate, and they’ll do some crazy stuff to beat you out in the job hunt.  They’ll work for less money, they’ll lie about their resume, they’ll use their mom as a reference, you name it.  Getting a better job when you’re going up against strangers can be a nightmare.

Second, you’re going to work for complete strangers, which can be a living hell.  You won’t find out that they’re raving lunatics until after you’ve already quit your current job and gone to work for them.  Every time I’ve gone to work for strangers – every single time – I’ve regretted it within a matter of months.

Strangers hire other strangers when they run out of friends willing to work for them.

Phase 2: The Buddy System

After you’ve been working for a few years, going to local user group meetings, and survived a few reorgs, you’re going to know a lot of other people working in your same field.  You’ll even know people in unrelated fields.  DBAs meet project managers, end users, report writers, developers, and so on.

Everybody Loves the Buddy System

Everybody Loves the Buddy System

When it’s time for you to start looking for another job, you can put out the word among your contacts.  Because they’ve worked with you before and they know what a kick-ass worker you are, they’re likely to vouch for you.  They’re likely to tell you about jobs before they go into Phase 1 recruitment, because they’d rather hire you than a stranger.  You’re a sure bet, because you’re doing such good work.

The only way to get from Phase 1 to Phase 2 is staying in touch with people.

I can’t emphasize this enough – if you don’t learn to network, you’re going to be permanently stuck in Phase 1.

Networking sounds so slimy, but it just boils down to this: meet people, and keep in touch with the ones you genuinely like.  I used to think networking meant rubbing shoulders with greaseballs who were trying to sell each other stuff, but that’s not true at all.  Just keep in touch with people you like, and go to the places where they hang out to meet more people like them.  For database professionals, that’s the upcoming PASS Summit.

Befriend Buddies, Not Just Bosses

One fast way up the corporate ladder is to hitch your wagon to a rising star.  If you do great work for a great boss, you can both go places quickly.  I’ve taken that approach a few times in my career, and it’s served me really well.  I remember getting a call from one boss as soon as he’d changed companies, and he said, “I know what you’re making now.  I’ll give you an extra $X to come work for me at the new shop, and you know I’ll be good to you.”  Sold.  However, that’s not the only way up.

The programmer next to you today might be the CIO at another company tomorrow.  A few years ago, Matt Mullenweg was just another guy I ran into at Houston Wireless meetings.  I had no idea he was building something cool in his spare time, and since then, that little blogging platform has raised tens of millions of dollars in funding.

Look around you right now.  Your coworkers and customers are the only ones who will take your career to the next level, regardless of how unskilled and antisocial they seem.  Even if they’re really, really bad at what they do, it’s your job to make them look better and leave a permanent positive impression on them.  They might be your key to a better job down the road.

If you wait to network until you need a job, it’s too late – and you’ll be stuck in Phase 1.

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

Top 10 Interview Questions for Windows Administrators

I know, I know, I do a lot of these posts, but Steven Murawski posted a tweet asking for our best questions to ask during an interview of Windows sysadmins and desktop administrators.  Here’s my favorites:

10. Pretend I’m a manager, and explain DNS to me.

Windows is increasingly tied to domain name resolution, and the bigger your company gets, the thornier DNS problems become.  If they can verbalize how end users’ computers make DNS requests and how forwarders work, and then if they can toss in Active Directory, they’ve solved some enterprise problems.

Starting with a generic open-ended question like that tests a candidate’s communication skills, too.  Bonus points for making a tough concept seem easy.

9. What’s a Windows profile? When would you delete one, and what gets deleted?

If you’re looking for someone to do desktop support, they should have at least a vague idea of where the user’s data can be stored.  Bonus points if they can explain where common application settings are stored, what the Registry is, and how roaming profiles work.

8. When an end user says a file went missing, what do you do?

End users delete files all the time, but before you recover it from backup, first do a search on the drive to make sure they didn’t drag & drop it to another folder.  (Normally I don’t give interview answers here, but that one’s an exception.)  Then, after they explain that, I’d ask them to cover things like VSS snapshots, end user recovery in Explorer and how to restore from their favorite backup program.

7. How do you recover one SQL Server database or one Exchange mailbox?

Different backup systems have different ways of dealing with this, so I may not be able to vet their exact answer if I haven’t used the same backup system they’re using.  However, I can do a pretty good job of sniffing out when someone doesn’t understand the complexities involved.  If they shrug and just say “I click restore and it’s done,” then they’re bluffing.

For example, when restoring an Exchange mailbox, do you really want to pave over every email the user has received since the last backup?  Or does the user just need one or two important emails pulled out of the archive?

6. If you get hired and you can pick any laptop, what do you get?

I wanna see ‘em get all excited.  I wanna see ‘em giddy with glee at the thought of picking out their own shiny new hardware.  The more excited they get, the more I know systems administration is a way of life for them, not just a hobby.

5. What’s the first software you’d install?

Hardcore sysadmins have their own favorite tools they like to use.  Listen with an open mind, too – the more sysadmins you interview, the more cool tools you’ll discover.  If they mention a tool you haven’t used before, drill into it.  Find out why they use it and how it saves them time.  If it’s a tool they’re passionate enough to mention, then they can probably describe some underlying concepts and technologies involved, and it’ll give you more confidence that they know what they’re doing.

4. What do the letters PST mean to you?

I want to know if they’ve experienced the pains (both technical and legal) involved with these files.  How do they back up PST files if the end user leaves their laptop online all the time?  Are there any size concerns with PST files?  Is there a good way to use PSTs?

3. What’s PowerShell, and how do you feel about it?

I don’t necessarily need PowerShell experience (although it’s a big plus for Windows sysadmins) but I want to know that they’re at least vaguely aware of the concept and what it means.  Bonus points if they can relate scripting to the *nix world, and if they bring up Windows Core.

2. Are you involved with any local user groups?

Be it Windows or just a hardware hacker group, I love candidates who love communities.  I like seeing someone get so involved in what they do that they seek out other people who share similar interests.

1. What do you want to do next?

Windows systems administration is a cool gateway into a lot of different careers.  Do they want to manage Exchange?  Become a SQL Server DBA?  Go into management to be the next CIO?  Having a drive and a passion means they’ll try to do a better job so they can keep moving up the ladder.

Want help interviewing your candidates?  Check out our services.

Brent Ozar PLF Team

Brent Ozar PLF is a boutique consulting firm focused on understanding your environment and strategy. We partner with you to objectively identify pain points and develop solutions that align to your business goals. Your experience comes first; we share our knowledge and expertise to help you.

Twitter - Facebook - More Posts

Top 10 Developer Interview Questions About SQL Server

Knowing good SQL questions to ask during an interview with a developer can help you filter out the best candidates from the ones who aren’t the most qualified.  There’s a huge difference between “It worked on my machine” and “It scales well in production.”  These interview questions will help you filter out the bad apples before you hire them.

10. Explain why DBAs don’t like cursors.

I like to phrase this interview question this way because I’m not saying the DBA is right – I’m just asking the developer to explain the DBA’s point of view.  I don’t have a problem with the developer rolling their eyes as they explain the answer, but I have a problem with the developer being surprised by the question.

The candidate gets bonus points if they seem even vaguely aware of the terms “set-based processing” and “row-based processing”, but that’s purely a bonus.  (I wish I could say that these concepts are requirements, but in today’s economic market, companies don’t always want to pay top dollar to get the best candidates.)

9. Where do you like business logic – in the app or in the database? Why?

Personally, I like stored procedures because they’re easier for us DBAs to test, tune and tweak. On the other hand, the developer community isn’t always as fond of stored procs.  For their side, see these posts by Jeff Atwood:

I don’t mind what arguments the coder candidate uses, but I want to see ‘em put some thought into it.  No matter which angle they take, I’ll play the devil’s advocate and prod them with arguments just to see how they react.

8. Explain when and how transactions should be used.

Not In The Oprah Book Club, Oddly

Not In The Oprah Book Club, Oddly

Start with just that open-ended interview question, and if they have trouble getting started, give them a scenario.

“Say we’ve got a table for Orders, and a table for OrderDetails.  Someone places an order for two books – Bacon: A Love Story and the hit bestseller Eat What You Want and Die Like A Man.  Tell me what happens.”

After they’ve answered, ask them when transactions should not be used.  I don’t want my developers wrapping anything inside a transaction unless it absolutely needs to be.  (Unlike bacon, which should be used as often as possible for wrapping purposes.)

7. Explain referential integrity and where it can be enforced.

If they stumble on the question, circle back to the Orders and OrderDetails tables we used as examples earlier.  What’s an orphan?  How do we make sure that we don’t end up with OrderDetails for records with no matching Order record?  Where are all the places we could enforce referential integrity?  (Think foreign keys, triggers, the application, or not at all.)  Have you worked in places where there was no referential integrity, and what problems did you run into?

6. What’s the fastest way to get a thousand records into the database?

I’m not looking for the best answers – I’m just looking to hear that they’ve done some work to performance tune their queries.  If they’re doing fully logged individual record inserts, one at a time, into a data warehouse-size system, we’re going to have problems down the road.  (Yes, I’ve actually worked with a BI developer that did millions of individual inserts per night in full recovery mode and thought the performance was the database’s fault.)

Bonus points if they link back to the previous interview question and talk about whether or not they should disable constraints or referential integrity during data loads.  (I don’t care what their final answer is, but I just want them to know the pros and cons.)

5. What’s the difference between a primary key and a clustered index?

This is almost a bonus question.  Most of the time, the candidate doesn’t know because it’s a function of the data modeler or architect, not the developer.  However, I want to see how the candidate reacts to tough questions.  Ideally, they say in a relaxed tone of voice, “I’m not sure, but I know who I’d ask.”  If they don’t mention where they’d go, ask them where they go for SQL Server answers.  Speaking of which…

Bonus Points for This Candidate

Bonus Points for This Candidate

4. What’s your StackOverflow name?

I don’t need to see a high reputation, but I do want to see an awareness of the site.  This interview question serves two purposes: it finds out if they’re serious enough to be active in the community, and it shows them that you’re okay with their community activity.  Start a conversation with them about the level of internet time that you find acceptable in the office, and encourage them to share their knowledge with their peers.  This sells the candidate on your shop.

3. Tell me about a time when a DBA got mad at you.

This is a spin on the classic interview question, “Tell me about a time when you failed.”  Implemented a user-defined function, trigger, CLR in the database, or something else that made the DBA freak out?  I want to hear that the candidate listened to what the DBA had to say, good or bad.

If they say it’s never happened, rest assured it’s going to happen soon.

2. How can you tell if a query will scale for production?

I want to hear that they do things like load tests or maybe look at execution plans.

I’m sometimes comfortable when a senior developer says things like, “I can pretty well tell when something isn’t going to scale, because I know the production boxes really well.”  The key is asking a followup question about times when things didn’t scale.

1. When is the DBA right?

Always, kid.  Always.

Want help interviewing your DBA candidates?  Check out our services.

Brent Ozar PLF Team

Brent Ozar PLF is a boutique consulting firm focused on understanding your environment and strategy. We partner with you to objectively identify pain points and develop solutions that align to your business goals. Your experience comes first; we share our knowledge and expertise to help you.

Twitter - Facebook - More Posts

SQL Server DBA Interview: Kendal Van Dyke

Kendal Van Dyke is a Senior SQL Server DBA from Florida, and he’s been blogging since last year.  He’s syndicated at SQLServerPedia, and his recent series on RAID performance is a must-read.  I’ve talked back and forth with him a lot lately, and I figured I’d try something new: a virtual interview.  I emailed Kendal a list of questions, and here’s how it went down:

Kendal Van Dyke

Kendal Van Dyke

Brent: I think I recognize your avatar because you fragged me last night.  What made you decide to use your Xbox avatar as your online persona?

When I started getting really active in the online SQL community I didn’t have a decent headshot so I just used my avatar since I had already made one for XBox Live. It unintentionally turned into something recognizable since I used it everywhere. One of these days I really do need to take a good headshot though. I don’t think my avatar will be taken seriously by the PASS abstract selection committee, unless of course they think I really am a 6 foot tall cartoon.

Brent: I can tell by reading your series on RAID performance that you put a ton of work into it.  How many hours did the whole thing take, start to finish?

I didn’t keep track, to be honest! The testing was spread out over two months, with maybe 4-5 hours per week put into pushing buttons and rebuilding drives in different configurations. The hardest part was writing up the results. I put at least 4 hours of writing into each part of the series. All in all I probably put at least 50 hours into it, if not more. I’ve got more things in store that I hope to publish soon, too.

Brent: Blogging, when you do it right, is a part time job – if not a full time job.  It’s also the worst-paying job I’ve ever had, hahaha.  Why do you do it?

I gave a presentation at the first SQL Saturday in Orlando two years ago. As nerve racking as it was, I found that I really enjoyed sharing what I knew and I came to realize that I had more things to share that other people might be able to learn from. I also realized that there were a lot of one-off things that I wanted to document somewhere in case I ever ran into them again, and a blog seemed like the best way to kill two birds with one stone. I’ve had comments on some of my posts thanking me for helping solve a problem and that alone makes it worth it for me. It certainly isn’t for the money! haha

Brent: You got started blogging on your own web site.  If you’re trying to reach the most number of people, why do you blog on your own, instead of, say, using a popular group blogging site, writing magazine articles or writing books?

Bruce Campbell did a terrific commercial for Old Spice about experience that sums this up nicely. Although sites like SQL Server Central allow open submissions for articles, my impression is that writing for a magazine or a book – or even blogging on the bigger sites – is by invitation only. You don’t get an invitation unless people know who you are so you’ve got to build up your reputation somehow. Some people do that by answering forum posts. Others build up their social networks. I choose blogging and I ended up on Blogger because it was free, easy to get started, and I could figure out what to write about (and how) without any pressure. Now that I’ve got a year of experience I think I’ve gotten to the point where I can do those other things. Ironically, I don’t know that I want to blog on the bigger sites anymore – I worked hard to build up a personal brand and I don’t know that I’m ready to give up the control that I have over my own look and feel that having my own blog affords me. Instead, my next move is to take content that I would normally put on my blog, start publishing it in articles, and reference my blog if readers want to read more from me. That way I can maximize reach while still retaining the identity I built for myself. It’s a win-win for me. As for books, perhaps one day I’ll have gained enough recognition to be offered the chance to write something, but that’s still a long way out.

Brent: If you could give new bloggers any tips about the experience and how to get started, what would you say?

I’d start by reading your series on how to start a technical blog (I wish you had done that series before I got started, it would have really helped me!). Be patient because it’s going to take time to build a subscriber base and generate regular traffic. Having a pillar post really helps too. Before I wrote my disk performance series I was getting 10-12 visitors a day and now I’m over 100 per day just for that series. Also, don’t be afraid to ask other bloggers for feedback and help. I’ve found the blogging community to be very open when I’ve asked for advice.

Brent: You’re on Twitter as @SQLDBA.  How’d you find out about Twitter, and what made you start using it?

I’d heard bits and pieces about Twitter from news sites, blogs, etc, but I never paid much attention to it until the 2008 PASS summit. I didn’t get to go to the summit but I subscribed to the RSS feed for #sqlpass and got a kick out of what everyone was tweeting. That prompted me to sign up for an account and now I’m hooked!

Brent: The call to speakers is out for the PASS Summit in Seattle, and I know you’ve done some speaking.  Are you submitting any sessions this year?  I wanna encourage you since my favorite sessions always involve storage, heh.

Absolutely! One of my goals this year it to attend PASS as a speaker. And yes, the disk performance stuff will definitely be one of my abstracts. I haven’t submitted anything yet but when I do I’ll post the details on my blog.

Brent: Sounds good, looking forward to it!  Readers: swing by Kendal’s blog and check it out.

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts

Top 10 Questions To Ask During an Interview

Stop!  Before you accept that cushy job, make sure it’s actually as cushy as you think it is.  Managers have a long line of questions to ask in an interview, but what about you as a candidate?  What questions should you ask?

Here’s my top ten questions to ask before taking an IT job:

10. What happened to the last person in this position?

Did they quit, did they get promoted, did they die of a stress-induced heart attack, what?  Rarely is a position created completely from scratch, and you want to know why the last person left so you can avoid their fate.  If they’d been around for less than a year, I would ask the same question about their predecessor as well.

9. Have you had any layoffs in the last year?

Nobody’s going to tell you if layoffs are scheduled for the future, but you can at least ask about the past.  Maybe they did a round of layoffs and they’re perfectly positioned for future growth, but maybe they’re spiraling down the toilet.

8. What’s the on-call rotation schedule?

Will you be sharing the pager with someone, on call one week per month, or on call at all times?  If you’re on call, do you get a company laptop and wireless aircard to be able to respond, or do you have to hoof it to the nearest desktop, or heaven forbid, the office?  And to follow that up…

7. In the last year, how many times has the on-call person been called?

From 1997 until 2008, I was on call 24/7 – but I got maybe one call per month.  That kind of load is do-able, but if the on-call phone is ringing every other night at midnight, forget it.  Or at least budget psychiatry bills in with your expenses.  Speaking of expenses…

6. Is there a training or travel budget for this position?

In your struggle up the career chain, you’ll reach a point where suddenly you’re expected to do a little learning on the company dime in order to keep your skills sharp.  It never hurts to ask.  If the answer is no, ask if you would be paid your salary while attending an industry conference like the week-long PASS Summit on your own dime.  I know employees who have to take vacation time to attend these conferences, and that really hurts.

5. Can I access online tools to do my job?

More and more companies are barring employees from surfing the web.  This isn’t just a quality-of-life issue – although allowing Twitter would be nice – but it can also make life tougher when troubleshooting an IT problem.  The best help is on the web, not in Books Online.

4. Can I schedule vacations around the holidays?

I’ve worked in IT shops where everybody wanted to take vacation around Christmas week or New Year’s, but the low guys on the totem pole weren’t allowed to do it.  Seniority dictated the vacation schedule, so the old pros got the holidays off while the new kids on the block got shafted.  It shouldn’t dissuade me from taking a job, but it’s something to think about.

3. How important is my work to the company?

I’ve worked in shops where my database platform was the black sheep of the family, the platform of last resort.  I’ve worked in shops where it was seen as highly visible and mission critical.  The more valued this position is, the more you’ll be seen as an asset to the company – and less likely to be looked over at raise time, or worse, laid off.

2. What’s the telecommuting policy?

Database administration lends itself really well to working from home.  Denny Cherry and I sit around our houses most of the time, while some folks are cursed with driving in to the software factory every day.  Telecommuting cuts your expenses, increases your productivity, and raises your quality of living.  Some companies get it, and some don’t – but ask before you start.  This is one of those policies that probably isn’t going to change after you take the offer.

1. What does “success” look like for this position?

Here’s how I like to phrase this to my future manager: “90 days after I start, if you’re talking to your boss about what a great job I’ve done in my first 90 days, what kinds of things are you raving about?  What are the tasks that you wish this new employee could accomplish?  What would make you the proudest?”

The answer to this isn’t written in the job description.  We’re talking about things that will make your manager jump up and down with excitement, things that will make you a seriously valuable employee, and things that you want to put first on your task list when you start.

And a Bonus Question: Will I have to sign any non-compete agreements?

In IT, the answer to this is often yes, and they can be pretty restrictive – especially at consulting companies.  It’s not uncommon to sign away your rights to work for any competitors or any clients for years after you leave the company.  In a tight market or in a small town, that can pretty much eliminate your job options.  Better to find out ahead of time rather than after you’ve already accepted the offer, quit your old company, and started filling out your new hire paperwork on your first day at the new job.

More Articles on Interview Questions

If you liked this, here’s a few more of my posts about interview questions for job candidates:

Brent Ozar PLF Team

Brent Ozar PLF is a boutique consulting firm focused on understanding your environment and strategy. We partner with you to objectively identify pain points and develop solutions that align to your business goals. Your experience comes first; we share our knowledge and expertise to help you.

Twitter - Facebook - More Posts

8 DBAs talk about their jobs

OdinJobs.com interviewed eight different DBAs from completely different backgrounds and careers.  The one thing we’ve got in common is that we blog, but outside of that, we’ve got wildly different points of view about the career and what we like about SQL Server.

I shall now copy/paste Jason Massie’s hard work at listing each person’s blog URL and feed, because I have no shame:

The Panel Blogroll

Inside the articles, the links don’t work too well, so you can jump to the three parts from here:

I love reading articles like this because they tell me a lot about the people answering the question.  I got a chuckle out of Pinal Dave’s answer to the question about the differences between production DBAs, development DBAs, and SQL Server Developers.  (Pinal – if you read this, no, we are not all the same, and I’ll buy you a drink at PASS to tell you about some horror stories there.)

More DBA Career Articles

  • Moving from Help Desk to DBA – a reader asked how to do it, and I gave a few ways to get started.
  • Development DBA or Production DBA? – job duties are different for these two DBA roles.  Developers become one kind of DBA, and network administrators or sysadmins become a different kind.  I explain why.
  • Recommended Books for DBAs – the books that should be on your shopping list.
  • Ask for a List of Servers – DBA candidates need to ask as many questions as they answer during the interview.
  • Are you a Junior or Senior DBA? – Sometimes it’s hard to tell, but I explain how to gauge DBA experience by the size of databases you’ve worked with.
  • So You Wanna Be a Rock & Roll Star – Part 1 and Part 2 – wanna know what it takes to have “SQL Server Expert” on your business card?  I explain.
  • Becoming a DBA – my list of articles about database administration as a career.

Brent Ozar

Brent specializes in performance tuning for SQL Server, VMware, and storage. He's one of the very few Microsoft Certified Masters of SQL Server, a published author, and a Microsoft MVP. He likes travel, Jeeps, Apple gear, jokes, and writing about himself in the third person. Read more and contact Brent.

Website - Twitter - Facebook - More Posts