August 11, 2008 at 1:09 pm
From SQL_Server_Performance.com Peter Ward
One of the challenges that many organizations are facing is not just how to recruit staff but more importantly how to retain their existing staff. According to a recent survey by Gartner, over 50% of ICT employees have been employed with their current organization for less than two years. I am sure that if you look around your office there will be a lot of faces that were not there two years ago as well as a lot of missing faces.
The challenge for employers is identifying what motivates someone to stay in an organization. Even though salaries are higher than ever for database professionals, it is not necessarily money that motivates someone to leave an organization. Sure, an extra $50,000 is motivating but $5,000 may not be a motivating factor. Often $5,000 is not enough of a motivator, as there are potentially additional costs associated with a new work place such as parking costs or the additional cost of public transport. What a lot of people are starting to do is put more value on a role rather than salary alone by including items such as training or working with the latest technology. What motivates you to move employers—is it money alone or are there other factors that influence your decision?
Do the companies care to retain their employees? Is it easy to find a suitable candidate for the job? Is it easy for DBA or database developers to find a job?
It seems this is another chicken and egg question. I see there are companies have a hard time to recruit staff and on the other hand people complain there are no job around.
:ermm:
August 11, 2008 at 8:31 pm
The answer to the infamous "chicken or the egg" problem is... the egg. A chicken can only be a chicken... it is possible for an egg to become something else under the right conditions.
I, too, have seen a lot of people complain about there not being any SQL Server jobs... part of the reason is many employers think a GUI developer is enough to get the job done because SQL Server is "easy like Access or a spreadsheet". Then there's what some employers think a DBA should do... everything including running new cable to cubes and hanging new drywall. 😛
THEN, once you get a job, many people use overtime as a standard practice instead of planning correctly. Developers and DBA's don't have a problem with doing the occasional all night death march, but after two years, it get's a bit tiresome. That's why I have a commentabout "planning" in my signature line.
Last but not least... some developers/DBAs have to move... they've overloaded/lied on their resumes and can't keep up. :hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
August 11, 2008 at 9:59 pm
I think it's a bit of luck, timing, and location.
There are always jobs around, and there are plenty of places that do value staff and try to keep them. There are also plenty of places that treat people like disposable, easily-replaced resources.
The challenge is in finding the place that matches your skills, desires, needs, and situation.
August 11, 2008 at 10:17 pm
Heh... or taking what I said before... the challenge is to be the Egg and not the Chicken. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply