>but if you've ever been on the other side of hiring, people just don't know.
I've spent my entire career on the other side of hiring and I've yet to encounter a single valid excuse for not knowing, and subsequently not advertising, a salary range. Before you hire, you need to know if you can afford to hire. If you know you can afford to hire, you know what you can afford to pay. It really is that simple.
Affordability is different to declaring your position at the outset.
For example, when I buy a used car or a house, I know what my budget is. But I'm not telling the seller that upfront. Because my budget does not mean I want to pay the top end of the budget. I'd rather pay below my budget if I can.
The only excuse for forcing employers to do declare is that you want to hold them to a higher ethical standard. Not because there's no reason to do otherwise strategically.
>Because my budget does not mean I want to pay the top end of the budget.
Yeah I get the whole "if we advertise a range, everyone will demand the top of the range" argument. Unfortunately, that assumption has never held true.
> I guess I shouldnt commit my git changes either then
It's a crime against software. Real programmers one-shot their code in ink on paper, type it in verbatim, and run it without errors the first time around.
This never ending chase for a kinder, gentler way to use language is a fools errand. Every time we come up with another term for something, eventually it gets into the lexicon as a nasty term because unkind people will always find ways to use it disparagingly
People came up with "unalived" to get around censorship built by idiots who think they can trivially police language like this, now unalive is being used viciously by unkind people
I once asked a high-ranking Meta trust & safety employee why they don't just block paid ads that include telegram links and the short version of the incredible mental gymnastics they went through was "identifying telegram links is hard".
'normies' is, and has always been, self-deprecating. We (people who use HN, et al) are 'nerds' and 'geeks' who understand tech beyond the surface layer and can immediately see the downside to using things like Muse. We're significantly in the minority, hence we're not 'normal'.
I like it! The 'skill focus' prep appears to be the only way to improve my skill attributes but despite choosing that for each tournament in early season, it doesn't appear to have any permanent effect on my attributes.
There's a skill focus for each tournament that gives you a temporary boost to tournament results. And then there's an annual progress option at the beginning of each season to permanently update your attributes. Thanks for playing it!
Depends on a whole bunch of factors. Location, growth stage, product industry, and funding are the main influencers.
Location - Assuming you're not based somewhere obscure, there'll be endless compensation reports, benchmarks, glassdoor data, etc available as a starting point.
Growth stage - How you compensate people when there are three people in the company is immensely different to when there are 20 people, 120 people, 500 people, etc. Equity is more important at the earlier stages but with everything going on in the world, don't assume equity alone will be sufficient to win people over.
Product industry - Some of this is location specific but different product industries pay different premiums. In the UK for example, FinTech pays more than most areas of tech, gaming pays less than most.
Funding - If you're sitting on a ridiculous amount of funding, then you need to lean into paying as far above average as possible. One thing that doesn't and probably never will change is that the more you pay people, the easier it is to hire. Obviously the less funding you have, the less you have to spend on comp but see my point above in growth stage.
reply