How to not get a response from a job post
-
Like most of you probably out there I get a ton of letters from recruiters every day. Sometimes they make sense and I take a look, maybe even respond. But more often then not I get job descriptions that are contraditary and vague. I recently recieved this one and wanted to share it with you...recruiters take notes on what NOT to do here...
The Senior Database Developer will be in a unique position to elevate the quality of information available in the organization by seeing beyond initial requirements and across traditional line-of-business boundaries. The position is a member of a team of dedicated SQL Server professionals responsible for database integrity, security and performance.
Okay, looks harmless enough right? Except when has it become the developers job to handle integrity, security and performance? These are all DBA tasks. I know most Sr. developers and anyone that has worked in a smaller shop can handle some of these tasks but from reading this I immediately get the impression whoever posted it either copied it from someone else or they have no clue what they are talking about
Skills:
'Excellent OLTP data modeling and advanced T-SQL development skills are required.
'SQL 2005 experience is desirable but not required.
'Database Administration and Data warehousing are not significant components of this position.
'Testing and source code management skills are expected.
SQL Reporting, MDX (a syntax for querying multidimensional data in SQL Server) or CUBE (SQL Server 6.5 includes two extensions to GROUP BY'"CUBE and ROLLUP'"that let SQL Server optionally generate aggregate groupings in a single query)."
Okay so the requirement aren't too off their rocker except there are some things here that don't make sense. Like...if Admin work isn't a key part of this position, why would their primary responsibilities be that of a typical DBA?
Then it says that Data Warehousing isn't important but MDX is...ummm...okay so lets see, that would be like saying you don't have to know how to steer the car just push the gas pedal :-/
Also one thing I see all over the place is 'OLTP Modeling' and often are asked that by recruiters just to find they have no clue what they are talking about and are just reading their sales script, i mean interview question. This one I could see being it a Sr. development position you would probably have some good experience with modeling but this is really an Architect's job.
Sorry for the rant but sometimes it seems that every single job posting out there is like this. I think we should create a new standard for job descriptions, like a web form where companies can pick out skills they want so they don't have to actually think about the requirements.
/rant
Cheers,Ben Sullins
bensullins.com
Beer is my primary key... -
Actually I like this. It tells me who not to go to for a job. Kind of recruiting Darwinism
-
The only issue I have with your otherwise valid complaint is that in the SQL Server world, far more so than in the Oracle world, there is often a need for "hybrids". Many smaller companies aren't going to have separate DBA/Dev/Architect positions, so they really do need a good combination of skills. You'll also find that there are many individuals that are perfectly capable of performing these disparate duties by themselves. You'll even find that many of us have been the defacto IT department, which means we do everything from coding apps with backends that we've modeled, to pulling out the crimper to create a "straight=through" cable as the need arises, and then fixing that printer jam over lunch.
With that said, I agree that the requested required skills often don't seem to match with what the job description implies that they would be.
-
Some of my favorite ones are the ones that say "5+ years SQL 2005 experience"...gotta love that.
I agree w/ your point about the hybrid roles, in almost every company I have been at I have had to wear many hats...
Cheers,Ben Sullins
bensullins.com
Beer is my primary key... -
I'll tell you another way not to get a person's attention is to send an email about "job possibilities" and then ask all kinds of personal questions before you've said much about the job. Sorry folks, but I'm not in the habit of disclosing my current salary, my desired salary, a list of references, my thumb print and a DNA sample before I know what is on the table.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply