|
|
|
|
|
by mb22
3312 days ago
|
|
AtScale | Engineering | San Mateo | Salary: very good | ONSITE http://atscale.com We built an analytics platform that works with all the modern big data platforms both onsite (hadoop) and in the cloud (BigQuery, Athena). Our stack is Scala (back end), Go, JS. We do difficult things, actual algo implementation and stuff verging on real computer science. We desparately need more people that know a lot about Hive, Spark, Presto, Impala, etc and are willing to make it very interesting for the right person. We have a great team with no churn because we trust them to make the right decisions and execute. Thank you and good luck in your search. https://jobs.lever.co/atscale |
|
I hate to do this on this thread, but - commit to an explicit salary range or don't put anything down about it. What is "very good"? You might as well say "competitive" - it offers exactly the same transparency as if you had listed nothing, because it's qualitative, not quantitative.
What am I supposed to think after reading that description? "Very good" for me personally means north of $200k - for someone else it could be significantly higher or lower. But we don't really get the benefit of knowing if your "very good" matches our "very good."
It's particularly disingenuous to me to list salary as if you're going to be transparent about it, then slap something on there that just maintains the information asymmetry you had before. At least the other companies who list nothing at all are forthright in their lack of salary transparency.
To be clear, I'm not taking a side on salary transparency. I'm specifically saying you should take a side here, instead of trying to have your cake and eat it too. If your salary range is actually "very good" for that skillset, you will find that the right people are applying. Would you be interested in a SaaS product that said "Very Expensive" on its pricing page, instead of a) listing actual, quantifiable pricing or b) not listing pricing and requiring a sales call?