Hi! We're hiring a Database Specialist and want to be able to test job candidates' SQL experience. We found an MS SQL interview test online, but we're wondering if anyone out there in the Tessitura community has an interview test they already use successfully or has any advice to share. Thanks!
We don't have anything currently, so I'd love if you could share what you end up going with!
That being said, it's much easier to teach SQL skills than it is to teach clear & collaborative communication skills, so just make sure you're testing both! :)
Agreed! Communication and people skills aren't nearly as trainable as SQL. I had a couple of days worth of SQL training when I administered Microsoft Dynamics in a past life and then took a couple of online classes as a refresher when I became a Tessitura Sys Admin. I'm able to write custom reports, stored procedures, and tons of queries with what I've learned through those classes, on the job experience, and TLCC sessions. I'd love to see the test you end of designing to see how I'd do.
Best of luck!
The way I looked at it was if you know the SQL then I can give you time to learn how the Theatre and the users work, or if you know how Theatres work then we can teach the SQL, but you need a good knowledge of SQL or in a Theatre.Which is why I tend to set 2 tests. One sql focused and the other on information gathering.
SQL technicaltest - I set some queries up for people to explain what they do, or what they think they did - often with simpler questions like how many columns does it bring back if they struggle or are nervous at the start.Then some with obvious mistakes - like not incrementing a variable in a loop.Finally a test where you add an extra table into the sql that causes that amount paid to almost double in the second query result but keeps the seat count the same - so testing how thoroughly people not only check the sql but the result (common sense checking) and if they know what caused it/how to fix it
This is an oral test rather than written as I always felt it was more important to understand how people try to tackle a problem rather than just knowing the right answer, this was a way to judge people with less SQL knowledge who may have strengths elsewhere as well as ascertaining the level of experience of those with SQL knowledge. This part of the interview also involved DP and PCI knowledge.
That was the technical test, the second test itries to find out if they understand what information they need to get and to see who they go about asking a user for the information - have had more experience than I like of having people spend days writing some complex sql and when the user sees it say it isn't right and tell you what they need to change which in the majority of cases led to the sql being simpler and a couple of hours work.
Setting them the problem that Dev team wants to record usage of First Night tickets against their patrons. A member of the Dev team is in the interview and is their to be asked questions about this.Most SQL devs don't do that but try to concentrates on writing the SQL even without knowing table structures or what the user actually want. How people approach asking the Dev user what they are trying to do and asking for clarification on terms etc again tells you a lot about how someone approaches solving a problem which can often be more important in the long run as they will always be faced with an issue they haven't seen before.Admitting to not knowing something (esp in an interview) is one of the better indicators in this test.
Unfortunately I don't have copies of tests as they were with the last place I worked.
There are some people on the forums here who have experienced these tests though.