This is a discussion on Not getting hired? 10 reasons why within the Education & Career Talk forums, part of the Topics of Interest category; Originally Posted by rishabhpuri Hey, everyone, my name is Rishabh Puri , I am a successful businessman, an author, poet, ...
Last edited by DoIHavetohaveaUserName; 01-22-2019 at 05:27 AM.
I recently had to reject a number of great candidates who had the skills, the experience and the confidence, just for the reason that their salary request was way over my budget.
Made me think of this vid
The reasons I wasn't hired:
1) Not having a degree
2) Overqualified for the position
3) Taking a cut in salary, they thought I would quit when I could get a job that matched my pay level. But I was laid off from my previous job, so I was getting desperate for anything.
This last interview seemed very promising, I was even getting myself ready to travel across the country to live in a city I had never visited before. I was looking forward to the remoteness of the location. I was definitely qualified for the position, but I think what hurt me is that I needed 3 weeks to make the move, & they were in a pinch to fill the position. They had 2 ladies going on maternity leave, so they were in a hurry to train someone. That position was my dream come true in pay, schedule, & benefits, for a job I already know how to do. I was very disappointed when I got the letter.
Depends on the level of employment. If a child wished to cut your grass then making part of non public organizations aren't usually the main obstacle. But if you talk about executive level positions, or more then usually trust is the main issue.
What a snapshot of time.
I feel as though the BEST thing, literally THE BEST thing I could do, would be to lie to them. Then I could get in the door and figure it out in short order like I used to do.
I have recently lost several job's based on me being too kind and highbrow SEEMING to fit in at that company. The hiring manager literally told me, he himself didn't fit in on that basis and I was classier than he was in one case. This was a top end engineering firm with a diverse portfolio of applications in terms of their business partners. I had a friend that knew the guy and he told me that was the confirmed reason, that I was considered too polite.
3a. You are too old
Yeah, it makes category 3 a real thing. They think slow and cant adjust, and partly they are correct. I do not adjust to stupid very well, and most companies policies and processes are deeply stupid. I can say this as a professional. The software I most worked on was workflow and business intelligence engines.
3b. The interviewer is terrified of you
Most interviewers within the first few minutes begin to fear I will take their job, and that fear grows throughout the interview. By the end of the first 30 minutes they are usually stammering and sweating. It's so predictable and annoying. Remember that often I do not know their tools and specific software. Still, they KNOW I can and will learn it, so even their objections sound trite to them. They start apologizing for saying the canned crap. The one's that are are not afraid are usually just too stupid to be afraid.
Relationships are a two way street.
And I can talk to. That really freaks them out. In my day nerds were people that could not talk. I was a rare exception. My human interface was not broken, and still is not.
But, I am all about sense, real sense. To bad THEY are not.
I had one military boss painstakingly deliver a throw down on everyone (40+ employees, contractors and military oversight), and he showed why he was a big manager with his 8 point plan bragging he came up with it in the last few days. He was letting go all of the contractors, so I had nothing to lose. I asked him if he would hear me out. He was worried but he made the mistake of letting me speak. I had a folder I always took with me to meetings which I called my CYA folder. CYA is Cover Your Ass. It was all the email proof that I had offered LITERALLY EVERY SUGGESTION he was making (and a dozen more he didnt list) and all starting from when I was originally hired almost 4 years previous and up to the last week. That is a near thing to MOST of my employment experiences.
Being able to imagine ways that things can be put together and make a difference IS WHAT I DO.
I have 30+ years experience as a software developer in all walks of the development cycle. <--- THAT should be my whole resume. THAT is all that really matters.
The thing about social media. What if there's 20 other people with your name and the employer clicks on the wrong person...
This thread is golden