Hacker News Reader

Comment by aepearson | Hacker News Reader

Personally? I am 100% more likely.

Likewise, especially since "competitive" is such a huge range. As an example, if I'm currently making $100k, I might entertain a position at a slightly interesting company that's offering a "competitive" salary of $95k. However, I don't think there's anything that would make me go through the hassle of interviewing for a job paying a "competitive" $60k.

Basically, posting the salary range gives me a quick and easy way to weed out those companies which aren't serious without a significant investment of my time.

So a displayed salary range (perhaps $5-15k in swing?) in any case offers something more tangible/clear than 'competitive'?

I could certainly agree with that. It doesn't confine a company to a certain $x, but isn't as opaque as the bog standard 'competitive.'

A range would at least give me a good idea of whether the salary is more or less than what I'm currently getting paid. If the high end of the range is well below my current salary, I know I shouldn't waste my time. "Competitive" can mean just about anything, so it gives me absolutely no information.

That's fair logic - what if other forms of compensation were included in the listed range? (e.g. top end of band + equity)

Are there any other factors that influence your decision when applying for a new job? e.g. Prestige of the company, tech challenges, etc?

The tech stack used. When they're still doing LAMP in 2015, never. Or PHP in general. But that's just me I'd say

Ouch. We're still using PHP but appreciate what you're saying. What tech stack are you using at the moment?

(Elixir/Phoenix || Node.js/Meteor || Ruby/Rails) && (Angular.js, React, Homegrown JS frontend stuff), as well as desktop stuff with JS (my "lib": https://github.com/Anonyfox/node-webkit-hipster-seed ) from time to time. Actually I'm fluent in many languages so the concrete choice doesn't matter really as long as it is suitable for the given problem. But today there is no question where the answer would be PHP. Especially when the future is "soft" realtime, distributed and high performant or for tiny devices, problems you can't throw more hardware/caches at.

Reply on news.ycombinator.com