The new posting is a lot cleaner.
From a purely personal perspective, when I see requirements like this:
• Experience working with Windows server, including Active Directory and proper disk configurations.
• Experience using MS SCOM for SQL monitoring and alerting.
These IMHO, are not a DBA's direct responsibility. If the posting said something like "Understanding Windows Server, AD, and disk ... and can provide expertise blah, blah, blah, then I would have been less turned off.
To me, the DBA should be able to articulate requirements to the persons in charge of these areas, and work with them to make sure that these things are configured properly.
With that being said, I have a somewhat negative view of things based upon past experiences. I have had been a part of some very immature IT departments in the recent past. There wasn't a lot of understanding within the departments of mission critical things.
For example, the SAN administrators experience consisted of taking a 2 day class! That's it. It's the only understanding of disks/sans that he had!
I spent more time teaching him about SANs as opposed to doing DBA work.
Additionally, when I look back at interviews and the companies I have interviewed with, the better positions seemed to have very short and to the point postings. The posting for my new position was three paragraphs. The first was two sentences about the company, the second was 6 sentences about the position, and the last was three sentences on how to apply. The "details" were purposely kept to a minimum because they wanted to weed out the candidates who could study up on a listed subject, without any real knowledge, and still sound good in an interview.
Michael L JohnIf you assassinate a DBA, would you pull a trigger?
To properly post on a forum:http://www.sqlservercentral.com/articles/61537/