How to 2X Your Salary as a Software Engineer
youexec.com
How to 2X Your Salary as a Software Engineer
1–10 of 47 posts
Re: How to 2X Your Salary as a Software Engineer
#2In my experience, just do the following:
Be generally likable Write decent to good code Connect on a regular basis with current and former co-workers Be aggressive about finding new opportunities (usually through people you've worked with)
I agree with most of the points the author makes here, but I don't think you need to stay 2 years at a particular job - 1 is usually sufficient to avoid the negative resume effects and still get some decent projects under your belt.
Re: How to 2X Your Salary as a Software Engineer
#3Can someone fill me in, do most jurisdictions allow employers to report to each other how much you made in the previous job? Or is this considered protected data that employers cannot ask for?
Which jurisdictions have which rules?
Obviously if you don't have to disclose your previous salary you get an advantage. The same advantage as the employer has in not disclosing the salary they paid to the person you'll be replacing.
Re: How to 2X Your Salary as a Software Engineer
#4In my experience, just do the following: Be generally likable Write decent to good code Connect on a regular basis with current and former co-workers Be aggressive about finding new opportunities (usually through people you've worked with) I agree with most of the points the author makes here, but I don't think you need to stay 2 years at a particular job - 1 is usually sufficient to avoid the negative resume effects…
>1 is usually sufficient to avoid the negative resume effects
A string of one year stints would be a huge red flag to me. I would have a hard time selling this person up as we don't hire FTE's to come and go in a span of 12 months. Too much churn kills you, I'd likely pass unless circumstances where extraordinary.
Re: How to 2X Your Salary as a Software Engineer
#5In my experience, just do the following: Be generally likable Write decent to good code Connect on a regular basis with current and former co-workers Be aggressive about finding new opportunities (usually through people you've worked with) I agree with most of the points the author makes here, but I don't think you need to stay 2 years at a particular job - 1 is usually sufficient to avoid the negative resume effects…
1 year stints wouldn't really fly where I live.
Re: How to 2X Your Salary as a Software Engineer
#6In my experience, just do the following: Be generally likable Write decent to good code Connect on a regular basis with current and former co-workers Be aggressive about finding new opportunities (usually through people you've worked with) I agree with most of the points the author makes here, but I don't think you need to stay 2 years at a particular job - 1 is usually sufficient to avoid the negative resume effects…
>1 is usually sufficient to avoid the negative resume effects A string of one year stints would be a huge red flag to me. I would have a hard time selling this person up as we don't hire FTE's to come and go in a span of 12 months. Too much churn kills you, I'd likely pass unless circumstances where extraordinary.
I'd say 1 year minimum (if you're unhappy), 3 years max if it's a company you enjoy. If you're "meh", start looking at 1.5 years, but only switch if you find something exciting, take your time.
Re: How to 2X Your Salary as a Software Engineer
#7In my experience, just do the following: Be generally likable Write decent to good code Connect on a regular basis with current and former co-workers Be aggressive about finding new opportunities (usually through people you've worked with) I agree with most of the points the author makes here, but I don't think you need to stay 2 years at a particular job - 1 is usually sufficient to avoid the negative resume effects…
>1 is usually sufficient to avoid the negative resume effects A string of one year stints would be a huge red flag to me. I would have a hard time selling this person up as we don't hire FTE's to come and go in a span of 12 months. Too much churn kills you, I'd likely pass unless circumstances where extraordinary.
I've worked for many 1 year stints (everywhere I've worked besides my old startup), and have never had a problem finding jobs.
Of course I probably wouldn't know if a place passed on me because of that.
I wonder what the probability distribution for how much hirers weight "loyalty" or "stick-around-ness" looks like.
Re: How to 2X Your Salary as a Software Engineer
#8In my experience, just do the following: Be generally likable Write decent to good code Connect on a regular basis with current and former co-workers Be aggressive about finding new opportunities (usually through people you've worked with) I agree with most of the points the author makes here, but I don't think you need to stay 2 years at a particular job - 1 is usually sufficient to avoid the negative resume effects…
Yeah you will get to 2x much faster doing 1 year instead of 2. Also, you can probably even explain away one job being less than 1 year pretty easily.
"Oh, I didn't get to work there long because X company made an offer that I couldn't reasonably turn down when taking into account my family's future".
Granted you have to get to the interview stage...
Re: How to 2X Your Salary as a Software Engineer
#9How realistic is this though? Imagine you come out of college and work for the Big 4 making $100k. Assuming you make 10% more (compounding) every 2 years, by 38-36 you would make over $200k, by 50 you are making close to $500k. You hit that much sooner if you change those numbers by 20%. At what point do those returns diminish and you're having to do something more creative than simply looking for a job every 2 years?
Re: How to 2X Your Salary as a Software Engineer
#10Earlier quoted context omitted.
>1 is usually sufficient to avoid the negative resume effects A string of one year stints would be a huge red flag to me. I would have a hard time selling this person up as we don't hire FTE's to come and go in a span of 12 months. Too much churn kills you, I'd likely pass unless circumstances where extraordinary.
I've worked for many 1 year stints (everywhere I've worked besides my old startup), and have never had a problem finding jobs. Of course I probably wouldn't know if a place passed on me because of that. I wonder what the probability distribution for how much hirers weight "loyalty" or "stick-around-ness" looks like.
Yeah, no idea. I'm not concerned with loyalty so much as I am with dealing with the fallout of churn. I've only ever worked at small companies on small teams, so a single engineer leaving tends to hurt. The company isn't loyal to them, so I expect an engineer to look out for their own self interest in the same way. That said, one year is a pretty short time, and if they're _only_ concerned with that next pay bump then they're probably going to cause my team some problems.
On the flip side, it's my responsibility to make sure that my engineers are happy in their position and weren't sold on a lie.