= 27d567bc2d48d9f40e9ccc20ea370b15)
MattG comments on Salary charts & Projection tool - Less Wrong
You are viewing a comment permalink. View the original post to see all comments and the full post content.
= 783df68a0f980790206b9ea87794c5b6)
Loading…= b715d02e85f7b3b4ae65ca3d3e450868)
Subscribe to RSS Feed
Powered by Reddit
= f037147d6e6c911a85753b9abdedda8d)
You are viewing a comment permalink. View the original post to see all comments and the full post content.
Comments (24)
I was planning on doing similar work for my next, next project. I love what you're doing and agree with the mission (although, I think both the "which career" and the "how to get the career" are about equally taught, and horribly so).
As far as this specific implementation goes, I can tell you what I'd like for my clients. I'd rather have them start with a target income, then only consider jobs above that income... I believe BLS has ways to filter by the salary number, rather than job title, and I think it's essential for what you're trying to do.
If you click the Average Salary column, you can sort in ascending and descending order.
It's funny you mention that, that feature is actually built into the tool, it's just I hadn't written a user interface for it yet. I got your message as well, let's set up some time to talk.
The roadblock I came up against was how to return results that are useful. Many desirable-at-face-value careers (e.g. Artists, actors, etc.) have pretty high 90th percentile salaries but low average salaries. Is it useful to show people something that's possible albeit unlikely? One implementation I had toyed with was showing the number of people at that position actually making that kind of money.
What if you calculated the expected value for each position? That seems like the most accurate representation of what you're actually trying to capture.
Iff you have a uniform prior over your earning potential relative to those of others in the same job or job category.