loading...
Cover image for Compensation tips

Compensation tips

gonedark profile image Jason McCreary Originally published at jason.pureconcepts.net ・3 min read

In the past week a few people have asked my advice regarding compensation. Coincidentally, I personally have had to think about compensation as I recently changed jobs.

During my career I've changed jobs 14 times across 12 companies. These were strictly full-time positions. I'm not counting the various contract work I've done over the last 20 years.

My experience has forced me to become comfortable discussing compensation. But most people, especially developers, are not. In fact, as developers, we're likely to accept a position offering the ability to work with new tech or the latest hardware rather than higher compensation. I know I have.

At some point, however, you're going to want to increase your compensation. You'll be faced with the decision to seek a raise or change jobs.

Before addressing this specific scenario, I'd like to share some general advice on compensation.

Always get money up front.

Whether this is a downpayment on a side project or a higher starting salary - always get money up front. Getting money later is not only difficult, but a never ending game of catch-up.

At one of my first jobs, I accepted a salary of $45,000. I wanted $50,000. The company gave an annual 3% raise, so I figured I'd make it up. While true, I didn't do the math. At $45,000 it takes 4 years to raise to $50,000. Had my starting salary been $50,000, I would have made $21,000 more during that same time. In addition, my salary would have risen to $56,000.

Your value is not your worth.

Worth is a deserved amount. In regards to our compensation, we're likely to give ourselves a higher worth. Indeed, we may be worth it. But compensation is more about value, which is a judged amount. Your salary is an amount based on the value you provide to the company and the value the job provides to you.

At one company, I started a role as a Senior PHP Developer. I transitioned into an opening on the iOS team. In the industry, an iOS Developer is worth more than a Senior PHP Developer. However, my value was less because within the company I was not an experienced iOS developer.

Stick to the schedule.

Be as strict as possible with your hours while remaining a team player. If there is a special project or something you want to go above and beyond, do it. Just don't make this the norm. Otherwise, you've willingly lowered your compensation. One of my favorite uncon talks on the matter is Go the fuck home!. Take the 5 minutes to watch it.

In addition to your hours, also stick to the schedule for reviews. If a company says "let's talk again in 6 months", have the talk after 6 months. Do not wait.

I was on a team tasked with a large upgrade under a tight deadline. To meet the deadline, several of us were working more than 60 hour weeks. We all worked hard and got it done. But during that time I worked 50% more, effectively decreasing my compensation 34%.


While the circumstances varied, the specific question I was asked came down to:

Should I seek a raise or change jobs?

Ultimately you have to make this decision. But the following points may help guide you.

Will a raise really help?

Depending on your circumstances, you may be past a point where a raise would help. Play through some scenarios. What happens if the raise is 3%? 5%? 10%? What if the raise isn't immediate? Also think through the psychology. Does a raise get you back to feeling good about the job? Or does a raise just make up for past circumstances?

Do you have other offers?

It's easier to get a job when you have a job. There are, of course, exceptions. For most though, it's easier to make a lateral or even upward move in compensation when changing from a current job to a new job. Without a current job, there's a greater risk to take a decreased compensation.

If you're at a point where you want to leave your current job be sure to have your finances in order. You'll want enough savings to allow yourself extra time to find another job.

What is your ideal job?

An ideal time to think about what you want in a job is when you're changing a job. Doing so will not only help you assess potential jobs, but how to value them. A few years ago I wrote Why I leave a job. It may help get you started.

Posted on by:

gonedark profile

Jason McCreary

@gonedark

I build things with my hands. The human behind Shift - https://laravelshift.com, master of Git - https://gettinggit.com, and author of "BaseCode" - https://basecodefieldguide.com

Discussion

markdown guide
 

This subject is so taboo that I'm afraid to hit the Like button 😃

In our field of work, and connected tech areas, from what I saw so far (>10 yrs) if you want more money it's better to change jobs at around 2 yrs, because the overall salaries increase more then 5-7% of the avg paycheck increase.

 

"We all worked hard and got it done. But during that time I worked 50% more, effectively decreasing my compensation 34%."

I know that feel bro. That's the main reason I changed my job. Some extra hours doesn't worth it

 

Very good post - I always told myself: Family first, after all getting a new family is much more expensive than getting a new job (married, seven kids)

But I'm aware that I'm in the entitled position as Senior Dev to choose from multiple offers, not that easy when it's your first job to stick to a firm: Go Home policy

 

Thank you for that video. As a tester I'm often convinced my self that extra hours is the thing how I demonstrate my value. That video is a good reminder. Will try to do the math more often. That seems like an interesting approach to try and keep me focused during the day and help to be the reason to leave the office earlier (:

 

Awesome read Jason, thanks for writing it. I do have one question, say if you moved into a different job (at the same company) but never received a raise in compensation. How would you approach asking for a raise?

 

That can be one of those no-mans-land areas.

If one was promised as part of the transfer then you should send a quick email just following up. Also most a reminder that part of the transfer included a raise.

If one was not promised, you might have to do a little more to present your case on why you deserve a raise - more responsibilities, higher skilled labor, etc.

 

It depends on the country and culture. Even if the IT HR evolves the rest of the country may lay back.

 

I don't get it. I see you doing the hip brogrammer jargon of "PHP is bad, Apple is infallible" but ultimately languages are fairly unimportant. Plenty of bad swift/ios devs out there, and plenty of good PHP/Perl devs out there who don't subscribe to whatever niche language is hot at the moment. sounds like you need to sell the projects you worked on better rather than the ultimately transient tech.

 

What? I literally have no idea where you're getting this…