4 ms·
Because often the salary isn't decided when they make the job opening, the salary is decided when they make the offer. At my company, for instance, there are a
by jonfw 6y ago
Because often the salary isn't decided when they make the job opening, the salary is decided when they make the offer.
At my company, for instance, there are a number of us who were hired at the same time under the same position. But we have varying levels of skill/experience, and our salaries can reflect that even though our title may not
- SketchySeaBeast 6y ago> At my company, for instance, there are a number of us who were hired at the same time under the same position. But we have varying levels of skill/experience, and our salaries can reflect that even though our title may not Do you know that the salaries match that skill/experience line? Did you all just happen to request the right amount of money that plots you correctly, even though you didn't know what the other people were requesting, nor what the company is willing to pay?
- jonfw 6y agoI don't think anybody has figured out how to perfectly make salaries match skill/experience. But there is certainly a correlation. The job opening that I applied for cast quite a wide net. There are people who have masters degrees and 8+ years of experience, and there are people fresh out of boot camp, and everywhere in between. If you're required to post salaries, than suddenly you have to invent more job titles which lends itself to a more hierarchical organization
- SketchySeaBeast 6y ago> But there is certainly a correlation. You know this because you see everyone's salary, or have all talked about it? And if you've got fresh grades and people with masters and 8+ years of experience, there's already a hierarchy there, not giving a name doesn't mean it doesn't exist. As someone who's far from a tech center, I honestly have no idea as to my worth as a developer - I have zero frame of reference. If I were to apply for a job tomorrow it would be basically a guess based upon what I'd like to be earning and could be vastly undervaluing or overvaluing myself. Sites like glassdoor kind of insight, though not really given the small sample size, reporting bias, and lack of requirements for truth, and no developers I know talk openly about their salary.
- jonfw 6y agoIn my experience, a flat org-chart goes a long way towards establishing a less hierarchical culture. I've definitely had some discussions about salary with my friends at the company, although they're very guarded. A lot has to be inferred. The only real way to gauge your value is to collect more data- if you don't have developer friends that share that information, the only way to collect that data is to cross-shop offers. Or you can try to glean as much as you can from recruiters. One thing I asked when I initially spoke to recruiters, "what do you think a prospect with my skillset could command in the market?". In that first phone call they're still trying to convince you of their value, so that's when they're least incentivized to low-ball you
- westoque 6y agoI agree but only to a certain degree, a fresh grad vs mid-level, then a mid-level most certainly have a higher base salary. But for people applying for the same position, salary reflects how good you are at negotiating on top of your perceived value.
- jonfw 6y agoEverybody on our team, minus leadership (10-15 years+ of experience) has the same title and same level of 'seniority'. And our team hires people fresh out of boot camp, and they also hire people working on their second master's degree who have over 8 years of experience. I certainly agree that salary doesn't perfectly reflect perceived value, but when perceived value can range from 70k to 170k there is a very significant correlation