Look folks, we’ve been down this road before. Apparently some of you are still not getting the message because I continue to get some really, really awful DBA job descriptions.

My post about a better job description for everyone was a cut and paste from a job description that had been sent to me five times previously. I rejected the offer each and every time, and even provided feedback on the description in an effort to help make things better.

To my utter shock I found a colleague of mine had taken the job even after I blogged about the description. As it turns out, the person(s) who wrote that description went back and updated it to make improvement in order to attract the right person, and they did! They are happy, my friend is happy, and I was blown away that my little blog here had that much positive impact on everyone involved.

So last week I got another horrible job description. I’m going to post it for you here. I’m not going to pick it apart like last time. I don’t think I need to nitpick like before. So why am I posting this? Because I hope that the person who wrote this description will recognize it here and read my previous post about how to write a better job description for everyone.

Overview:

The Database Administrator’s role is to design, install, monitor, maintain, and performance tune production databases while ensuring high levels of data availability. This individual will work closely with the [redacted]-based software development and support team to develop, implement and oversee database policies and procedures to ensure the integrity and availability of global databases and their accompanying software. This position will report to the [redacted] Project Lead.

Responsibilities:

  • Has 7 or more years of experience in database development and support in MS SQL Server environments.
  • SQL Development – ability to write and troubleshoot complex SQL Code and design ( stored procs, functions, tables, views, triggers, indexes, constraints ) using modern techniques.
  • Extensive and advanced knowledge of TSQL language.
  • Ability to analyze SQL execution plans and understand the component parts.
  • Willing and able to learn the insurance business including gaining a working knowledge of financial related data loads as well as other operational uses of the data.
  • Ability to evolve to become a subject matter expert of the databases used by the applications
  • Strong experience in Database Administration in SQL Server ( 2005, 2008 )
  • Knowledge of SQL Server 2012 features, improvements and upgrade issues in preparation for upgrades to the new version company-wide next year.
  • Working Knowledge of SSIS. Practical experience preferred.
  • Experience in troubleshooting and resolving database integrity issues, performance issues, blocking and deadlocking issues, replication issues, log shipping issues, connectivity issues, security issues etc.
  • Experience in Performance Tuning, Query Optimization, using Performance Monitor, SQL Profiler and other related monitoring and troubleshooting tools.
  • Ability to detect and troubleshoot SQL Server related CPU,memory,I/O, disk space and other resource contention.
  • Strong knowledge of backups, restores, recovery models, database shrink operations, DBCC commands, Clustering, Database mirroring, Replication.
  • Expert experience in implementing operational automation.
  • Strong knowledge of how indexes, index management, integrity checks, configuration, patching. How statistics work, how indexes are stored, how they can be created and managed effectively.
  • Knowledge of SQL Server tools ( Profiler, DTA, SSMS, SAC, SSCM, PerfMon, DMVs, system sprocs)
  • Solid acquaintance with windows server, security delegation, SPNs, storage components.
  • Documentation skills for processes and procedures ( creating KBs, runbooks, topology etc )
  • SQL Database Operational support to tech users
  • Solid acquaintance with windows server, security delegation, SPNs, storage components.
  • Documentation skills for processes and procedures ( creating KBs, runbooks, topology etc )
  • Knowledge of 3rd party DBA tools and applications ( e.g redgate, idera, SCOM, Erwin )
  • Application release management duties including: test environment maintenance, backups/restores, database change management and propagation between test environments and to production. Execution of scripts against test and production database as required
  • Data mining for the business and other parties as needed

OK folks, let’s see if you’ve learned anything from my previous post: what are the issues you see above?