"For the purpose
of this report, Hired examined software engineering
candidate interview requests (IVR) and salary data from
January 2021 through December 2022 inclusive.
The data included reflects over 68,500 candidates and
494,000 interview requests between companies and
software engineers on Hired during this time period."
Then, I think, the numbers reflect only candidates and companies that use Hired, as opposed to the industry as a whole. I wonder how many folks land jobs through Hired?
Especially when it's well-known that many engineers, especially senior, are essentially never "on the market". They work through their networks, leveraging referrals, and will frequently vanish from one job and appear in another without submitting a resume, contacting a recruiter, or touching anything on linkedin/gh/etc.
Seems like that alone would put a big skew on results. It's kind of like the "r/cscareerquestions" effect. There's literally only 3 people posting: hapless anxious innocent newbies/newgrads, low-marketability folks who are struggling to find a position, and people who get off on trolling/doomposting and otherwise feeding off the despair of the other two crowds. The result being a forum that perpetually makes it seem impossible to get hired as a software engineer (even during the covid hiring spree!).
This isn’t my experience. I’ve interviewed many seniors in my time, and also gone on many interviews as a senior.
Networks fail people all the time. Mine failed me because I was at one company for a decade(switching teams), and my entire network still works there. I don’t want to go back, so I essentially have no network.
We hired an architect who’s entire network was still at IBM, similar to me. There’s other possible failure modes, it happens quite a bit IME.
Ah that's fair, I was being too hyperbolic. I suppose what I mean is "a nontrivial contingent [of seniors]."
Also it's worth noting that while your whole network might be at IBM still, I've found leveraging "I know X, who knows Y, who works at / worked at [target company i want to apply to]". They'll usually only be able to give you a "someone I know but haven't worked with" referral (some places call them just a "candidate lead"), but often it's still miles better than putting your resume in the website intake form. Going 2 degrees out in your network graph is almost always a shockingly large number of people / places.
Almost all the engineers I know get their jobs through random process. They use things like Hired, sending out resumes, responding to recruiters, rooftop slushie (no longer available), and then some actual referrals if they know someone. You use everything available cause you need to get multiple competing offers. You're not going to just interview at one or two friend's places and then get an offer and take it. You're gonna get 5-7 offers and then try to take the best one out of those by making them compete for one another.
This - turns out - requires a lot of companies and interviews and a lot of work.
> It's kind of like the "r/cscareerquestions" effect.
I canceled my ACM subscription in my late 20s because I got tired of ACM basically doomposting about careers. Last night I was going through my Gmail folders and found a bunch of old ACM doomposts I never deleted from their CSCAREERS mailing list.
So, it's not just reddit that doomposts- Industry veterans are just as paranoid and can also serve as Chicken Little.
anecdotally, i know more people that struggle with the hiring process then these extroverted super connected senior developers that just hop job from job that apparently exist. from the group of people i keep in contact with, i think only one is doing something like that. also the people we hired went through application pipelines and weren't just showing up after being recommended
I know quite a few developers who have a knack for following market trends and jumping on the rocket ship before it is about to launch.
It's actually not that hard if you think about what filter you would apply. The one hard part is finding recruiters who specialize in placing people at these companies, and, of course, passing the interview (or at least enough success that the interviewer doesn't tell the recruiter you are a poor quality candidate).
>They work through their networks, leveraging referrals, and will frequently vanish from one job and appear in another without submitting a resume, contacting a recruiter, or touching anything on linkedin/gh/etc.
I literally never heard of this, ever. Not even for staff+ positions.
I've read something on the lines of "even Tom Hanks sends his resume to the director when applying for a role". Hyperbolic or not, I've found this to be vastly true.
> Especially when it's well-known that many engineers, especially senior, are essentially never "on the market".
> Seems like that alone would put a big skew on results.
Yes it does. Same with internship pipelines at unicorns or FAANG. Some students intern at the same company multiple times during undergrad and transition full time after graduation. They appear to never be on the market.
I have had high callback rates from working with hired, as well as multi year engagement resulting from an offer through hired. These were with companies doing interesting work I would have never known I was a match for otherwise. You also need to do your own due diligence on the company, because hired is structured to take as little time commitment from their recruiters as possible (this is actually a good thing because it forces the companies on the website to be upfront).
I have two experiences of using Hired to try to land jobs; I got interview requests, I interviewed, but I never found a role I was committed enough to or qualified enough for.
Both times I came out without any offers. Definitely have my own share of the blame here, but I don't think Hired put a ton of high quality leads on my radar for the effort I put in.
Yeah there does appear to be bias in their sample since Ruby on Rails was their most in-demand skill. Not to knock it or anything, but it hardly seems like the number one skill industry wide.
I think its naïve to rank skills by a framework or library, but we're talking about a hiring platform website, used by keyword driven recruiters. If they were being more honest and accurate, lumping Django/Node would seem more appropriate. JVM/Java + C#/MSFT seems like it could stand on its own as well.
This. I recall most predictions saying 2024 would be the tipping point, but even then I doubt regulations at the local and national level will change that fast.
Ah memories. My first machine was a Classic ii. I think it might be in a friend's garage in Ohio, will have to check with him. Thanks for the great post!
https://www.davidspilmanfinebooks.com/pages/books/13948/caro...