Why unemployed workers are so burnt out
bbc.com
bbc.com
* Scour job listings for something that looked like a very good fit w/skillset
* Apply
* Have a phone screen
* Interview
* Get offer
For the first step, there were generally only a handful of openings that fit that criteria, and my success in the process was very high with about 25% average success rate from application to offer. Depending on the role, there were sometimes two screens: recruiter & hiring manager. The interview itself was typically one and done, and knowing the answer in a week. In the process, I'd probably be one of a dozen or fewer candidates.In my most recent search, the number of available roles was astounding. So many felt like a good fit, but each also had 50+ applicants, even for very senior roles. I applied to about 70 total jobs over a couple months, with about 30 resulting in Zoom calls, 3 going the full distance, and with 1 offer (2 companies responded to my application with interview requests a full 2 months after I applied). "Going the full distance" meant 6-8 interviews spread out over a couple weeks, which was far more mentally draining than doing everything in one go.
Complicating things further was the fact that over 50% of companies never let you know that they're not moving forward. For 6 or 7 of the ones that did (all larger companies), I had several screens with each as the recruiters for specific roles either ghosted me until another one picked me up, or the recruiters were fired as part of layoffs.
The result was that I ended up spending 2-3 hours a day in the process, which doesn't seem like much, but it did really serve to wear me down mentally to deal with so many spread out meetings, sift through 50+ job postings every day (more if I failed to check in a day), customize resumes, customize cover letters (anything to try to shift the odds), etc.
Employers ghosting applicants is one of the worst parts of the (non-)hiring process.
Many companies expect applicants to be at their beck and call during the hiring process, and then simply cease communication and become unresponsive as a (discourteous and unprofessional) way of saying "we don't want to hire you."
Almost worse is the "holding pattern" where they may even have filled the position but continue stringing applicants on indefinitely with vague and noncommittal responses.
As a somewhat absurd workaround, some companies automatically send rejections to all applicants (hired or not) after a set period of time (such as 90 days).
Recently a company said "no thanks", which is nice of them -- they responded. However, they also said "we'd like to talk to you!". Perhaps they have other roles for which I'm a better fit?
A brief cover letter that provides additional context to the resume is useful to me as a hiring manager, but I also know that few people read them. That said, anything to boost my chances is good, so I'll include such a letter with my applications.
In my experience, assuming the applicant is competent, being a good fit is more important than things like what specific skills they have or what they're worked on in the past. You can train new applicants in whatever skills your specific position requires, but you can't train new applicants to work well with an existing team.
Does it matter, though? Companies do not employ for the long term so my fit as a person is irrelevant. I won't be there long enough to really have that come up assuming I am able to front the minimum personality for the team. At the end of the second year my 0% raise I'll have taken two straight years of pay cuts.
As an applicant it’s hard to know the preference of the reviewer so that makes it harder. But I think that, for me, I just sort of accept that there’s much wasted effort in applying to jobs. Looking for work is a job, so spending 1-2 hours per application is work that must be done, even if some of it never gets seen.
I wrote a cover letter for the job I’m in now. I never asked my manager if she read it or if it influenced her decision. But I’ll probably write one next time.
Same goes for thank you notes. Hard to know if they work. But it doesn’t hurt, other than the labor involved in writing.
https://www.wsj.com/articles/that-plum-job-listing-may-just-...
First job didn't even contact me, and it disappeared from LinkedIn 3 weeks later.
Second and third job didn't contact me for months, only to get an automated rejection email.
The last job gave me an interview, and looked at me funny when I told them I only program as a hobby. It really sounds like they wanted a developer and an admin, but didn't want to hire two separate people (it was not a "devops" position). When I asked for an update, they told me there were 2 positions available, and who they hired for one dictated who they hired for the other. I haven't heard from them since, and at this point, and I expect another automated rejection email in the next month or so.
So yeah, HR people kindof suck.
I think there’s different philosophies around sysadmin work and you suffered from a mismatch from the position.
I know lots of sysadmins and they all automate tons of stuff. They aren’t “programmers” per se, but they wrote a lot of code. Mostly shell or maybe Perl or python or something similar. And they probably assume all sysadmins program and wouldn’t even think to call that out in the job posting.
This is part of hiring I hate the most, the mismatches. There’s no foolproof way I can think of to avoid. Networking is probably best, but that’s hard for me to do. But allows for questions like “so what do you mean by automation, is that like programming or some specific tool?”
I mean shell I can understand, and Perl to a minor degree because of sed/awk pcre regex, but Python is really getting into programmer territory in my books.
I wouldn't call myself a programmer by a long shot, I've written a 6502 state machine in C before, but I'm shocked it works at all, and it's not cycle accurate.
For what it's worth, this was some redhat shop who use slurm and foreman/katello... it really did seem like they wanted me to write code to run on their cluster (probably C++).
It sucks that I'm stuck where I am now, but it could be worse... so I'm not totally mad they've strung me along, but it would be nice if HR folks would say what they actually mean/want, and be prompt about it. Applicants are people too, and we deserve to know if the job actually exists if we're going to spend the time interviewing and training to get acclimated to whatever setup the CTO/CIO wants us to use to do our job.
Your arithmetic is off.