Yeah I've noticed the same. There's a DBA I know with 12+ years "experience" but I still rate him as being junior level although his position is obviously Senior DBA now. I think a problem with it is that most/all companies almost never demote anyone. The worst that ever happens is a stagnant salary or a job role change but not going from "Senior DBA" to "DBA" with an appropriate pay cut. I think if such demotions were more easily enforced then people would be less likely to rest on their laurels for so long. Regards, Mike ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx <oracle-l-bounce@xxxxxxxxxxxxx> on behalf of Iggy Fernandez <iggy_fernandez@xxxxxxxxxxx> Sent: 11 September 2014 23:00 To: Kumar Madduri Cc: oracle-l@xxxxxxxxxxxxx Subject: RE: Definition of Top Class DBA The problem is that everyone in the team is already billed as a "senior DBA" after one or two years on the job because (understandably) no one is satisfied with the "junior DBA" or "DBA" title. Therefore we need inflated titles like "top DBA" or "DBA architect" but all they really mean is "truly senior DBA" :-) Kindest regards, Iggy Senior DBA "Been there. Done that." ________________________________ Date: Thu, 11 Sep 2014 13:07:55 -0700 Subject: Re: Definition of Top Class DBA From: ksmadduri@xxxxxxxxx To: iggy_fernandez@xxxxxxxxxxx This has been a great discussion and good learning. But the original reason why I asked was, I kind of get upset when even technical DBAs/technical managers say they need Top DBAs. That too me is kind of vague. You could be Top DBA where you are but not Top DBA at 'xyz corp'. So I would rather post for a job with the skills I am looking for rather than putting unneccesaary adjectives. The guy/gal who thinks they are 'Top DBAs' usually post these postings :) (other than HR guys of course and I dont blame them because they dont have expertise).