How To Handle Rejection From Applying To Programming Jobs?
As soon as I decided to change my career as a developer and become a web dev. I have been rejected by almost 30 companies, sent hundreds of job applications and literally got almost no response back.
It has generally been the same story. I would breeze through phone rounds, do well enough in on-site interviews that I would have a lot of hope, and then I’d get a friendly rejection e-mail.
The easier thing to do would be just to give up and pretend like it never happened. But I insisted. And it got me the job.
In this video, I'm going to tell you why you should not give up if you're receiving rejection after rejection emails.
SUBSCRIBE To Antonio's YouTube Channel: https://simpleprogrammer.com/yt/antoniosubscribe
Get Antonio’s FREE ebook on Controlling Emotions so you can take action right now:
Join Antonio’s Active Instagram Community:
Engage in Antonio’s Facebook Group:
Follow Antonio on Twitter:
Transcript Of The Video
Antonio Cucciniello: Did you just get another rejection email? Something like this, “We won't be moving forward with your resume today.” I know how you feel. I've seen this too many times. Today, let's talk about why you need to hang on. Getting that rejection email sucks. We can all agree on that. I've gotten hundreds of them. Here is the thing though, there's a reason why you didn't get that job. Either you are not qualified for it or the timing was not right or maybe you just wanted the right fit, cultural fit. There can be tons of reasons why. But let me ask you something, how are you going to handle this? Most people are gonna sit there and complain about how hard it is to get a job and waste their energy there.
Then there's the other type of person, the one that just takes that failure and learns something from it. It's often not the fact that we failed that makes us a failure. It's instead our way that we react to the failure that actually makes us a failure. So if you're just gonna sit here and mope around and tell me how hard it is to get a job, how applying just sucks and how you've reached out to people on LinkedIn and no one gets back to you, you're setting yourself up to be a failure, regardless of what I can do. But if you're the kind of person that takes a look at that failure and says, “Okay, why didn't I get this job? Maybe I didn't meet the qualifications. Maybe I said something wrong in the interview. Maybe my technical skills weren't that good. Maybe I need to work on my cultural questions. Maybe I need to care about learning more. Maybe I didn't just really show my value.”
And then take that reason why that you've figured out and come up with concrete action steps in order to fix the weakness that the failure exploited. Then you will be successful in finding a job as a programmer. There's a limited number of rejection emails that you can get before the offers start to pour in if you follow this method of learning from failure and becoming better by it. My challenge for all of your programmers that are struggling to find a job out there because I was in your exact shoes, seek the failure, seek the interview that rejects you and gives you feedback. The failure is telling you something. It's often telling you to improve those interview skills, improve the technical skills or improve your behavioral skills, whatever they are. The failure is trying to tell you in the most obvious way but 99% of you aren't listening.
Once you've listened to it, think of some things that you can do that will improve your situation and fix that weakness that failure exploited for you. This way the next time you go into the next interview don't face the same problem again and if you fail in that one, you improve and learn based off of what happened in that one and you keep adding to your skill set and eventually you'll be this person that is unstoppable and wanted by every company that you apply to. I promise you that the person who consistently shows up, listens to failure when it's speaking right to you and then adapts is the one that ends up winning in the end.