Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

Need your help...SQL Developer interview questions..pls Expand / Collapse
Author
Message
Posted Sunday, December 01, 2013 9:24 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Friday, December 06, 2013 1:53 AM
Points: 51, Visits: 67
Hi All,
I am working in a small company having 2 years of experience .. But I am into Production Support..I am planning to move to other company and try for some SQL developer jobs..I have no idea what type of questions they ask..I tried googling, but all are direct SQL questions(like What are Indexes ? , What are the types of Joins? ) ..Could you please post some scenario based SQL developing questions ..It would be really helpful for me..
Post #1518702
Posted Sunday, December 01, 2013 5:00 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 7:47 AM
Points: 35,946, Visits: 30,231
Are you able to correctly answer and carry on a fairly decent conversation about those "direct" questions? If not, you might not survive the interview.

Shifting gears back to your request, the post at the following URL contains most of what I and many others expect an SQL Developer to be able to do and talk about in some good detail on top of all the "direct" questions. I say "most of what I'd expect" because I'd also expect a candidate to be able to talk about/demonstrate things like how to join 3 or more tables, being able to talk at some good length about the intricacies and dependencies of indexes, and to discuss various performance issues that they've solved in the past along with some new ones at the interview.

http://www.sqlservercentral.com/Forums/FindPost1517650.aspx

Of course, if it's for a Junior position, then a lot of those Senior level requirements aren't appropriate.

As for scenarios that they might ask or test you on... they seem to vary greatly based somewhat on esoteric knowledge that you might need to adapt to but I would expect them to ask you to handwrite some code for joined SELECTs, joined UPDATEs, and the like. If you pass those, I'd expect them to put a computer under your nose, give you some requirements, and have you create the necessary tables, keys, and indexes in a third normal form as well as write a query or two to solve certain problems on the objects you just created.

If it's truly for a Senior SQL Developer position, I'd expect scenarios from every bullet on the list I posted the URL for and more.

I'd also expect them to ask some questions about the four letter words in SQL Server like SSRS, SSIS, SSAS, and maybe even SSSB. They might also harp on you a bit about PowerShell and SQLCLR. I don't personally consider those questions to be appropriate for any level of SQL Developer but it happens. Such knowledge is sometimes used as a "tie breaker" between two or more good candidates.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

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."

"Change is inevitable. Change for the better is not." -- 04 August 2013
(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1518718
Posted Sunday, December 01, 2013 10:12 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 7:47 AM
Points: 41,508, Visits: 34,424
Different companies will ask different questions. Hell, I used to ask different questions depending on my mood and the candidate's CV. There's no fixed set of questions.

You say all google finds are direct questions, well, would you be able to answer scenarios around those direct questions? If someone asked you to determine the best index for a specific query or what join type should be used in a particular query, would you be able to answer?

Relax, don't exaggerate your skills, don't make up answers.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1518752
Posted Sunday, December 01, 2013 10:21 PM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Thursday, April 03, 2014 10:57 PM
Points: 416, Visits: 512
For only just 2+, they will ask you basics questions only, And, in some cases, they will like you write down some basic queries (just to see practical queries.)
And, it all depends on Your CV and Their Requirement.

So , Keep UP yourself with the "BASICS", i hope u will do fine.
Post #1518753
Posted Sunday, December 01, 2013 11:01 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 7:47 AM
Points: 35,946, Visits: 30,231
Mr. Kapsicum (12/1/2013)
For only just 2+, they will ask you basics questions only, And, in some cases, they will like you write down some basic queries (just to see practical queries.)
And, it all depends on Your CV and Their Requirement.

So , Keep UP yourself with the "BASICS", i hope u will do fine.


For front-end developers and companies that don't really know what they're asking for, I agree... the basics of SQL will normally get you by. But, if it's for a real "SQL Developer" job by a company that truly understands what the position is, be prepared to be ripped apart at the seams just so they can see what you're made of because the position of "SQL Developer" at any level is comparatively rare and competition for such jobs is high.

How do I know this? Because those are the only jobs I've sought for the last 12 years so I've been on plenty of those interviews and I'm currently conducting interviews for two companies that asked for help in finding good "SQL Developers". Even "experts" at the "basics" simply aren't good enough for those types of jobs. A really good "SQL Developer" can reach pay scales rivaling those of DBAs and people want to know what they're getting for their money.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

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."

"Change is inevitable. Change for the better is not." -- 04 August 2013
(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1518760
Posted Monday, December 02, 2013 3:51 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 3:51 AM
Points: 14,788, Visits: 27,264
I'm going to follow on what the others have said. You first have to demonstrate that you have the core knowledge of SQL Server before I start asking you other questions. If you don't know the difference between a clustered index and a non-clustered index, you are absolutely not going to do well with any of my database development questions.

----------------------------------------------------
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood..." Theodore Roosevelt
The Scary DBA
Author of: SQL Server 2012 Query Performance Tuning
SQL Server 2008 Query Performance Tuning Distilled
and
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #1518825
Posted Monday, December 02, 2013 10:51 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 1:12 PM
Points: 3,297, Visits: 2,340
Jeff Moden (12/1/2013)
Even "experts" at the "basics" simply aren't good enough for those types of jobs.

A nickel's worth of free advice on this statement: If you "talk the talk" and rate yourself as an "expert" you'd better be prepared to "walk the walk" because you will be called out on it. You may get by the initial interview, but they'll eat you alive during the technical interview.



Tally Tables - Performance Personified
Best practices on how to ask questions
Post #1518958
Posted Monday, December 02, 2013 12:23 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 7:26 AM
Points: 22,472, Visits: 30,141
Jeff Moden (12/1/2013)

...

How do I know this? Because those are the only jobs I've sought for the last 12 years so I've been on plenty of those interviews and I'm currently conducting interviews for two companies that asked for help in finding good "SQL Developers". Even "experts" at the "basics" simply aren't good enough for those types of jobs. A really good "SQL Developer" can reach pay scales rivaling those of DBAs and people want to know what they're getting for their money.



So that explains why you asked where I was willing to work when I posted that I would be coming home to having to look for work.

Too bad they aren't willing to work with a remote worker, or so I assume.



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1518991
Posted Monday, December 02, 2013 2:24 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 7:47 AM
Points: 35,946, Visits: 30,231
Lynn Pettis (12/2/2013)
Jeff Moden (12/1/2013)

...

How do I know this? Because those are the only jobs I've sought for the last 12 years so I've been on plenty of those interviews and I'm currently conducting interviews for two companies that asked for help in finding good "SQL Developers". Even "experts" at the "basics" simply aren't good enough for those types of jobs. A really good "SQL Developer" can reach pay scales rivaling those of DBAs and people want to know what they're getting for their money.



So that explains why you asked where I was willing to work when I posted that I would be coming home to having to look for work.

Too bad they aren't willing to work with a remote worker, or so I assume.


Z'actly. On both points.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

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."

"Change is inevitable. Change for the better is not." -- 04 August 2013
(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1519021
Posted Monday, December 02, 2013 2:33 PM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 7:26 AM
Points: 22,472, Visits: 30,141
Jeff Moden (12/2/2013)
Lynn Pettis (12/2/2013)
Jeff Moden (12/1/2013)

...

How do I know this? Because those are the only jobs I've sought for the last 12 years so I've been on plenty of those interviews and I'm currently conducting interviews for two companies that asked for help in finding good "SQL Developers". Even "experts" at the "basics" simply aren't good enough for those types of jobs. A really good "SQL Developer" can reach pay scales rivaling those of DBAs and people want to know what they're getting for their money.



So that explains why you asked where I was willing to work when I posted that I would be coming home to having to look for work.

Too bad they aren't willing to work with a remote worker, or so I assume.


Z'actly. On both points.


Why are companies so eager to use new technologies to reach customers but unwilling to use these same technologies to enhance their work force. Oh, and then you have companies willing to off-shore this type of work but not willing to on-shore it to remote workers.



Lynn Pettis

For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here or when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here and here
Managing Transaction Logs

SQL Musings from the Desert Fountain Valley SQL (My Mirror Blog)
Post #1519026
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse