DBA in PHX
-
I Need a DBA
This job is in east Mesa, AZ (suburb of Phoenix). The ad as it ran in the paper looks like this:
Requirements:
· Three to five years of working experience as a database administrator using SQL Server (version 7 and/or 2000) is required. SQL Server in a NT/2K environment.
· Experience with backup/restore/recovery, SQL, stored procedure and trigger development, tuning, enterprise data modeling and schema change management
· Experience implementing and tuning physical and logical data models.
· In-depth knowledge of SQL Server and Windows operating systems.
· Working knowledge of network connectivity and interpretabilities of multi-platform environments (NT,2000, Unix...).
· Excellent communication skills to work with application development team to review data requirements and usage of the data model and tools.
· T-SQL experience
· SQL Server clustering experience a definite plus
Preferential treatment:
· minimum 2 year degree
· Erwin modeling and data design.
· Application programming background utilizing SQL Server
I need someone who can hit the ground running. If you don't know 3 ways to optimize speed on the server, don't apply, because I will be very short-tempered with you in your interview. I can not sponsor visas, and we likely won't pay relocation costs.
Interested? If so, email your resume' to me at sql_dba_job@ypcorp.com. Text or MSWord format, please.
-
This was removed by the editor as SPAM
-
I will be very short-tempered with you in your interview? What do you mean by that? perhaps there is more than 50+ ways to optimize.
Shas3
-
how much $$$$$$ whats the range ?
-
Dear eljeffo,
Thank you for your offer letter. I accept for the agreed 115K plus travel and relocation expenses.
I cannot however put up with anyone getting angry so the terms of the contract will have an anger management clause giving me full right to terminate services at anytime should the environment become too hostile.
I look forward to our meeting next month.
Yours truly and sincerely,
John Zacharkan
Edited by - zach_john on 06/16/2003 08:47:01 AM
John Zacharkan -
Kingram:
for Jr. level people the rate would likely be in the range of $45 - 60k / yr, and for Sr. level between $65 - 80k / yr
Zach, sorry, but you don't meet our qualifications. While I can appreciate a certain amount of "sack" in an interview, I don't need any more loose cannons in my department.
-
Hi eljeffo,
quote:
for Jr. level people the rate would likely be in the range of $45 - 60k / yr, and for Sr. level between $65 - 80k / yrsorry for hooking into this thread. But just out of curiosity, is this some kind of average earnings for a senior dba?
If so, hmm...I should seriously consider changing job
Cheers,
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url] -
a5,
It's an average here...
-
quote:
It's an average here...hmmmm....thank you, I think it's time to consider really seriously some changes in my 'career'
Cheers,
Frank
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url] -
I am sure you didn't mean it, but you really come across as someone who people would not want to work for, especially for those low salary numbers.
I wish you good luck in finding someone that allows you to treat them poorly, due to your lack or patience and obvious people skills.
-
As I saw in another posting set, the data guys outlined what they really wanted, and the people that would fit with that group likely responded. As far as "low salary numbers", this market is saturated with DBA's and D/A's right now. While I understand the desire for HR to keep the salary really low, I don't agree, and that's why the numbers are UP where they are. We are offering a fair amount for this market.
I also understand that there are a lot of ways to optimize speed. I was looking for a few good ones. Most of the applicants I had so far that couldn't list anything beyond "um, add more RAM" (which is one valid way) were not qualified, but were hoping to luck into the gig.
So, I stand by my decision to list the positions in the manner that I did. The intention was to weed out the people who really didn't know at least 3 ways to optimize query speed. Also, only 1 of the respondents to this posting (who will be interviewed) knew to move the MDF's, LDF's, and tempdb to separate devices... is that method that much of a hidden trick?
Anyway, to those who are responding and qualified: thanks for your attention, and keep it up. To those who are derisive of the posting: whatever. To the rest: thanks for reading.
-
eljeffo,
apologies if you didn't like the responses. We do moderate some posts if we think they are flames. Keep in mind your post is kind of "in your face" and understandably some people didn't like. As someone who's hired people, I can appreciate lack of desire (and lack of time) to interview unqualified people.
Hope this wasn't a bad experience and you'll continue to come back ot the site. Apparently none of your interviewees spend much time here
Steve Jones
-
Steve,
I'm not offended, and I use the forums daily. That won't stop.
There are a few billion people on the planet, and all have different opinons, and each person thinks theirs is the best one. Those with similar opinions congregate, and those with different ones congregate elsewhere.
No offense intended, and none taken.
Jeff
-
Improving performance is a broad topic.
Based a recent MS workshop I attended, they would tell you to investigate memory, IO, then CPU, in that order if you have issues. Of course, performance needs to be quantified, either in terms of throughput or response time or both. In my experience, internal server drives are not the best compared to external arrays. How the disk controllers are configured can also make a big difference in what you are seeing.
Viewing 14 posts - 1 through 13 (of 13 total)
You must be logged in to reply to this topic. Login to reply