We Don't Have a Talent Shortage. We Have a Sucker Shortage

Post by bitcoinmoney » Sat, Apr 20, 2019, 7:12 PM UTC

wrestlerman wrote: post #140

Based on my experience this is very true. It's very annoying when you want to find a job, but you don't want to be a sucker, so you end up looking for a job for a long time. I don't get it. You want to hire someone talented or smart, obviously, you are gonna have to pay them good money. What's the problem with that? I'm sure they will bring much more value than a usual sucker. Personal story ahead. I've been looking…

Post by watwut » Sat, Apr 20, 2019, 7:13 PM UTC

black-alert wrote: post #137

I think we do have a talent shortage, seriously, I see it all the time in the companies I work for. And if you run in an interview like the author describes, it is very likely that the interviewer just lacks talent and happens to be in that position, otherwise he or she would recognise the opportunity and go for a good deal. But there are also good reasons why companies are often extremely careful hiring new staff. M…

Post by dreamcompiler » Sat, Apr 20, 2019, 7:15 PM UTC

Game_Ender wrote: post #67

areyouseriousxx wrote: post #43

Earlier quoted context omitted.

I find it strange, as software developers, that we discuss the effects on automation all the time, but no one seems to understand that automation has made searching for new employees incredibly inexpensive and efficient compared to the past. So in technical roles there are a lot of companies that are always hiring. Recruiters work for free until they find you someone and placing job listings online is so inexpensive…

Interviews take 2-3 man days from a company per candidate you end up doing a full onsight interview. That is on the order of $1000’s per interview, and you generally have to do several per role. Then for high demand roles even the best will take several months to ramp up which costs a large fraction, say 25-50% of their total compensation. So replacing a dev can cost you in total $100k+ at least. That is not really c…

Post by nullc » Sat, Apr 20, 2019, 7:15 PM UTC

eps wrote: post #143

vetelphon wrote: post #22

I had an interview with a company working in the ML space. There is a semi-difficult problem that their particular industry needs a solution for so I spent a couple hours in the hotel the night before writing up a solution for it. I was doing an interview with their head of ML and brought this subject up in general without mentioning that I had already solved it. His immediate response was: "that's impossible." And i…

At some point I was working for a shop that did smartcard-based payment systems. I was patching some smaller bug when I noticed a call that was suspiciously close to an assert() that was accidentally left in. Merely commenting it out made the payment handshake complete 50% faster. Being an eager junior as I was I went to the principal dude who wrote this part (and pretty much the rest of the core) and he dismissed me…

Post by klenwell » Sat, Apr 20, 2019, 7:18 PM UTC

strictnein wrote: post #169

klenwell wrote: post #153

Like a lot of people here, I've been on both sides of the table. Currently on the hiring side of the table interviewing web application developers. I agree with a lot that's said in TFA, especially as someone who's suffered through a months-long motivated job search where I shared the pain. For example: > There are easily several thousand people in the town who are capable of building that business. Get over yourselv…

Maybe laws are different where you're at, but mentioning or considering gender in a role is the biggest of no-nos. Grounds for firing and large lawsuits.