Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 

SQL Exercise During Candidate Interview Process

A discussion of how BPS uses a SQL exercise for candidates and why it is helpful.

At the Boston Public Schools, SQL is highly important. As I mentioned in my introductory post, the data at BPS is vital and a significant chunk of time for any application developer is spent at the database level writing, modifying, or reviewing queries.

Over the last year we’ve spent a good deal of time looking for good candidates for a few open application developer positions. Some of the interviews went well, others not so well, and we’ve made several new hires in the last year. One of the key aspects to the interview process has been a SQL exercise we administer. Candidates work out the solutions at a computer connected to a real database using Query Analyzer and/or SQL Management Studio.

The SQL Exercise itself isn’t terribly difficult. It has 5 questions with the first few being somewhat easy and the last couple being moderately difficult but certainly not overly complex. Rather than asking 5 unrelated SQL questions, each question builds on the previous one in some way by adding a handful of extra requirements or a particular logic modification. While the questions aren’t too difficult, the exercise has become a cornerstone of the interview process. Why? For a number of reasons:

  1. It establishes that a candidate has a baseline fundamental understanding of SQL. The queries require the use of grouping, correct filtering criteria in the where clause, selecting a certain number of rows, joining tables in the right way, etc. Simple stuff, yes, but it serves as a way to ensure a baseline level of competency in SQL.
  2. It shows how candidates do under pressure. We give candidates 30 minutes, and the majority were unable to finish all 5 questions [most got through 4 questions]. While it is completely understandable if someone isn’t quite able to finish, if a candidate is simply unable to get even through the first 2-3 questions, it isn’t a good sign for how they’ll do on the job. However, if they get through all 5 with time left to spare and have developed clean, correct queries, that’s a very good sign.
  3. It gives insight into their coding standards. For example, is the SQL clean, indented, broken over multiple lines, etc? Are good table alias names used? Does anything stick out that screams “unmaintainable”?
  4. It gives us a way to evaluate how they react if they’re unsure about something. Many of the candidates ask at least one or two clarifying questions during the exercise. For the ones that don’t, it’s either because they completely understand the requirements [which is fine] or they decide not to seek help despite needing it. The latter would raise a red flag – what if they encountered a similar situation while actually working on a high-priority task? We’d certainly prefer they seek assistance and clarification when needed.
  5. The SQL Exercise is a great comparison mechanism between candidates since everyone gets the same set of questions. While we certainly consider other aspects of the interview when making a hire decision, the SQL Exercise can help sway the decision and/or help break a tie between two equally qualified candidates.

I’d highly recommend anyone evaluating technical candidates to incorporate a hands-on technical exercise into the interview process. For BPS we chose a SQL-oriented exercise, but other possibilities [depending on the focus of the position] including asking candidates to develop a mockup webpage design, code a certain business logic function, develop a simple web form with specific requirements, etc. The exercise should be a representative [though likely scaled down] version of what the candidate will do on the job and will therefore give insight into whether they’re ready to successfully do the job they’re interviewing for.

Comments

Posted by Anonymous on 1 June 2011

Pingback from  Dew Drop – June 1, 2011 | Alvin Ashcraft's Morning Dew

Posted by John Sansom on 1 June 2011

Hi Andrew,

It's always interesting to hear about how other organisations go about their interview process for Data Professionals. Thanks for sharing yours with us.

Requiring candidates to perform practical exercises is without a doubt a valuable tool for the interviewer. The more relevant the exercise the better, with real business scenarios for your particular organisation being the most ideal, although granted not always practical to provide.

Posted by Jason Brimhall on 1 June 2011

I like to use hands on exercises as well.  I think it is useful for much the same reasons you have listed.

Posted by Martin Catherall on 1 June 2011

yes, we use a very similar method of filtering for developers, there's a bit more than SQL involved here, but the're given 6 user stories (we like agile) each progressively more difficult. Most people are expected to get through the first 4, but the last 2 are pretty difficult. The user story test is designed to not only test the candidates technical ability, but how they interact with others.

Posted by Anonymous on 1 June 2011

Pingback from  SQL Exercise During Candidate Interview Process – Help With SQL … |  | Sports Fitness StoreSports Fitness Store

Posted by netmikem on 5 June 2011

We do something similar although we've been typically looking mainly for developers ... who have some SQL skills (i.e. not database developers per se). This is just one aspect of the interview process.

One thing we do differently is that we don't give the candidate a computer. It is a paper test with 6 SQL questions, most of them are relatively simple.

While we recognize that we all use Books Online at various times, we wanted to avoid giving the candidate that crutch so that we can gain more insight into their experience and general approach. We don't take points off for minor syntax issues.

Posted by Ramdas Narayanan on 6 June 2011

I like the approach of taking some basic sql question(s) and adding requirements as the interview progresses. It gives more insight into the candidates train of thought and the approach problem solving.

Posted by David Voss on 13 June 2011

I recently interviewed where the technical portion was done on a whiteboard.  I didn't realize how much I came to rely upon Intellisense and Visual Studio for my .NET development and SQL Prompt, Books Online, and Google for SQL. :)

Posted by john.campbell on 28 June 2011

I had one of these tests several years ago.  The first one was about the use of sp_helptext, which I had never heard of.  The guy felt sorry for me and said just skip that and go on with the rest. He stopped me at #8, saying that no one had ever done that many problems correctly.  I was hired on the spot. He removed the sp_helptext question from his test, and I use sp_helptext once in a blue moon.  I thought that it was a very good tool that cut through a log of the B.S. and game playing that is involved in the hiring process.

John.

Leave a Comment

Please register or log in to leave a comment.