News for hackers. Stuff that matters.
Re:The Software Engineer’s Guide to Negotiating a Raise by meatysnapper on Tuesday June 30, 2015 @06:41PM (#9808872)
My career has basically gone this way:

60k shitty entry level job (< 3 years)... quit for a

90k slightly less shitty job (1 year) ... quit for a

140k + $350k bonus/equity (< 2 years) ... quit for a

160k + much more equity, nearly certain IPO (hopefully for the full 4 years to vest 100%)

Don't hate the mercenary, hate the employer who won't pay you what you are worth!

Re:The Software Engineer’s Guide to Negotiating a Raise by crpatino on Tuesday June 30, 2015 @08:40PM (#9809288)
> Don't hate the mercenary, hate the employer who won't pay you what you are worth!

I think you fail to see a fact, the same fact that was overlooked by all your former bosses actually.

Your 6-years-ago self was probably not worth half of what your current self is. Your ability to land each new job was built upon the foundations of higher skills and professional maturity you achieved on the previous job.

Ambitious, talented employees keep growing, positions are static by nature. Job hopping is the de-facto career path.

Re:The Software Engineer’s Guide to Negotiating a Raise by PirateDave on Tuesday June 30, 2015 @09:32PM (#9809516)
Is 160k common in SV for 6 years experience?

I'm in the L.A. area and people want to crap their pants when I tell them to give me 150k.

Re:The Software Engineer’s Guide to Negotiating a Raise by meatysnapper on Tuesday June 30, 2015 @09:03PM (#9809404)
I am definitely worth more now; I agree. Unfortunately:

1) Management in all but one job I've had invested nothing in training and helping new employees grow. My technical growth has come through personal projects and taking on extra work.

2) Promotion never offered anything like the salary increases a new job offered. The incentive to stay is not there.

Re:The Software Engineer’s Guide to Negotiating a Raise by lmm on Wednesday July 01, 2015 @06:44AM (#9811027)
> Your 6-years-ago self was probably not worth half of what your current self is. Your ability to land each new job was built upon the foundations of higher skills and professional maturity you achieved on the previous job.

I think employers massively overweight experience, particularly in a field that changes as fast as ours. Five years ago I was just as smart as I am now, maybe smarter - I didn't have 5 years' experience with tools X, Y and Z, but tools X and Y are already basically obsolete. But the market says I'm worth twice as much now as I was five years ago.

Re:The Software Engineer’s Guide to Negotiating a Raise by crpatino on Wednesday July 01, 2015 @12:29PM (#9813090)
You are not worth more because you know more technologies, though it is an unfair fact on this industry that there will be one or two over-hyped stacks at any time. But back to the point, you are worth more because you have been exposed to the social dynamics patterns that repeat themselves over and over in each new development process. You don't learn that kind of stuff hacking on your bedroom and open source contribution, while valuable, can only take you so far. This is, IMHO, as far as and objective reason to hire someone experienced as you will get.

Also, there is the concept of social proof - which you may argue is a form of over-weighting experience, but that's an open ended question. If you have a track record of going to work for somebody else and achieving X, Y, Z goals there, you are perceived to be a safer choice than someone that in theory might be smarter than you, but that is lazy or otherwise unreliable, or with low communication skills, or a first class jerk. Not that you cannot hire this types if you go with someone more experienced, but from HR perspective, you are more of a "known quantity" once you have been around for a few years and built a track record for yourself.

Re:The Software Engineer’s Guide to Negotiating a Raise by s73v3r on Wednesday July 01, 2015 @11:45AM (#9812653)
But you also have five years more experience in designing software, organizing code, debugging, etc. All things that are largely tool agnostic.
Re:The Software Engineer’s Guide to Negotiating a Raise by lmm on Wednesday July 01, 2015 @11:50AM (#9812693)
I have five years more "professional" experience, seems to be the difference - I had verifiable coding experience on open-source projects before that that would have demonstrated those skills. I've got more confident in my judgement but I'm not at all convinced that judgement has actually improved.
Re:The Software Engineer’s Guide to Negotiating a Raise by aswanson on Wednesday July 01, 2015 @11:30PM (#9816691)
Did your core languages change during each switch? What is your current stack/expertise?
Re:The Software Engineer’s Guide to Negotiating a Raise by lmm on Thursday July 02, 2015 @03:23AM (#9817323)
I stuck to the JVM (since people seem willing to pay more if you have experience on the specific stack, and my first job happened to be Java); for the last 3-4 years I've been doing almost exclusively Scala.
Re:The Software Engineer’s Guide to Negotiating a Raise by Chinjut on Tuesday June 30, 2015 @06:47PM (#9808901)
That was some jump from $90k to $490k! (How'd you pull that off?)
Re:The Software Engineer’s Guide to Negotiating a Raise by ceras on Tuesday June 30, 2015 @08:16PM (#9809214)
I'm surprised you found a near-certain pre-IPO company who gave you a lot more equity than $350k. Most options I've seen at that stage seem to consistently not even reach 0.1%, which is already much less than $350k for your typical IPO.
Re:The Software Engineer’s Guide to Negotiating a Raise by meatysnapper on Tuesday June 30, 2015 @08:23PM (#9809236)
To quote Zaphod Beeblebrox, "I got lucky".

These companies can be found, and you probably know their names. You can get through their interviews by adopting the mannerisms of their interviewers (be it old cynical guys, or Stanford new grads, or whatever) and studying your SAT interview question book.

The way to really strike it rich is look for say a social network with 30+ million active users that is willing to give you options. It's hard to fuck up 30+ million users.

EDIT: Just because I got lucky does not mean the OPs post is wrong. My luck was aided by me jumping ship as frequently as I could whenever a good new opportunity presented itself.

Re:The Software Engineer’s Guide to Negotiating a Raise by rev_bird on Tuesday June 30, 2015 @07:39PM (#9809090)
Echoing Chinjut's question – I've never seen a jump like that, unless it was equity that turned out to be worth $350k, but looked like less when it was offered. How did that happen?!
Re:The Software Engineer’s Guide to Negotiating a Raise by meatysnapper on Tuesday June 30, 2015 @07:51PM (#9809129)
Mostly equity; I joined a company the week of the IPO but accepted the offer before that. I basically got very lucky, but the base salary + equity any relatively big name post-IPO company would also be $200k-ish.

Keep in mind that I stayed at none of these companies for more than 2.5 years!

There were 2 brief interludes 1) Non-technical grad school, but that actually netted me a very slick summer internship one year that paid way better than my previous job too. 2) Failed startup, that paid nothing

Unfortunately, I think I've maxed out on the software engineer pay scale now unless I get even luckier.

Re:The Software Engineer’s Guide to Negotiating a Raise by hexedpackets on Tuesday June 30, 2015 @11:12PM (#9809876)
Those are awesome and I'm sure well-deserved jumps. However, you definitely have not maxed out on the pay scale, especially if you're in SF/NYC. To quote patio11:

> Pick a number, any number: somebody does a lot better than that. For most numbers you’d naively think of, its an awful lot of somebodies. $100k? Not the top. $250k? Not the top. $500k? … Not the top.

http://www.kalzumeus.com/2015/05/01/talking-about-money/

Re:The Software Engineer’s Guide to Negotiating a Raise by rev_bird on Wednesday July 01, 2015 @12:38PM (#9813154)
Thanks for the response. I'm not a developer (yet... heh), but I think I'm probably within sniffing distance of the top of the pay scale for my particular role. It's a weird feeling to know, "Welp, this is the end of big raises," but at the same time, I'm incredibly relieved by the thought that I could go my whole life without another pay bump, even for cost of living, and still be totally fine. I wouldn't want that, sure, but so long as I don't get myself fired I'll have everything I need. What a ridiculously lucky deal we've found.

The less emotional benefit of getting higher in the pay scale is that job-switches can be about something more meaningful than just, "Oh shit, that's more money!" Now, so long as I can get close, I'll be happy to just go wherever would be most fulfilling.

Re:The Software Engineer’s Guide to Negotiating a Raise by ranit on Tuesday June 30, 2015 @10:52PM (#9809819)
Maxing out is not considered "unfortunate" by most definitions of luckiness. :-)
Re:The Software Engineer’s Guide to Negotiating a Raise by s73v3r on Wednesday July 01, 2015 @11:47AM (#9812668)
Depends. If he gets bored/unhappy at his current positing, then his options for leaving might be narrowed.
Re:The Software Engineer’s Guide to Negotiating a Raise by rev_bird on Wednesday July 01, 2015 @12:33PM (#9813117)
At that point, it seems like it just comes down to how much you're willing to pay to be happy. If your lifestyle inflates to the point that you can't take a pay cut, then yeah, that's a shitty situation, but I know of some folks who would gladly trade $50,000 for a little more free time, and in the next year or so likely will.
Re:The Software Engineer’s Guide to Negotiating a Raise by trowawayyy on Tuesday June 30, 2015 @08:37PM (#9809274)
Hey! Great job. That's awesome.

My trajectories been

25k 6months, 45k 6m, 75k 1yr, 110k now.

Hoping to get to 150k in one more year. 150+ would be a sweet salary!!

(Throwaway)

Re:The Software Engineer’s Guide to Negotiating a Raise by ljk on Tuesday June 30, 2015 @07:53PM (#9809137)
that's impressive! what's the shortest time you've spent at a company?