Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase 12345»»»

Industry Experience... Required? Expand / Collapse
Posted Thursday, January 1, 2009 12:43 AM

SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Tuesday, August 4, 2009 10:02 AM
Points: 810, Visits: 915
Comments posted to this topic are about the item Industry Experience... Required?


A Freudian Slip is when you say one thing and mean your mother.
For detail-enriched answers, ask detail-enriched questions...
Post #628375
Posted Thursday, January 1, 2009 1:46 PM



Group: General Forum Members
Last Login: Yesterday @ 9:09 PM
Points: 42,046, Visits: 39,429
While I believe that industry experience can, indeed, be a huge help, I believe it should be "nice to have" rather than a requirement when it comes to DBA's and "Ninja" SQL Developers. Both of those types will quickly ramp up on just about any industry. It takes a much longer time for someone with industry experience to become an excellent DBA or "Ninja" SQL Developer.

The real fact of the matter is, I usually ignore the "must haves" on those types of job requests... it's usually just wishful thinking on the part of the client or something that HR said they have to include. For example, tell me why you think a DBA needs to have a Master's degree in rocket science to handle an accounting database for a health insurance company.

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

Helpful Links:
How to post code problems
How to post performance problems
Post #628505
Posted Thursday, January 1, 2009 10:06 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, June 8, 2016 7:26 AM
Points: 276, Visits: 566
I agree it is a nice to have industry experience, but absolutly not necessary.

Further I think single industry experience is a detrement. For example in healthcare (At least in the federal and state hospitals I work in), we are so far behind other industries, that if your scope is so narrow as to only include healthcare, you are missing out. And people with only healthcare experience tend to put blinders on and not think outside the healthcare box. I believe this is the main reason that MUMPS and Cache are still kicking in the healthcare industry (and retarding our data analysis and research efforts!).
Now if only I can get the directors to understand this concept - unfortunatly they to have been trapped in 1 industry so they don't see any issues.

I've worked in several industries and I see the same mistakes made over and over and solutions that could easily be adapted are dismissed as not relevant.

Expand your horizons, look to other industries for solutions and start thinking outside the box!

Post #628598
Posted Friday, January 2, 2009 2:47 AM



Group: General Forum Members
Last Login: Wednesday, October 19, 2016 9:30 AM
Points: 2,375, Visits: 860
I think the only way to answer this question is if you can identify what kind of DBA you are and what kind of environment it is.

I've consulted for many years and gone into retail businesses , banks, government , industrial, commercial etc without any requirement for business knowledge

but as you approach the more senior positions within your IT career then indisutry knowledge will help you make that jump up a notch. - Employers will be more excited (and comfortable) about employing you if you have worked for a major rival and you can bring something to the business that a rival does well but you don't....(especially if they are paying over the going rate for a DBA)

This doesn't really apply to production DBA's so much as developement DBA's where understanding business logic without being told and understanding the terminology of the business and being able to translate that into tables and procs is crucial for effective and fast working if you want to hit the floor running ....

even so - production dba's might want to gain experience in large and small organisations, where the challenges are different - for example hiring a DBA who had 10 years experience in a small business, while skilled and experienced may not be used to working with a team of DBA's and 400 servers...

Post #628657
Posted Friday, January 2, 2009 2:56 AM

SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Wednesday, February 2, 2011 2:54 AM
Points: 28, Visits: 17
I agree that industry or sector experience is far less important than technical ability unless you are facing off directly against the user community, which is rarely the case in DBA and developer roles. A technically able person will pick up the industry stuff as they need it.

Far more important these days, with the decline in in-house bespoke development, is experience of package and system integration.

Of course, it has always been tough establishing your technical credibility in an IBM mainframe shop without some years served under your belt.
Post #628662
Posted Friday, January 2, 2009 5:53 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, January 8, 2009 11:02 AM
Points: 3, Visits: 16
I believe industry experience to be the interview deciding factor but there has to be more opportunities for new CS graduates. Everywhere I go there are one-to-many offshore H1B visa holders taking jobs that could be given to inexperienced graduates coached by mentors. Colleges are increasingly looking for 'real world' professsors who can share 'real world' experiences and creating courses that culminate with 'real world' projects. I am very concerned about the dwindeling CS major rate and the hopelessness that pervades through the newbie software development community about finding any job, even internships.
Post #628738
Posted Friday, January 2, 2009 6:07 AM
Say Hey Kid

Say Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey KidSay Hey Kid

Group: General Forum Members
Last Login: Wednesday, February 2, 2011 4:11 AM
Points: 671, Visits: 356
I've seen job postings that state "industry experience" required, especially related to financial industry jobs. I agree that data is data, and industry experience shouldn't be required. If the job description sounds really interesting, then I would apply for the job anyway.


Post #628744
Posted Friday, January 2, 2009 6:13 AM



Group: General Forum Members
Last Login: Wednesday, July 8, 2009 10:04 AM
Points: 107, Visits: 156
My experience as I move across industries has been that the only "must-have" that is often non-negotiable is a degree, and that has been because at some point in the past someone in the organization's HR has said "everyone above pay grade 123 must have a degree" (of course usually they don't care about a "relevant" degree, and you have Vice Presidents and DBA's with basket-weaving degrees just to check the box off on the application).

Another relevant side discussion is the fact that their is no degree directly aimed at turning you into a DBA - if you want to be a coder, get a CS degree; if you want to be a DBA (or a server admin), get some degree you like so you can check off the box. Business and MIS degrees are useful, but they still aren't "DBA degrees" like CS is for coders or engineering is for engineers.

I find as I have moved from Education to Market Research to Banking/Finance to Healthcare that the industry specific piece of the job is very quickly picked up - as the original editorial says, the much larger (and more important) part is the technical specifics that any DBA worth their salt can dive into w/o knowing anything about the industry...along the lines of: "I don't care what this database does, but I can tell you're missing the key indexes on these three tables that would actually allow these poorly written stored procedures to work."

Post #628749
Posted Friday, January 2, 2009 6:28 AM


Group: General Forum Members
Last Login: Monday, September 22, 2014 4:27 AM
Points: 14, Visits: 101
I can see an argument both ways. While it is true that
data is data
, not all DBA and or SQL positions are specifically geared towards trawling through stored procedures and code. There are positions that require the domain knowledge of the sector in question due to data mining. There are tasks such as prediction models and applications that require one to be able to identify which data should be weighted higher or lower.

In many scenarios it can certainly boil down to what the exact job role will be. If they need one to maintain a database architecture, the inherent objects, and optimize performance then yes the argument that data is data certainly makes sense. If job role is to begin working on neural networks and prediction modeling, from a database developer or dba perspective, then domain knowledge of the industry is a valid requirement.
Post #628760
Posted Friday, January 2, 2009 6:28 AM



Group: General Forum Members
Last Login: Today @ 3:45 AM
Points: 17,172, Visits: 32,133
It has to be a "nice to have." Most of the time, your statement of "data is data is data" is just too true. My experience has been reasonably wide across various industries (I think) and I haven't had too many issues ramping up on the new set of business requirements. After all, just because you know insurance doesn't mean that you've got an instance understanding of some new set of business requirements that have occured because of a change in the law or moving into new territories in a new country... Any of these situations will require you to learn the new concepts and determine storage models, code, etc., to meet them.

"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 Query Performance Tuning
SQL Server Execution Plans

Product Evangelist for Red Gate Software
Post #628761
« Prev Topic | Next Topic »

Add to briefcase 12345»»»

Permissions Expand / Collapse