Live data from Hacker News

I applied to 250 jobs and timed how long each one took

careerfair.io

181–190 of 220 posts

Re: I applied to 250 jobs and timed how long each one took

#181

Earlier quoted context omitted.

> Why would someone put ANYTHING on their resume that is not factually correct? If their current income is $0 and the income from a successful ruse is minimum several weeks of several thousands of dollars, and the cost per throw is around a dime… It’s not hard to see how the algebra works out.

you need algebra to figure that out?

Algebra that you can do in your head is still algebra.

Re: I applied to 250 jobs and timed how long each one took

#182
post #33
post #17

I overheard a guy at the gym a couple of weeks back saying that he's automated (gpt4) the keyword-optimised CV/cover letter process to the point where he was able to apply to - I'm a bit suspect on this bit, but the generation at least is believable - 75 jobs in an hour and a half. We've raised the noise floor significantly. Ps. If you're here mate I hope it worked out for you.

I think there's a dynamic where: - Desirable job applicants get hired quickly, but people who can't get hired stay on the market - People who can't get hired will keep applying to more and more jobs - So every new job opening gets flooded with applications from people who couldn't get hired elsewhere - Employers don't have time to read the flood of applications in detail, so they rely on cheap filters (keywords on re…

This, and a few more dynamics, including:

- The better applicants usually have several warm leads and often don't bother with high-effort application processes, since they have a pretty decent chance of getting hired wherever they apply, and they're also not bothering to apply for things they're wildly unqualified for

- The worse and more desperate applicants have the time and motivation to stick through the most bizarre and convoluted application process until they get kicked out, with no regard to how well they actually match the requirements

So thus, the more hoops you put into your process to try and stem the tide of the hoards of desperate unqualified applicants, the more you disproportionately screen out the highly qualified applicants who have better things to do and better opportunities to pursue.

Re: I applied to 250 jobs and timed how long each one took

#183

Earlier quoted context omitted.

When I apply for a job it takes me at least an hour if not more. I adopt my resumé, write the motivation letter. If I spend less then 15 minutes it means I'm doing it as a requirement from the social benefits agency, for a job that I don't want.

> I adopt my resumé, write the motivation letter. Only to find out that the other side didn't read that letter, and most didn't read the resume. I know, because I asked.

Funny story. When I was going the coop workshops in uni they invited in some people from microsoft to talk about what they look for in a cover letter and they straight up said they don't read them.

Re: I applied to 250 jobs and timed how long each one took

#184
post #33

Earlier quoted context omitted.

I think there's a dynamic where: - Desirable job applicants get hired quickly, but people who can't get hired stay on the market - People who can't get hired will keep applying to more and more jobs - So every new job opening gets flooded with applications from people who couldn't get hired elsewhere - Employers don't have time to read the flood of applications in detail, so they rely on cheap filters (keywords on re…

This is also how 80% of companies can believe they’re hiring mostly top-1% programmers. No, you’re hiring top-1% of applicants , not top-1% of employees !

All companies share a common pool of bottom 99% applicants.

Re: I applied to 250 jobs and timed how long each one took

#185

Earlier quoted context omitted.

Yes, I can see that working early in a career. Now that I think of it, my best friend did exactly that too when he was 19, and he managed to get his foot in the door. For what it's worth I think your current strategy of applying for relevant jobs is the right one, particularly if it's a difficult market where you are. Tangential skills are also good possibilities. I hope you find something that works for you.

When you are fresh out of college you don't stand out. A few months ago we had 100 applicants for an entry level programming position. Every applicant was finishing their bachelors (a couple in CS, the rest in computer engineering) in June. They all had done some internship (in a not very relevant area but that is expected) and a class project. Almost all of them were Eagle scouts (until recently scouts only allowed…

Most people are terrible at writing resumes. We used to joke that we would throw half the resumes in the bin immediately on the grounds that we didn't want to employ unlucky people!

The biggest mistake I see for people with experience is that they describe their role and responsibilities but not what they specifically contributed and why they are awesome.

The best advice I was ever given is that your resume is a marketing document. It should contain things you would like to be asked about in an interview. Cut out everything else.

Re: I applied to 250 jobs and timed how long each one took

#186

Earlier quoted context omitted.

Yes, I can see that working early in a career. Now that I think of it, my best friend did exactly that too when he was 19, and he managed to get his foot in the door. For what it's worth I think your current strategy of applying for relevant jobs is the right one, particularly if it's a difficult market where you are. Tangential skills are also good possibilities. I hope you find something that works for you.

When you are fresh out of college you don't stand out. A few months ago we had 100 applicants for an entry level programming position. Every applicant was finishing their bachelors (a couple in CS, the rest in computer engineering) in June. They all had done some internship (in a not very relevant area but that is expected) and a class project. Almost all of them were Eagle scouts (until recently scouts only allowed…

> It was really hard to filter down who to interview because they all look the same and we only had one position

Did you make up some BS metrics, or did you do the honest thing and draw résumés from a hat?

Re: I applied to 250 jobs and timed how long each one took

#187
post #179

Earlier quoted context omitted.

It’s definitely helped spread it. But honestly, these situations are nothing new. Back in the dot-com crash I remember it all being the same. Even entry level school computer labs were requiring CS PhD’s! And women, well, same.

Er, we had the internet during the dot-com crash. And before it, even. As I recall, things were not quite so bad in the 1980s. I vaguely recall seeing the odd newspaper article about the intense interest in a job, because it attracted maybe 500 applications. That was newsworthy.

It used to be you had to physically show up, or mail in a form to apply. That tends to put the brakes on mass applications pretty effectively.

It’s less the internet, and more folks using the internet/apps for processes that used to require in person physical presence. Which has been getting more and more common.

Re: I applied to 250 jobs and timed how long each one took

#188

Earlier quoted context omitted.

One of the biggest issues I've had, and I don't know how workday looks from their end, when it comes to entering in education and specifically degree. My degree says "Software Engineering," which I never see given in a list. So I usually just pick whatever is closest like "Computer Science," and I always wonder if there is a system that does some correlation between what it put in the box and on the resume.

I applied to company using workday recently. The job was a referral and the JD made it explicitly clear I didn’t need a degree. Yet it was a required field. And of course, it wasn’t a free form text field that would allow me to just enter N/A or my high school. It was a drop-down/search box that had a predefined list of colleges and universities. I ended up just entering some college I attended for two months before…

I've also seen that too. The no-free-form entry sucks. I went to a pretty big public school, but for some reason it wasn't included in the pre-populated list on one job I was applying to. No clue what the company using it's controls look like, but I even checked over big name public universities to see if they were on the pre-populated list and it was surprising how many were missing. Like UNC (University of North Carolina) wasn't listed.

Re: I applied to 250 jobs and timed how long each one took

#189

Earlier quoted context omitted.

When you are fresh out of college you don't stand out. A few months ago we had 100 applicants for an entry level programming position. Every applicant was finishing their bachelors (a couple in CS, the rest in computer engineering) in June. They all had done some internship (in a not very relevant area but that is expected) and a class project. Almost all of them were Eagle scouts (until recently scouts only allowed…

> It was really hard to filter down who to interview because they all look the same and we only had one position Did you make up some BS metrics, or did you do the honest thing and draw résumés from a hat?

From my experience, when you have too many similar resumes there are no useful metrics you can define. You just have to choose some to interview and bin the rest.

Re: I applied to 250 jobs and timed how long each one took

#190
post #67

Earlier quoted context omitted.

> Now suddenly every person magically has 8 years experience in a weird esoteric requirement that we're looking for. That's crazy to me. Why would someone put ANYTHING on their resume that is not factually correct? That in the end is a disservice to yourself and to your potential employer, not to mention the pressure it puts on job seekers to push the envelope on embellishment. What I am on the fence about in my own…

I think it depends a bit on where you are in life. I remember exaggerating a bit when applying for my first job. I was fresh out of university and really needed that job. I spent the following 2 years miserable, I just didn't fit in that well. Nowadays I'm brutally honest with my application and the following interviews. I see it as me choosing where to work rather than the other way around. If they pick my applicati…

> I can understand people being desperate and in need of that first job

Desperate people do desperate and unpredictable things though. Case in point:

> I remember exaggerating a bit when applying for my first job. [...] I spent the following 2 years miserable, I just didn't fit in that well.

Every now and then I have to investigate employees who seem to spontaneously lose their shit-- aside from one with an alcoholic spouse, so far every single one of them were just in over their head. They don't return calls, cozy up to security and ask questions about monitoring tools, check into mental hospitals, suddenly have internet connection issues all the time, lose or destroy their equipment repeatedly, etc. One would hop onto the IT support Slack channel and see what widespread issue was currently impacting others, then claim it was happening to her (and do the same with general/social, to see when people were getting sick and with what).

I wouldn't say it rises to the level of malingering, but it's clear they're desperately stalling, and it just creates a vortex that sucks them and everyone around them into. Contractual obligations stop being met because they become an entire sideshow and won't surrender. My fear is that one might eventually resort to sabotage; the closest we've come was a nonperformer trying to leverage workplace violence allegations against an executive.

> Nowadays I'm brutally honest with my application and the following interviews.

This is the way to do it. When you weave a web of lies, you have to maintain all those threads. Pathological liars are always anxious. Honesty makes for a much easier life.

Post reply on HN