One complaint that applies to most other salary apps (and mainstream reported numbers) too: unclear definition of salary - does it include bonuses, RSUs, options, etc. amortized annually? Without that, it seems to me meaningless to consider two 180k salaries as equal when one is making only 60k in bonuses/RSUs and another (let's say more wall st oriented) making 180k in year-end bonuses.<p>Are the salaries I'm seeing on the site base salaries only? If so, how are you guys planning to address the above issue? Otherwise, I do love the idea of the Salary Fairy (and FairPay).
Hi HN! We built these visualizations with d3 library. I'd love to hear your feedback, especially on the visualization of predictions between cities. Thanks!
Very cool application. I agree with MangoDiesel in that I found myself going through about 20 profiles with averages and then another 10 without, which makes for a poor experience. Intermixed would have been better.<p>Also, can't wait to see more users onboarded and see what people will guess on my own profile :)<p>Out of curiosity, what will your monetization be like?
After the first 7 predictions I made I ran into a series of many people where I was the first one making the prediction and didn't get to test my prediction against the crowd. It would have been a better experience to stagger the new profiles in with established ones because after 5-6 profiles in a row where I was the first one predicting I grew bored and clicked away.
Why don't you have users state their actual, current salary, and use that as part of the predictive analysis?<p>If you gather this data in different compensation categories, such as renumeration, options, benefits, RSUs etc – one would be able to get a better picture of what a "salary" is.
Is the job salary section still US only? How much is 'averaging' skewing the results? I am quite a bit over CTO (not to mention Sr Software Engineer) as just a web developer, and I don't feel like I'm overpaid...