@Jimmy9008 said in How do you know what a fair salary is for the area you work?:
Hi folks,
How do you decide what is a fair salary for an IT position?
As a hiring manager It was:
Look at the skills, identify skills that align with the job (IE it's cool if you were an oracle RAC admin but If I didn't need that I didn't care). If I see a good alignment (Your skills mostly are skills I saw value in) I'd assign $$ modifiers to the skills (Say someone who can do BGP/MPLS work was worth an extra 20K over another admin who couldn't), sum them up and if the value > the cost to hire you and you had the best value of any candidates at the time you got hired!
I am finding it to be quite difficult to get an idea as many job listings that require a similar skill set often say 'salary depending on experience'. So, you cannot really get any data.
Working for a large company there's stuff like GlassDoor to get an idea of what a company has previously paid a given title but even then that can get iffy, especially in consulting where everyone might get the same title but have wildly different skillsets and value. If it's a company who has H1B's you can look up the salary data on that (I think our average H1B makes 120K but you could align specific jobs to specific visa's and guess based on that). For software companies trying to figure out what the pay bands and level's corresponding between companies (Say for titles like MTS) https://www.levels.fyi/ isn't horrible. If you want to pseudo-anonymously ask people internally at a given company https://www.teamblind.com/articles/Topics works for larger companies.
There's also just go drinking with people and ask.
Salary != Compensation. Say it with me...
. Once you add up, RSU's ESPP, weird 401K benefits (Post tax rollover maximums and supporting reverse rollovers), HSA pre-paid match, health benefits, unlimited vacation, variable bonus tied to my MBOs, training and T&E costs It could be argued I've had years where 50% (or more) of my compensation wasn't my base salary.
https://thenicholson.com/thinking-taking-offer-need-know/
Plus, I have never quite trusted the data shown on sites like PayScale. Its probably quite skewed towards data being provided by those on lower salaries anyway.
It's just a data point. Just because you don't like that data point doesn't mean it's not data. it just might not be relevant data.
I also expect each area varies quite drastically in salary. It doesn't feel right to judge say a Sysadmin salary for somebody working from Kings Cross or Old Street to somebody in Greenwich...
Once you get above helpdesk fodder this shouldn't matter as work remote jobs (or jobs where you can office out of a remote office).
How do you begin to decide whats fair?
Who gives a @#%@ what's fair? It's about you trying to provide the most recognized value and extract the most value back in compensation as possible. Seriously, Rules of Acquisition should guide you in compensation negotiations.