The Software Engineer’s Guide to Negotiating a Raise

Re:The Software Engineer’s Guide to Negotiating a Raise by vonmoltke on Tuesday June 30, 2015 @05:20PM (#9808514)

One of the theoretical advantages of a large, diversified firm is the plethora of internal opportunities for job and even career changes with less friction than trying to put yourself on the open market.

In practice, unfortunately, it seems all too easy to get pigeonholed, hit a political snare, or some other roadblock that makes your career there a trap rather than an opportunity.

[ Parent | on HN ]

Re:The Software Engineer’s Guide to Negotiating a Raise by pacaro on Tuesday June 30, 2015 @09:55PM (#9809608)

This.

I worked at Microsoft for nearly 14 years. I had the privilege of working on 4 very different teams (microBrowser, Palladium/Bitlocker, Robotics, Midori)

So in many respects it was like working at 4 different companies, in that respect I avoided the pigeonhole trap (which certainly also applies when you do move companies) but over time I accumulated corporate cruft which ended up dragging me down. Moving to a new company allows you to reset that.

[ Parent | on HN ]

Re:The Software Engineer’s Guide to Negotiating a Raise by donut on Tuesday June 30, 2015 @11:14PM (#9809883)

What do you mean by corporate cruft?

[ Parent | on HN ]

Re:The Software Engineer’s Guide to Negotiating a Raise by pacaro on Wednesday July 01, 2015 @09:54AM (#9811786)

For example, your review history follows you, after a certain point poor promotion velocity is used to justify not promoting...

[ Parent | on HN ]

Re:The Software Engineer’s Guide to Negotiating a Raise by wting on Wednesday July 01, 2015 @12:55AM (#9810147)

You become the goto guy / domain expert over enough things that most of your time is spent being interrupted or in meetings instead of building stuff.

[ Parent | on HN ]