2 ms·
"What you're worth" is totally dependent on the skills you bring with the needs the company has. Even in something as specialized as web development, there's h
by mgkimsal 16y ago
"What you're worth" is totally dependent on the skills you bring with the needs the company has. Even in something as specialized as web development, there's huge room for variances.
Couple of points...
Soft skills - can I comfortably discuss a range of topics and ideas with people at all levels of an org, including their clients? What is it worth for you as an employer to know you can bring someone in to a meeting who is, not just presentable, but groks what's going on, says the right things, picks up what they need to know, and can act on it?
Domain knowledge - even outside of your core org's focus - can be invaluable when trying to come up with solutions to some problems. If the knowledge is there with the right problems, there's value created. If not, no value.
A friend works at a company which had some security problems based on some poor decisions that were made in the web services APIs. Someone with practical experience - like me - wouldn't have made those decisions. What 'value' do you place on the tens of thousands of dollars in man hours, customer relations issues and lost opportunity cost would you put on bringing someone like me in vs someone else with less experience?
So... "what do you think you're worth?" is very hard to calculate before the fact, because you usually don't have much insight in to the inner working and problems. After you're hired, you can generally expect to be on the COL-raises and mild bonuses - usually computed based on the dept or team's collective efforts. If you can get some form of profit-sharing negotiated, you may be better off, but even that is still subject to the company's overall financial health, and you normally have little positive control over that.