Jokes on you, I don't want to work
-
Fucking too real. I can't tell if they're legitimately too incompetent to perform their most basic tasks at work or fucking with me.
Why not both meme.
-
This post did not contain any content.
This activated my fight or flight response
-
This post did not contain any content.
Ghosted an applicant I had miss work for three interviews award
Ah there it is.
When the fuck did this start becoming the norm, anyway?
-
Ghosted an applicant I had miss work for three interviews award
Ah there it is.
When the fuck did this start becoming the norm, anyway?
Yeah I thought I did pretty good in an interview and HR told me she’d let me know in a week about the outcome. Never heard anything.
-
Yeah I thought I did pretty good in an interview and HR told me she’d let me know in a week about the outcome. Never heard anything.
The ghosting is unfortunate but not new to me, precisely. I should have clarified: when did MULTIPLE interviews start becoming the norm?
-
The ghosting is unfortunate but not new to me, precisely. I should have clarified: when did MULTIPLE interviews start becoming the norm?
wrote last edited by [email protected]idk how you define interview, but for my team (engineering/automation), we do an HR screening call, a phone interview, and then finally an onsite walk around of the shop to ensure they're able to communicate effectively and talk about machines.
skipping the later steps just wastes our time and results in hiring shit people
I certainly don't want to spend more time than necessary interviewing people, and this is how we've determined is best to achieve that
total time is probably 20 min for the HR screen, anywhere from 5-60 minutes for the phone interview (the better it goes, the longer it goes, and I certainly don't force extending it, it's allowed to happen at the applicant's direction. standard length would be maybe 25 minutes to cover the necessary points and get a pass, any shorter and it means the applicant is crap). and same thing for the walk through, it's only going to be about 15 minutes required, but then can go much longer if we're having a good time. which is the case a surprising amount of the time
-
idk how you define interview, but for my team (engineering/automation), we do an HR screening call, a phone interview, and then finally an onsite walk around of the shop to ensure they're able to communicate effectively and talk about machines.
skipping the later steps just wastes our time and results in hiring shit people
I certainly don't want to spend more time than necessary interviewing people, and this is how we've determined is best to achieve that
total time is probably 20 min for the HR screen, anywhere from 5-60 minutes for the phone interview (the better it goes, the longer it goes, and I certainly don't force extending it, it's allowed to happen at the applicant's direction. standard length would be maybe 25 minutes to cover the necessary points and get a pass, any shorter and it means the applicant is crap). and same thing for the walk through, it's only going to be about 15 minutes required, but then can go much longer if we're having a good time. which is the case a surprising amount of the time
What you're describing is pretty understandable. But I've also been in multi-round interviews where I'm talking to different people but saying the exact same things, which is frustrating.
-
What you're describing is pretty understandable. But I've also been in multi-round interviews where I'm talking to different people but saying the exact same things, which is frustrating.
yeah, and that's something I'm super against. all of our stages cover different material, and the actual interviews are with the same people (with the bonus of meeting some other people onsite if they're available, just to have a chat)
-
If they don't call back, it's only because they are too busy contacting random people on linkedin just to tell them in a call they don't have to qualifications for the job. Priorities.
Or setting up an interview and then saying "sorry the company decided that they're not looking to hire anyone right now" a day or two before. Why does that keep happening to me?
-
What you're describing is pretty understandable. But I've also been in multi-round interviews where I'm talking to different people but saying the exact same things, which is frustrating.
My current job had me pretty much interview with every member of my now team. It was insane and I'm happy I didn't have to do it while unemployed and desperately searching. I can't imagine going through that repeatedly
-
Or setting up an interview and then saying "sorry the company decided that they're not looking to hire anyone right now" a day or two before. Why does that keep happening to me?
IIRC this is because companies will post jobs that they want to hire for internally. Either they are required to post these positions publicly, or they benefit from doing so.
-
Why not both meme.
I gotchu.
-
idk how you define interview, but for my team (engineering/automation), we do an HR screening call, a phone interview, and then finally an onsite walk around of the shop to ensure they're able to communicate effectively and talk about machines.
skipping the later steps just wastes our time and results in hiring shit people
I certainly don't want to spend more time than necessary interviewing people, and this is how we've determined is best to achieve that
total time is probably 20 min for the HR screen, anywhere from 5-60 minutes for the phone interview (the better it goes, the longer it goes, and I certainly don't force extending it, it's allowed to happen at the applicant's direction. standard length would be maybe 25 minutes to cover the necessary points and get a pass, any shorter and it means the applicant is crap). and same thing for the walk through, it's only going to be about 15 minutes required, but then can go much longer if we're having a good time. which is the case a surprising amount of the time
For my current web developer position I had to walk through generating a Ruby on Rails app and creating a blog with some controllers, models, etc. It was so basic that I was concerned the company would end up being terrible.
I’ve now worked there for 4+ years and I later found out they were simply filtering out applicants who claimed to know the framework but then didn’t even know basic Ruby. Like, applicants from completely different programming languages would apply and try to pretend they knew it come interview time.
-
The ghosting is unfortunate but not new to me, precisely. I should have clarified: when did MULTIPLE interviews start becoming the norm?
In IT? About 20 years ago, at least. I would never hire someone after 1 interview myself, that's crazy.
