zlacker

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+(OP)
Might be interesting to also cover areas / specialties like "devops", "security", etc.

And count who is only interested in remote. That ratio seems to be _way_ higher here than on the general market, to no particular surprise.

>>araes+(OP)
Very interesting. It looks like RUST is the only tech that has strong demand. Good thing you can't learn it in 2 weeks (or 2 months for that matter)

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

>>street+Oq
> Good thing you can't learn it in 2 weeks (or 2 months for that matter)

True story :)

It seems Rust’s designers optimized for C/C++ devs over everyone else in order to give them a realistic chance at overthrowing C/C++ for systems programming.

>>street+Oq
Same with git

>>Tempes+YN
Which surely doesn't mean that more companies started using git.

So... Lots of new applicants who don't know git?

>>maxvt+41
Totally agree on the additions, just happened to be 15-20 minutes of Excel twiddling and sort rather than working out an extensive database.

>>omneit+Du
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.

>>Kinran+jX
Or..

Experienced applicants do not bother to list git as it is an assumed skill in dev work these days.

>>araes+(OP)
I calculated the ratios, and ordered them (probably. It's 5am and I did it very quickly)

git: 0.28

rust: 0.42

c++: 0.94

typescript: 0.95

react: 1.10

kubernetes: 1.22

go[lang]: 1.33

php: 1.33

aws: 1.39

sql: 1.40

postgres[ql]: 1.50

c: 1.57

nodejs: 1.62

python: 1.69

java: 1.73

terraform: 1.83

docker: 2.25

c#: 2.29

ruby[on_rails]: 2.40

javascript: 3.00

scala: 3.00

linux: 3.22

html: 4.00

flask: 4.50

mongodb: 4.67

mysql: 5.50

javascript/typescript: 6.50

bash: 13.00

express: 14.00

css: 21.00