27 ms·
I'm not quite sure which part you're reply to, but my best guess is the bit about trying to hire a contractor to do hardware upgrades. In that case, we were ba
by tene 10y ago
I'm not quite sure which part you're reply to, but my best guess is the bit about trying to hire a contractor to do hardware upgrades. In that case, we were basically looking for interns; we were bringing people in who had relatively little experience. The guy we ended up hiring had no professional experience, and was looking to quit his job as a high school math teacher. He's worked out fantastically.
If you're talking about the sysadmin position, we've mostly given up on bringing in anyone who knows the difference between their ass and an RST packet, and we're going to try hiring interns to train.
If you're talking about the senior software engineering position, maybe you're suggesting that experienced software engineers are unwilling to go through a one-hour technical phone screen involving writing code? Maybe that's true; I don't know much about the earlier stages of that hiring effort.
- wyclif 10y agoAfter reading your comments here on sysadmin hiring and hearing similar stories elsewhere, I'm wondering if these problems are possibly compounded by other issues, too. One of them might be the rise of the "full stack" engineer. In other words, a lot of the pure sysadmin guys might be retiring now or moving into upper management, and there isn't enough young blood getting into sysadmin (cough DevOps cough) anymore. Maybe millennial-age young programmers are finding NodeJS, React, or anything new and shiny more appealing as a career path?