Comment by Aurornis
4 days ago
> Apply for a job, within an hour get an email
Hiring has been crazy for years. It's worse with remote jobs because you get a firehose of applicants everywhere.
When I was doing a lot of hiring I tried to be as responsive as possible because you don't want to lose the best candidates. I would try to review applicants as fast as they came in. You have to understand that in that hour I might get 40 resumes. 1 or 2 are amazing, another 2-3 could be worth a look, and another 5 might have made the cut if I didn't just read those 2-5 much better resumes ahead of them.
If you met the listing qualifications but got rejected as not qualified, I would double check that your resume wasn't unclear about something. You would not believe how many times I've interviewed candidates who had some key experience that they forgot to include on the resume and didn't realize it was missing until it spontaneously came up in talking to them.
The simpler explanation is that a tired hiring manager was just clicking buttons to dismiss applicants who didn't make the cut.
> You have to understand that in that hour I might get 40 resumes. 1 or 2 are amazing, another 2-3 could be worth a look, and another 5 might have made the cut if I didn't just read those 2-5 much better resumes ahead of them.
This sounds like a dream. We posted a job a couple of weeks ago and had 1200 applications in around 2 days. Most are complete garbage. I'm confused why they took the time to apply at all, even if AI did it for them.
If you go through "Show HN" posts you will see multiple projects that partially or completely automate both search and application process. Just set up a bot that searches for newly posted positions matching whatever criteria, customizes the resume, applies. Probably costs a few cents for the applicant, but increases their chances somewhat. And the rest of us deal with the consequences.
Some fraction of applications that don’t really fit are submitted by people trying to keep their unemployment benefits. You have to keep applying to continue to qualify, but the jobs don’t have to be a perfect fit.
Being unemployed is hard and can be really demoralizing. Try thinking “I’m probably helping someone pay rent until they find a job listing that works for them” when you’re rejecting obviously unsuitable applications. It at least makes the “wtf”-ness of some of them seem a little less weird.
> Try thinking “I’m probably helping someone pay rent until they find a job listing that works for them” when you’re rejecting obviously unsuitable applications
I could believe this if you were in a population 5,000 town with few employers and the person applying had to work in person.
In our industry, where there are 1000 different remote job listings available to anyone at any time, there is no justification for this.
1 reply →
A lot of them are also from hostile foreign powers trying to commit economic sabotage.
>You would not believe how many times I've interviewed candidates who had some key experience that they forgot to include on the resume and didn't realize it was missing until it spontaneously came up in talking to them.
Resumes are only a 1 page summary (2 if you're really experienced) and this kind of market has you doing hundreds of submissions if you lack connections (or your connections are also job searching). You don't have the time to tailor every application for every role.
A shame because LLMs should really be perfect at this. Most current tools are too obsessed with writing for you (and creating a blander resume) instead of just taking a master CV and drag and dropping the most applicable roles/projects/experiences in.
At this point why don't you try to go out and contact candidates yourself or via a recruiter rather than posting jobs? It seems to me that with LLM-based tools you are going to find it increasingly difficult to get those 2-3 out of the 40; all 40 will be LLM-written to perfect match your posting.
AI tools have devalued resumes and cover letters, personal repos, leet code scores, etc...
It's always been the case, but now it's more true than ever: your professional network is super important. If somebody on the inside can recommend you, your chances of getting an offer are good compared to throwing your resume on the pile.
Even for non-inside hires, I feel like it's more efficient for me as a hiring manager to go out and look for candidates rather than triage some AI-generated pile of crap.
>via a recruiter
While not as bad as applying yourself, they can be pretty damned awful.
Especially if the job is posted on LinkedIn. You can already just poll a list of the most qualified candidates and reach out to them with opportunities.
The problem is companies would actually have to make compelling offers to qualified people.
Yeah, I’ve never understood this - earlier in my career this was the standard to have technically skilled hiring managers look for and contact people.
Now people act like they must have this ridiculous firehose of resumes to sort through, then have non-technical HR gals sort and filter out based on whatever random criteria they use, and then by the time it gets to the hiring managers - they still have no idea if this person is a complete idiot or has any skills at all. The qualified people you actually want to hire don’t want to be treated like idiots or liars either.
I just don’t feel it has to be this way - there is zero value in a firehose unless you were looking for desperate and cheap people.
I don't think anyone really wants the firehose. It's just something that happens when you advertise on any popular platform.
However I'll agree with you, the non-technical people sorting CVs on unknown criteria is something that became very widespread lately, and is certainly part of what's contributing to the problem.
Perhaps managers starting to do it by themselves rather than having HR in the middle is the answer to the problem.
I do reach out to LinkedIn profiles and some social media accounts, but I'd never use LLM-written text to do so.
You have to appear like a real human. The candidates in demand get recruiter spam all week long. If you go LLM slop canon on their inbox they're not going to respond.
Cold outreach has a low response rate. It's worth doing, but you can't rely on it. You have to go through all angles.
Typically I'd be doing a mix of my own cold outreach, public job postings, an internal company referral program, and for difficult roles a trusted external recruiter who I know is good for candidates.
> If you met the listing qualifications but got rejected as not qualified, I would double check that your resume wasn't unclear about something. You would not believe how many times I've interviewed candidates who had some key experience that they forgot to include on the resume and didn't realize it was missing until it spontaneously came up in talking to them.
That assumes that I am writing my resume for just your job posting. If I am just going to copy and paste the job requirement verbatim on my resume, doesn't that make your job screening applicants for actual experience much harder? Often times the difference is splitting hairs anyway ("we're looking for someone who paints brown houses").
But as a rule I don't customize my resume for every job posting anyway - if I have to apply to 70+ job listings to even hear back from even one of them, I would just frankly not have the time to do so.
Regardless, if my application is getting thrown out because my title is not quite right in a subtle way, or I reference Javascript but not Python, and no one is telling me - that's unfair on everybody. The company is going to skip over the best candidates for superficial reasons, because nobody is telling them their resume isn't perfect.
Consider the case... I've got a stack of 100 resumes and 2 hours today to select the top 10 candidates from that stack. I'll be ranking those 10 and give them to HR at the end of the day today. Tomorrow, HR will take the top 5 who are available and schedule interviews for next Tuesday. One of them will be selected from those who interview next Tuesday.
What can you do to increase the odds that you're in the top 10 (and preferably top 5)?
It's possible that a superficial reason was used to separate number 10 from number 11 ... and maybe number 11 would have been a great candidate and future employee. What I don't have is three weeks to do all day 9-5 1h long interviews for every candidate.
That makes sense for the opportunities that actually close after they are posted. I'm talking about jobs that disqualify you as a candidate same day, then repost the same listing next week. And next month. And next year. These are clearly ghost jobs.
Regardless - it would be nothing to show some basic human decency and respect:
- Review them more often until you get the 5 quality candidates to interview (there's no way in hell you actually review all 100 resumes fully - quit sitting on them for weeks and weeks)
- Take down the posting after resumes are reviewed
- Submit a basic and honest response for the people who's resumes didn't make the consideration
- A simple human note for the candidates who were considered but didn't make the interview
- Timely closer for the interviewed candidates who didn't get the job
None of these add any substantial time to the hiring process, but can go a long way to remember the human in a job market that's an absolutely brutal and soulless Leviathan right now.
11 replies →
That's why feedback is important. If the reason was "we are looking for X experience and X is not on your resume" I can adjust that for later. If it was even as honest as "we found enough qualified candidates to interview and didn't look at your resume", that's still semi-actionable feedback. I either apply earlier or just accept that I was unlucky and it was not my ability.
Generic rejections like "we moved with other candidates" tells me nothing. So noise remains because candidates don't have feedback to improve upon. All because HR wants minimize lawsuits through obscurity.
1 reply →
> That assumes that I am writing my resume for just your job posting. If I am just going to copy and paste the job requirement verbatim on my resume, doesn't that make your job screening applicants for actual experience much harder?
It doesn't make the hiring manager's job harder if you decline to customize your resume. They press reject and move to the next resume.
> Regardless, if my application is getting thrown out because my title is not quite right in a subtle way, or I reference Javascript but not Python, and no one is telling me - that's unfair on everybody.
If a job listing asks for Python and someone submits a resume that does not list Python, it's fair to reject that candidate.
If there was a hidden requirement to know Python but the job listing didn't ask for it, you get a lot of applicants that don't fit. Smart hiring managers will update the job listing as they review candidates. There are some lazy companies that will have secret requirements that they don't put in the job listing, but that only creates more work for everyone involved. It's not a secret trick they're pulling to be mean. They're just bad at their jobs.
> The company is going to skip over the best candidates for superficial reasons, because nobody is telling them their resume isn't perfect.
Unpopular opinion around these parts, but there's a high correlation between the best candidates and people who take the time to review the job posting and customize their resume before submitting.
I doubt the "best candidate" is also the person who can't be bothered to take 10 minutes to update their resume before pressing submit.
> But as a rule I don't customize my resume for every job posting anyway - if I have to apply to 70+ job listings to even hear back from even one of them,
Complaining about low response rates and refusing to tailor your resume are highly correlated, in my observation.
> If a job listing asks for Python and someone submits a resume that does not list Python, it's fair to reject that candidate.
The thing though is it's a bad requirement. There are any number of great candidates who could be proficient in Python - the skills are very transferrable. (It's like trying to find a painter and filtering out people who have never painted a brown houses)
The thing you're screening for by being so specific is not finding the most qualified person, you're going to end up with the person with the most time and patience to fib or lie on their resume.
> I doubt the "best candidate" is also the person who can't be bothered to take 10 minutes to update their resume before pressing submit.
That's exactly wrong - the best candidates are going to be busy people who are great at their job - the people jumping through HR hoops to get hired are by nature going to be worse candidates.
6 replies →
Probably a dumb question, but when you say "tailor your resume", what kind of tailoring do you mean? I've seen this advice repeated a lot, but I've rarely taken it because I tend to apply to jobs with the same job title and roughly the same responsibilities; in general, I assumed that tailoring is mainly helpful if you have a diverse/generalist skillset.
Like, it's obvious to me why a true Jack of all trades would use different resumes for applying to a plumber role vs a carpenter role, but less clear why a career plumber would tailor resumes for applying to two plumber roles at slightly different companies.
12 replies →
>I doubt the "best candidate" is also the person who can't be bothered to take 10 minutes to update their resume before pressing submit.
Do you really think the best candidates are ones who are bothering to cold apply through hiring portals to begin with? The best interviewers, sure.
For people who are actively searching, 10 minutes for 100 applications is 15 hours of work. Reply rates can be as bad as 1 in 500. In this kind of market you want to get that application rate down to 2-3 minutes. There's no time nor point to tailoring towards dream jobs; oods are you dreams were crushed 200 applications ago.
There's no particular reason your time is more valuable. We're all just trying to survive in these tumultuous times.
1 reply →
>Unpopular opinion around these parts, but there's a high correlation between the best candidates and people who take the time to review the job posting and customize their resume before submitting.
There's also a high correlation between matching the job description perfectly and the resume being AI generated and/or dishonest. Doubly so if the requirements are overly specific or contain pure nonsense as some do (saw "Must have 5 years experience with Claude Code" recently). You can filter out people who blatantly don't match the job and those who obviously just copied the job description. Never seen much correlation between the quality of resumes in the middle (ok to great) and how well they do in interviews.
Not to mention at many places "requirements" are mere suggestions or a low-effort list of technologies taken from the resume of the person who quit. Everybody has their own filtering rules and hiring managers rarely agree with each other much less the HR people usually doing the first round of filtering. The true requirements come out only at the resume filtering or interview stage.
>I doubt the "best candidate" is also the person who can't be bothered to take 10 minutes to update their resume before pressing submit.
The "best candidate" a lot of times doesn't mean the best able to do the job. It often means the ones who 1. makes the hiring manager feel good by being enthusiastic about their (statistically) average job for average pay and 2. minimizes their perceived risk of looking bad for their hiring choice.
>If a job listing asks for Python and someone submits a resume that does not list Python, it's fair to reject that candidate.
If you're not a FAANGMULA type place then sure. But also if your job posting lists something like "Python 3.14" or "7+ years Python" I know the hiring manager probably doesn't know the first thing about python. In that case I think it's fair for any decent programmer to lie because they will likely surpass the hiring managers knowledge by studying python a bit before the interview.
1 reply →