> 8 Duke Dollars an hour.
You are lucky then; when I was young they'd chain us to our desks which
was a smelly old log actually and we had to work 29 hours a day and
we had to *pay* our employer for it. But we didn't complain ...
kind regards,
Jos (those were the days ;-)
> > ** the dull, silver star-holders
>
> Your star looks kinda tinny to me, while my star is
> really woody. A nice
> and woody star! :-P
>
> kind regards,
>
> Jos ;-)
That's probably because you're still using EGA. Perhaps it's time to upgrade?
; )
> > Your star looks kinda tinny to me, while my star is
> > really woody. A nice and woody star! :-P
>
> I think your star looks like cheap tasteless beer. :)
You must've been drinking something really naughty that affects your
eyes badly ;-)
kind regards,
Jos (< no glasses needed, I drink 'em straight from the bottle)
> I don't think Auggie would be pleased with that
> thinly-veiled derision, my friend. ;)
That's okay; I'm not particularly pleased with Auggie's wares*, despite their rampant popularity among the tasteless class. ;o)
~
* He's certainly a nice fellow, though. Beautiful office, too.
> You must've been drinking something really naughty
> that affects your
> eyes badly ;-)
It might have affected my eyes, but Guinness is good for you:
http://news.bbc.co.uk/1/hi/health/3266819.stm
Do also note that they once advised pregnant women to drink Guinness. :)
There is huge deference in countries as per as salary is concern
Salary negotiation doesnt matter
Like beginner are getting $500 / month normally in the country I belong
And if u ll compare it with usa u ll figure out a huge difference.
Thats the reason y software organizations are moving to other countries in search of low cost labor
> > I don't think Auggie would be pleased with that
> > thinly-veiled derision, my friend. ;)
>
> That's okay; I'm not particularly pleased with
> Auggie's wares*, despite their rampant popularity
> among the tasteless class. ;o)
That 3.5% (v/v) is not too endearing, either.
Try a Fuller's ESB if you can get your hands on one. The distributer in my neck-of-the-woods no longer carries it- maybe you will have better luck.
> > > I started out on $35k a year in Pennsylvania,
> USA.
> > In Pennsylvania? Where Scranton? Harrisburg?
> > Williamsport? Pittsburgh?
> > hiladelphia?
>
> Pittsburgh.
>
> I imagine it would be closer to $50k entry level
> around Philadelphia.
I'm a-guessin' closer to 40K-45K USD but maybe Kel will chime in.
> There is huge deference in countries as per as salary
> is concern
Small correction- difference, not deference.
From Merriam-Webster
Main Entry: deference
Pronunciation: 'de-f&-r&n(t)s, 'def-r&n(t)s
Function: noun
: respect and esteem due a superior or an elder; also : affected or ingratiating regard for another's wishes
synonym see HONOR
> Try a Fuller's ESB if you can get your hands on one.
My current wheat beverages of choice are the Boulevard unfiltered (distributed out of KC) and a local Bock (chock full of malty caramel goodness). My tastes run more to the malt than the hops. I'm not much for IPAs/bitters/etc.
~
> > Try a Fuller's ESB if you can get your hands on
> one.
>
> My current wheat beverages of choice are the
> Boulevard unfiltered (distributed out of KC) and a
> local Bock (chock full of malty caramel goodness).
Aah, let's hoist a nice Dunkels Weibier (or two)!
> > I imagine it would be closer to $50k entry level around Philadelphia.
>
> I'm a-guessin' closer to 40K-45K USD but maybe Kel will chime in.
*CHIME*
Well, without saying a number just yet, I'd like to ask for an opinion. Here's a thinly-veiled scenario:
Let's say that a certain major software company (many years ago) pays a starting salary of 37-40K for a new graduate with no experience and no government security clearance (which is required for this job and can take over a year to get).
Fred is hired as an summer intern while working towards his CS degree. He has no clearance or experience. He is well-received and is asked to stay permanently. He accepts at 30K.
Fred gets outstanding reviews each year and is highly regarded by the customer for the project on which he works.
By the time Fred get his degree, the starting salary for a new grad is now 47-50K. At this time Fred is making 47K. He sees his fellow graduate Barney (same degree) starting at the same company, same job, different department for 49K. Barney has no experience or clearance.
Fred feels slighted. Also, Fred knows that some of his colleagues are making over 100K. Collegues who write this:
http://forum.java.sun.com/thread.jspa?threadID=5132065&messageID=9475805#9475805
Today, Fred has 8 years of experience and makes 57K. His yearly reviews are consistently outstanding.
Would you consider Fred to be grossly underpaid for a Java developer in the Philly area?
Side note: I considered using Tom & Jerry has the fake names, but I didn't want to come off as childlike ;-)
> Fred shows a lack of ambition and probably deserves to be underpaid as a result
Perhaps a bit glib there. I'll try to take that as constructive criticism. I'll also assume that you believe I'm underpaid.
For what it's worth, I never really had a ballpark idea of other salaries until recently. I still don't know any exact numbers for certain, since it seems to be a "don't ask, don't tell" topic around here. Also, while other folks have been getting 2-5% pay increases each year, mine have been somewhere around 6-10%, which seemed to calm the flames at pay raise time.
Although I always felt underpaid, I didn't have anything concrete to go on until a friend recently showed me Software Developer Magazine article (Fall of 2005 I think) about average salaries by title, experience, location, and such.
Thanks for the reply, YoGee.
> > > Side note: I considered using Tom & Jerry has the
> > > fake names, but I didn't want to come off as childlike ;-)
>
> > I'd had liked the story better if you'd used
> > Tweetie Bird and Magilla Gorilla for pen names ;-)
>
> I had you pegged for a Stan & Loretta kind of guy.
Definitely not Sir, I'm more like a BamBam & Pebbles type of guy.
kind regards,
George Jetson ( > vooooom!)
> I'll also assume that you
> believe I'm underpaid.
Actually I have no idea what the going rate is for programmers in the Philadelphia area. But if graduates are coming in at 47-50K, and Fred has 8 years experience and is being paid 57K, something is wrong there. I might have misread but it seems like Fred has been with the same company for 8 years? That is an awfully long time to be in your first job. If Fred had more ambition he would think "there are guys earning over 100K here are they aren't even that good, I could do that" and go and look for another job. The fact that Fred hasn't done this suggests he has gotten too comfortable in his current position, hence the lack of ambition comment.
> > > I want to know how much java programer will get
> > > payed. I am beginner.
> >
> > Tuppence haypnee.
>
> Life has gone to heck post-decimalisation.
Those Celts know nothing with their sexagesimal mumbo-jumbo.
So there.
kind regards,
Jos ;-)
(comments in relation to KelVarnson's story)
1. You have run up against what I consider to be the great conundrum of the workplace. Once a company has their hooks into you there really is not much of a reason for them to give more than a token increase. Think about it this way, to maximize their profits it's in their best interests to push down on the payroll entire.
2. The surest way to increase your pay is to change jobs. companies are more willing to part with money for the new guy rather than the guy they have. It's kind of silly really because the guy they have is a known quantity whereas the new guy is very much an unknown.
The problem is that the market is constantly changing. Six months from now the going rate for a particular skillset and experience level will not be the same as it is now. Thus logic tells us that the six months spent on a job should be payed the same as the market right now. However it doesn't work that way and to understand why we have to look at it from an economic standpoint.
Consider yourself to be a product for sale in a market. Your market value is established at the time that you are sold in the market. Once you are sold you are no longer part of the economy as a product. You become a resource to the company that you were sold to. Your market value is only recalculated if you reenter the economy by looking for a new job.
Now in regards to getting degrees, training etc. Any time someone has completed a degree or training (as long as the company didn't pay for it) it's a great time to go hunting for a raise. Bear in mind though that th elusive raise beast is tricky and hard to catch sometimes. Be prepared with plenty of ammunition (documentation of achievements is good) to help trap the raise beast.
Good communications with managers is very important. A person who does their job well but isn't distinguished from the others by anything other than that they do their job will often go unnoticed because of their personality and nature rather than because of their performance.
Ok I've rambled on for a while, but ultimately it comes down to this, we are all consultants whether we work for a company in an in house development group or whether we roam the countryside dealing with clients. We are all consultants and as such it's our responsibility to negotiate our compensation, we cannot count on the company to recognize our greatness and reward it just 'cause.
Just my thoughts on the subject, your milage may of course vary.
PS.
> I might have misread but it seems like Fred has been with the same
> company for 8 years? That is an awfully long time to be in your first job.
Really? I'm curious to hear other opinions on this. It seems like most of the people here have been here for a very long time. Of the few who leave, most come back. Eight seems like nothing to me.
> If Fred had more ambition he would think "there are guys earning over
> 100K here are they aren't even that good, I could do that" and go and look for another job.
The 6-figure folks have been working for here for 20+ years. Coming from my first job (a union, non-IT job) of 15 years, this was a big factor in your salary.
> The fact that Fred hasn't done this suggests he has gotten too comfortable in his current position,
It might also suggest that, in my first IT job, I haven't seen evidence that it is the norm to have moved on after 8 years. It's more like Jurrasic Park around here (lots of dinsaurs).
I do appreciate you input, YoGee, and welcome others.
> I want to know how much java programer will get
> payed. I am beginner.
For people who have to resort to asking this kind of question on a forum like this, I'd say your salary will probably be around minimum wage wherever you get a job.
Oh, and for you it might involve java, but not programming - just serving it, or soda.
> > I might have misread but it seems like Fred has
> been with the same
> > company for 8 years? That is an awfully long time
> to be in your first job.
>
> Really? I'm curious to hear other opinions on
> this. It seems like most of the people here have
> been here for a very long time. Of the few who
> leave, most come back. Eight seems like nothing to
> me.
I agree. Time in a single job in this industry seems to be much smaller then others.
In fact I would refer you to puckstopper31's comments. Most of them seem to be right on with what I have experienced.At most jobs, creeping up the totem poll is a slow process, but changing jobs can give you big jumps. (But I think this is especially true for the first job because you start at the bottom).
Good points, puck.
> Now in regards to getting degrees, training etc. Any time someone
> has completed a degree or training (as long as the company didn't
> pay for it) it's a great time to go hunting for a raise.
Ahh, but they DID pay for it. My 12-month post-degree window closed last summer.
Without getting too explicit, I do have a standing offer from the aforementioned customer, albeit an informal one ("whenever you feel like you want a change, we'd love to have you" kinda thing). I plan on pursuing this next month.
> Bear in mind though that the elusive raise beast is tricky and hard to catch sometimes.
> We are all consultants and as such it's our responsibility to negotiate
> our compensation, we cannot count on the company to recognize our
> greatness and reward it just 'cause.
Any ballparks about what is considered a reasonable raise? By that I mean, do employers tend to look at a potential raise as a percentage mark-up of the current pay, or just as a bottom-line whole number regardless of current pay. Example, Mary makes 40K but feels confident that her skill set and experience should put her at 60K (and let's assume that she's right). Mary does the march-in. Is an employer going scoff at a 50% pay raise (which sounds enormous), or will they tend to look at the 60K as being in a reasonable ballpark? Obviously, there are no absolutes. I was just wondering to hear any war stories.
> The 6-figure folks have been working for here for 20+
> years. Coming from my first job (a union, non-IT
> job) of 15 years, this was a big factor in your
> salary.
I would stop thinking in terms of years of experience and start thinking in terms of skills. Knowledge of the latest and greatest API's and tools means a lot. Just because you have less years experience than some other guy that doesn't mean you can't earn more money than them!
> Good points, puck.
>
> > Now in regards to getting degrees, training etc.
> Any time someone
> > has completed a degree or training (as long as the
> company didn't
> > pay for it) it's a great time to go hunting for a
> raise.
>
> Ahh, but they DID pay for it. My 12-month
> post-degree window closed last summer.
>
> Without getting too explicit, I do have a standing
> offer from the aforementioned customer, albeit an
> informal one ("whenever you feel like you want a
> change, we'd love to have you" kinda thing). I plan
> on pursuing this next month.
>
> > Bear in mind though that the elusive raise beast is
> tricky and hard to catch sometimes.
>
> > We are all consultants and as such it's our
> responsibility to negotiate
> > our compensation, we cannot count on the company to
> recognize our
> > greatness and reward it just 'cause.
>
> Any ballparks about what is considered a reasonable
> raise? By that I mean, do employers tend to look at
> a potential raise as a percentage mark-up of the
> current pay, or just as a bottom-line whole number
> regardless of current pay. Example, Mary makes 40K
> but feels confident that her skill set and experience
> should put her at 60K (and let's assume that she's
> right). Mary does the march-in. Is an employer
> going scoff at a 50% pay raise (which sounds
> enormous), or will they tend to look at the 60K as
> being in a reasonable ballpark? Obviously, there are
> no absolutes. I was just wondering to hear any war
> stories.
From my experience, someone who is hired at entry level, and continues to do the same job (albeit perhaps better with given experience) will run into issues with an employer who knows they can easily get another entry level person for the same (40k from your example) rather than give a pay raise to the existing resource. If Mary is serious about bucking for a raise, it is in her best interst to do the "march-in" with a 60k offer in hand to negotiate with (assuming she wants to remain in the same position). Worse case, she gets what she feels she's worth, but has to leave a known position for something new.
Also from my very recent experience, performance reviews are meaningless. They are an HR tool to assist them meet company goals, they have very little to do with your (Mary's?) percieved value.
I would also state that company loyalty is misplaced (I'm almost 10 years in my first "real" job and am just finding this out). They are not in business to make you or Mary happy. Brush up Mary's resume and test the waters. The worst Mary will discover is that she is not underpayed and/or not as experienced/valuable as she thought. At least she'll know where she stands.
My two....
> > The 6-figure folks have been working for here for
> 20+
> > years. Coming from my first job (a union, non-IT
> > job) of 15 years, this was a big factor in your
> > salary.
>
> I would stop thinking in terms of years of experience
> and start thinking in terms of skills. Knowledge of
> the latest and greatest API's and tools means a lot.
> Just because you have less years experience than some
> other guy that doesn't mean you can't earn more money
> than them!
That all really depends on the organization you work for too!
I have seen it go both ways. I have seen COBOL programmers who dont have a degree and 25 years experience refuse to learn any new technologies making 6 figures at company A and then programmers with impressive skillsets in modern technologies with less than a year experience but a masters degree making scum-sucking wages at the same company.
I mostly see this stuff at LARGE organizations where the people in charge are far removed from the developers, where experience and years of servitude matter the most to the managers.
Fresh new companies tend to award based on skills and performance.
IMHO.
> Any ballparks about what is considered a reasonable
> raise? By that I mean, do employers tend to look at
> a potential raise as a percentage mark-up of the
> current pay, or just as a bottom-line whole number
> regardless of current pay. Example, Mary makes 40K
> but feels confident that her skill set and experience
> should put her at 60K (and let's assume that she's
> right). Mary does the march-in. Is an employer
> going scoff at a 50% pay raise (which sounds
> enormous), or will they tend to look at the 60K as
> being in a reasonable ballpark? Obviously, there are
> no absolutes. I was just wondering to hear any war
> stories.
You need to look fo a job. Figure out where to look as well (are you willing to relocate.)
Once you have one or more offers that sets the baseline (if relocation then you need to calculate cost of living.)
You then decide if you want to negotiate with your current employer. You should use the offers you have to set an amount that you are willing to accept.