zlacker

>>whoish+(OP)
Not a "Wants to be Hired", just did a quick technology survey of the responses out of curiosity at what's being listed down to the top 30 mentions for skill alignment purposes and areas where there are probably many resumes. Compared:

>>39217310 Who's Hiring Feb 2024

>>39217308 Who Wants to be Hired Feb 2024.

Mentions of Item in (Technologies:) | Mentions in Who's Hiring (not specific or filtered)

python: 83 | 49, react: 53 | 48, aws: 46 | 33, javascript: 42 | 14, typescript: 41 | 43, sql: 35 | 25, nodejs: 34 | 21, linux: 29 | 9, docker: 27 | 12, ruby[ on rails]: 24 | 10, go[lang]: 28 | 21, css: 21 | 1, postgres[ql]: 36 | 24, java: 19 | 11, rust: 19 | 45, c++: 17 | 18, c#: 16 | 7, html: 16 | 4, express: 14 | 1, mongodb: 14 | 3, bash: 13 | 1, javascript/typescript: 13 | 2, mysql: 11 | 2, terraform: 11 | 6, kubernetes: 11 | 9, c: 11 | 7, git: 9 | 32, scala: 9 | 3, flask: 9 | 2, php: 8 | 6

>>araes+VC1
Using percents rather than absolute figures would make the comparison much easier. Great work though, this is basically skill gaps and “arbitrage” opportunities!

>>omneit+y72
Couple issues. 1) The figures are only mentions in a relatively limited comparison mode, so a percent is only "vaguely" valid. 2) The percent implies "sidedness," yet I really was looking at this from both lists, where the ratio's important no matter which side you're on. Need workers, skill alignment in resumes you get is an issue. Need a job, skill alignment in the people asking's an issue.