Re: title

  • From: Guillermo Alan Bort <cicciuxdba@xxxxxxxxx>
  • To: shrekdba@xxxxxxxxx
  • Date: Sat, 1 Oct 2011 10:12:06 -0300

I don't think comparing your salary to others' is a good way to measure it.
There's always going to be someone who's a better negotiator or who appeared
to know more than they do or that have some connections. I'm not saying
that's fair, but it is, so you might get a little frustrated and step on a
few toes if you try to increase your salary based on the premise "I do more,
so I should earn more". I know it's extremely annoying to find that someone
who can't really perform the task of a Sr. DBA has the same title as salary
as you, when half the team comes to you with questions ranging from "how do
I connect as sysdba in this windows environment" to "could you describe the
finer points of RAC architecture?"
I put forward, then, that while you should check the market mean for a DBA
on your city, comparing your salary to other members of your organization is
not a good idea, instead try to see if you can live comfortably and save
some money on your current salary. If you find that you need to struggle to
live as you want (hopefully you know how to manage your money and won't go
for any too extravagant) and save what you want, then you should ask for a
raise (and emphasize what you do right and not what others do wrong) or seek
a jump in your salary by changing jobs which as a DBA with your
qualifications should be fairly easy, though the current economy may not
allow for it.

Still Batman.

On Sat, Oct 1, 2011 at 7:49 AM, bill thater <shrekdba@xxxxxxxxx> wrote:

> The
> Bill "shrek"Thater
> Shrekdba@xxxxxxxxx
> sent from my phone
> From: Mike Haddon
> Sent: Friday, September 30, 2011 6:38 PM
> To: oracle-l@xxxxxxxxxxxxx
> Subject: Re: title
> Brian,
> I have seen the benefits of a title that is commensurate with your
> experience but,..
> Do you spend time with other team members just to help and maybe
> transfer some knowledge?
> Do you get one or more team members involved in an issue you are
> resolving because it's one of those that rarely occur and exposure to it
> will benefit his/her expertise and help them grow into REAL Sr DBAs?
> If you do at least that and never lose an opportunity to help them
> become better at what they do then there is no need for a title because
> the rest of the team knows who the real senior guy is. I title of SR DBA
> on the outside means the same, internally it means really nothing unless
> benefits and cash are better. Where do you go from Sr DBA??, maybe
> management?
> If you don't do at least that then I would suggest a change in strategy.
> Just my .02
> Mike
> On 9/30/2011 2:09 PM, Zelli, Brian wrote:
> > See, the problem is that because we are a public benefits corporation,
> one of the only ways you can get ahead financially is with a title change.
> > To answer some of the questions:
> >
> > I do have 27 years of IT exp and 17 years of DBA exp so I'm only a new
> guy to this org.  I have more years total than some of them.
> >
> > I know the platforms better than them.  They come to me with issues.  And
> none are in a managerial role.
> >
> > No ego.  Just looking to be compensated fairly.
> >
> >
> > ciao,
> > Brian
> >
> --
> --


Other related posts: